Built around a single constraint: every asset on the platform has to be tokenized and satisfy IFSCA regulatory requirements at the same time. No compromise on either.
ERC-3643 permissioned tokensONCHAINID identity claimsMulti-signature NAV attestationERC-7540 asynchronous vault
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
Security
Controls of record
The platform has completed internal smart-contract and application security reviews. An independent penetration test and external smart-contract audit are scheduled before launch.
L1Data
AES-256 encryption
Encrypted at rest and in transit, keys held in AWS KMS.
Private by default
Personal data stays masked; every access is time-boxed and logged.
L2Access
Least-privilege access
Scoped roles, with two-person approval on sensitive actions.
Unchangeable audit trail
Every action recorded in tamper-proof, append-only ledgers.
L3Build and infrastructure
Secure by build
Signed releases, automated code and dependency scans, and security testing in the release pipeline.
Hardened infrastructure
TLS everywhere, and no public data stores.
AI at aarnâ
The intelligence layer across aarnâ
aTARS is aarnâ's agentic layer, operating across investor interaction, platform operations and continuous monitoring. Actions stay bounded by defined permissions, controls and auditable workflows.
ATARS
Three functional areas, each with a defined job and an explicit status.
Live
Operational orchestration
Prepares, simulates, validates and reconciles workflows across the token lifecycle, reducing manual coordination while preserving deterministic controls and an auditable trail.
Every prepared transaction is simulated, checked against the guardrails, its invariants verified and its reconciliation confirmed before it is proposed for signing. The same discipline runs over the NAV attestation pipeline.
Live
Intelligent investor interaction
Understands the product, its structure and the investor's own position, answering questions and assembling relevant information and workflows in context.
It answers how ICT works, where a subscription has reached and when the next distribution falls, at the point the investor asks rather than after a ticket has sat overnight. Where something needs a person, it hands over with the full context already assembled.
In development
Continuous monitoring
Continuously observes infrastructure, transaction states and the underlying portfolio between reporting dates, reporting the findings to the team.
Not built yet - credit decisions over the underlying stay with the funds' authorised, SEBI-regulated managers.
Security review
Seven-round agentic audit
Before mainnet, the ICT contract suite was audited by two agentic methods: a four-round split-pass audit with 12 specialist agents per round, then a three-pass adversarial re-review by Claude Fable 5. Findings were gated against documented invariants; all were fixed in code and verified against the full test suite, bar one made redundant by a refactor.
4 × 12
Method 1
Split-pass audit
Configuration
4 sequential rounds × 12 specialist agents
Scope
All 23 contracts
Gating
Findings de-duplicated and gate-evaluated against documented invariants
44findings
Remediations → re-review
3 × 12
Method 2
Claude Fable 5 adversarial re-review
Configuration
12-agent adversarial panel × 3 passes
Scope
All 23 contracts re-reviewed from scratch, plus every remediation from the split-pass audit
Gating
Re-reviews the remediations themselves, not just the original code
