aarnâ
0%
Loading
Technology

infrastructure for
regulated tokenised assets.

Our technology is built around a single constraint: every asset on the platform has to be tokenised and satisfy IFSCA regulatory requirements at the same time. No compromise on either.

Permissioned tokens - ERC-3643

All aarna tokenised 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. Regulatory enforcement is programmable, not procedural.

Decentralised identity - ONCHAINID

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.

Independent NAV attestation

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.

Agentic risk curation - aTARS

aTARS is aarna's production multi-agent system. Risk analytics and curation over the underlying credit portfolio is planned, introduced progressively through the sandbox: concentration, security cover, tenor, delinquency signals, hedged exposure and stress behaviour.

Signals surface for human review. It does not select funds, size allocations or commit capital.

Security

The platform has completed internal smart-contract and application security reviews. An independent penetration test and external smart-contract audit are scheduled before launch.

  • Bank-grade encryption - all personal data locked with AES-256, keys in AWS KMS
  • Private by default - personal data stays masked; every access is time-boxed and logged
  • Least-privilege access - scoped roles, two-person approval on sensitive actions
  • Unchangeable audit trail - every action recorded in tamper-proof, append-only ledgers
  • Secure by build - signed releases, automated code and dependency scans, penetration tests on every change
  • Hardened infrastructure - TLS everywhere, no public data stores
Roadmap
  • Deeper DeFi composability - under evaluation, subject to institutional demand
  • Multi-chain deployment - under evaluation, extending beyond Ethereum to chains with institutional adoption