Canonical asset registry
The end state is not an RWA L1. It is a financial stack: registry, identity, orderbook, margin, lending, settlement, risk, oracle, compliance and liquidation, exposed as one programmable surface.
Native orderbook / RFQ
Unified margin
Risk engine and oracle
Each module is useless alone and compounding together. A single transaction can cross identity, risk and settlement without leaving the chain.
- Asset registry
- Identity / KYC
- Native orderbook / RFQ
- Unified margin
- Lending
- DvP settlement
- Stablecoin settlement
- Risk engine
- Oracle
- Compliance
- Liquidation
Who builds on it
The chain is infrastructure, not a destination. Distribution belongs to the clients built on top of it.
- Wallet
- Broker
- Exchange
- RWA issuer
- Market maker
- Institution
What is live today
The identity, compliance and asset-state layers already run as native protocol state on the testnet, with an open EVM surface beside them. Orderbook, risk engine and margin build on top of these.
Registry precompile
Binds wallets to institutions, reserves asset scopes and resolves time-bound roles.
Compliance precompile
Evaluates trusted claims, policies and restrictions for every token operation.
RWA precompile
Owns asset revisions, metadata versions, approvals and the single active official binding.
Regulated token suite
Keeps balances and supply in EVM storage while adapters resolve native identity and compliance.
Atomic across native and EVM state
A reverted outer contract call rolls back native module state and EVM logs together. The interface never needs to reconcile two partially committed ledgers.
Deliberately bounded claims
Roadmap stages beyond the live testnet describe intended direction, not shipped functionality. Protocol enforcement does not grant a legal license or guarantee that every represented asset is recognized in every jurisdiction.