On Ethereum, a token is a contract, and every feature beyond transfer — permits, royalties, vaults, sponsored gas — is another standard the contract must implement and every wallet must support. On EmpoorioChain, tokens are native runtime objects and those features are pallets that apply to all of them. This guide maps the features a token developer reaches for to where they live.
Fungible assets — ERC-20 → pallet-emp-assets, pallet-balances, pallet-stablecoins
DMS itself is pallet-balances. Other fungible assets are created in pallet-emp-assets: an asset id, metadata, an issuer, optional freezing and minimum balance. Stable assets such as DUSD have their own pallet with peg and reserve logic. No contract is deployed; the asset is a state entry, and every wallet that reads the metadata can display it.
await api.tx.assets.create(assetId, admin, minBalance).signAndSend(issuer);
await api.tx.assets.setMetadata(assetId, "My Token", "MYT", 18).signAndSend(issuer);
await api.tx.assets.mint(assetId, beneficiary, amount).signAndSend(issuer);
Non-fungible — ERC-721 / ERC-1155 → pallet-uniques, pallet-emp-nft and the product pallets
Collections and items are native. Product pallets (music-nft, video-nft, dynamic-nft, sbt) add behaviour: batch and lazy minting, mutable traits, non-transferability for credentials.
Signed approvals — ERC-2612 → pallet-permit
An owner signs an allowance (spender, amount, nonce, deadline) off chain; anyone can submit it. Works for any native asset, not only tokens whose contract implemented the standard. Typed signing payloads are SCALE-encoded natively; EIP-712 typed data remains available on the EVM side.
Royalties — ERC-2981 → pallet-nft-royalties
A royalty rule set at collection or token level and applied by the runtime on every transfer. A marketplace cannot bypass it; this is what EidoOS's creator share rests on.
Tokenized vaults and funds — ERC-4626 → pallet-yield-vault, pallet-tokenized-fund
Deposit an asset, receive shares, accounting handled by the pallet with DMS economics. TokenizedFundClient in the Rust SDK is the typed interface.
Sponsored transactions — ERC-4337 → pallet-account-abstraction, pallet-paymaster
User operations, session keys and paymasters at the protocol level. A token project can sponsor its users' first interactions under a validated policy (whitelist, per-operation limit, allowed pallets) without a bundler network.
Token-bound accounts — ERC-6551 → pallet-nft-wallet
An NFT owns assets; they move with it. Native, no registry contract.
Flash loans — ERC-3156 → pallet-flashloan
Atomic borrow-and-repay within one extrinsic against native pools.
Soulbound — ERC-5192 → pallet-sbt
Non-transferable tokens for credentials and membership; KryptoOS credentials can anchor to them.
Where the EVM still fits
If your token must be an ERC-20 contract — because a partner integration expects an ABI — deploy it through Frontier on chain id 2026. It will work, and it will not get the native features above unless it calls the precompiles (0x72 for ERC-721 views, 0x1155 for multi-token). The design guidance in the repository is explicit: native pallets when the chain can enforce the rule better than a contract; Frontier when Ethereum tooling is the fastest path.
Caveat on maturity
All of these pallets are in the live runtime. Not all have carried real traffic: the network settled its first DEX swap on 14 September 2026, and its first signed transactions of any kind only weeks earlier. Treat the feature list as wired and check EmpooScan for exercised before building a product on a pallet's untested corner.
Based on EIP_COVERAGE.md, ARCHITECTURE.md and PALLET_REFERENCE.md.