Tokenization
as runtime rules

EmpoorioChain enforces holder eligibility, sanctions screening and partitions on a regulated asset at the runtime level, so the rule holds whichever app moves it. No regulated asset has been issued; the identity layer registered its first DID on 14 September 2026.

5RWA and compliance pallets in the live runtime
0Regulated assets issued
0External audits commissioned
1DIDs registered on the public testnet

Read the design

Compliance pallets, NAV accounting, and the checklist a regulated asset manager would run.


What is
native tokenization?

EmpoorioChain's rule is that a compliance requirement lives on the asset, not in the application: pallet-emp-rwa for the instrument, pallet-compliance for who may hold it, pallet-sanctions for screening, pallet-identity-ssi for the credential a holder must present, pallet-tokenized-fund for baskets with NAV accounting. Wired in runtime 220; awaiting an issuer.

What exists today

emprwa

Real-world-asset tokens with partitions, disclosures and issuer controls — the native counterpart to ERC-1400 and ERC-3643.

Runtime index
54
Runtime index
tokenizedFund

Shares against subscriptions, redemptions at NAV, a typed Rust SDK client. No fund exists on the testnet.

Runtime index
76
Runtime index
compliance

Holder eligibility enforced on every transfer, with pallet-sanctions screening; the Travel Rule parameters are an unchecked mainnet-gate item.

Transfer checked
every
Transfer checked
kryptoos

did:emp identifiers and verifiable credentials — the identity input to compliance. Circuit verified against a real chain 13 September 2026.

DID on the testnet
1
DID on the testnet

Institutional toolkit

The on-chain half. The issuer, licence, custody and rails are the institution's.

Videos

No ecosystem videos yet.



Read: regulated assets, natively

How the transfer check works, what is live, and what is not.

Tokenization on EmpoorioChain | empoorio