A tokenized bond, a fund share or a property fraction is only useful if the token cannot end up somewhere the law says it cannot. On Ethereum that means a permissioned-token contract (ERC-3643, ERC-1400) that every marketplace must respect and that a single careless integration can bypass. EmpoorioChain moves the rule into the chain.
The pallets
| Concern | Pallet | What it does |
|---|---|---|
| Transfer restrictions | pallet-compliance | Rules per asset: who may hold, how much, where |
| Identity requirement | pallet-identity-ssi | Requires a valid KryptoOS credential (did:emp) before a transfer settles |
| Sanctions screening | pallet-sanctions | Chain-wide deny lists applied on every transfer of a flagged asset |
| The asset itself | pallet-emp-rwa | Real-world-asset token with partitions, disclosures and issuer controls |
| Fund structures | pallet-tokenized-fund | Shares, NAV accounting, subscription and redemption flows |
Because enforcement happens in the runtime, it applies regardless of which app initiated the transfer — Eoonia, a DEX, an EVM contract through a precompile, or a raw extrinsic from Polkadot.js. There is no integration to forget.
How a transfer is checked
- The sender submits a transfer of an RWA asset.
pallet-emp-rwaconsultspallet-compliancefor the asset's rules.- Compliance checks
pallet-identity-ssi: does the recipient hold a credential of the required type, not revoked, from an accepted issuer? - Compliance checks
pallet-sanctions: is either party on a deny list? - Only if every rule passes does the balance move. Otherwise the extrinsic fails with a deterministic error the wallet can explain.
The credential check reveals nothing about the holder's identity to the chain: the credential is a KryptoOS verifiable credential, and what the chain sees is that a valid proof exists for the required claim.
Privacy and post-quantum
RWA flows are where regulatory privacy requirements bite hardest. pallet-privacy and the ZK verifier pallets allow selective disclosure — prove accredited investor without revealing who — and the chain's signed-extension design carries an optional post-quantum signature (CheckPqcPolicy) so that long-lived asset records are not exposed to future key recovery.
What is live and what is not
All five pallets are wired into the live runtime (spec 220). The KryptoOS circuit that issues and anchors credentials was completed and tested against the live chain on 13 September 2026 — the network registered its first DID the following day. What does not exist: any issued regulated asset, any partner integration, any institution using this in production. The ecosystem's own review in September 2026 removed claims to the contrary from several websites, and this post will not reintroduce them.
What exists is a settlement layer where the compliance rule is a property of the asset and not of the app — ready for a pilot, and honest about being at that stage.
For issuers evaluating it
The integration document for exchanges and custodians (INTEGRACION_EXCHANGES.md) covers account model, finality (GRANDPA, roughly 17 seconds at the median on the testnet benchmark), the extrinsic envelope, and the three-state confirmation model. The testnet grants programme reserves a category for identity and compliance pilots; its prerequisites (a faucet, a public explorer) are being deployed before the call opens.
Based on EIP_COVERAGE.md, PALLET_REFERENCE.md, the KryptoOS Phase 3 verification (2026-09-13) and INTEGRACION_EXCHANGES.md.