Standards
The standards underneath
Compliance is a property of the instrument here, not a process wrapped around it. Four standards carry that: one for the token, one for the identity that may hold it, one for the price it is carried at, and one for how capital moves in and out.
ERC-3643
Permissioned tokens
All aarna tokenized assets are issued as ERC-3643 permissioned digital tokens. The standard enforces compliance at the token level: transfers execute only between wallets holding valid identity claims. The compliance layer is built into the token contract itself, not bolted on around it.
In practice: an ICT token cannot be transferred to an unverified wallet. Secondary trading, when enabled, respects the same identity and jurisdiction rules as primary issuance. Selected transfer and eligibility controls are programmable and auditable.
What the standard enforces
- Token-level compliance
- Identity-gated transfers
- Programmable eligibility
- Auditable controls
ONCHAINID
Decentralised identity
Investor identity is managed through ONCHAINID, a decentralised identity standard integrated with ERC-3643. On completing Sumsub KYC, identity claims are issued on-chain - accredited status, jurisdiction, AML clearance - portable across any ERC-3643 asset aarna issues.
Attestation
Independent NAV
ICT's net asset value is certified on a defined cycle, aligned with the reporting cadence of the underlying funds, and published onchain through a multi-signature attestation process, so pricing is transparent and independently verifiable.
ERC-7540 · ERC-4626
Asynchronous vault
Subscriptions and redemptions run through an ERC-7540 asynchronous vault, built on the ERC-4626 tokenized vault standard. A subscription or redemption is submitted as a request and settled in a separate step, rather than exchanged instantly in a single transaction. That matches how the underlying works: capital is invested into, and realised from, funds that price on a defined cycle.
In practice: an investor's request is queued, priced at the net asset value for that cycle, and then settled, with ICT minted to or burned from their wallet. Instant deposit and withdrawal are disabled by design. Because the vault follows the ERC-4626 interface, wallets, custodians and integrators can read it the way they read any standard vault.
What the vault enforces
- Request-based subscriptions
- Pricing at each cycle's NAV
- Windowed redemptions
- No instant exit