The usual answer to "we need permissioning" is a private chain: same technology, closed membership, no public verifiability. EmpoorioChain's answer is different — keep the network public and put the permissions on the assets. This post explains the model.
Permissioning at the asset level
A regulated asset on EmpoorioChain — a tokenized fund share, a security token, a compliance-bound stablecoin — carries rules the runtime enforces on every transfer, regardless of which app or contract initiates it:
| Rule | Pallet | Example |
|---|---|---|
| Who may hold | pallet-compliance | Only accounts with an accredited-investor credential |
| Jurisdiction and limits | pallet-compliance | Not to accounts flagged for a jurisdiction; maximum position size |
| Screening | pallet-sanctions | Chain-wide deny lists; travel-rule parameters (a mainnet-gate item) |
| Identity requirement | pallet-identity-ssi | A valid, unrevoked KryptoOS credential from an accepted issuer |
| Partitions and disclosures | pallet-emp-rwa, pallet-tokenized-fund | ERC-1400-style partitions; NAV and subscription flows |
| Account lifecycle | CheckDormantAccount (signed extension) | Policy hook for dormant accounts, checked on every transaction |
The asset is public — its supply, its rules and every transfer are visible on EmpooScan — while the holders can be private, because what the chain checks is a proof that a valid credential exists, not who the person is.
Why not a private chain
A private instance forks the security budget: a handful of validators, no external verifiability, and a bridge back to the public network that becomes the weakest point. Asset-level permissioning keeps one validator set, one finality, one explorer, and lets a regulated asset and a public DEX pool live in the same state. The compliance rule follows the asset into any pallet — a permissioned token listed on the DEX still cannot settle to a non-credentialed buyer.
Governance boundary
pallet-gov-boundary (index 34) and pallet-guardian (index 32) define what on-chain governance may and may not change — the six iron rules of the governance design, including that no entity holds more than 10 % of effective voting power. For an institution, that is the assurance that the rules an asset was issued under cannot be voted away by a token majority.
What is live
Every pallet above is in runtime 220. The KryptoOS credential circuit was verified against a real chain on 13 September 2026 and the first DID registered the next day. CheckDormantAccount has been in every transaction since runtime 208.
What is not
No regulated asset has been issued. No institution uses this. pallet-sanctions has no initial parameters configured (a blocking mainnet-gate item). The DeFi, PQC/ZK and mobile audits the gate requires have not been commissioned. The previous version of this page described institutions and partners that were never part of this ecosystem; this one describes a runtime that is ready for a pilot and a pilot that has not started.
Based on EIP_COVERAGE.md, PALLET_REFERENCE.md, FORMATO_DE_EXTRINSECOS.md and MAINNET_GATE.md Gate 5.