On Ethereum a wallet learns about a token from a list someone maintains, then calls the contract for a balance. On EmpoorioChain the assets are in the chain state with their metadata, and Eoonia reads them there. This post is what that looks like from inside the wallet.
Fungible assets — pallet-assets
Eoonia's token module enumerates the assets registered in pallet-emp-assets, reads each one's metadata (name, symbol, decimals) and the account's balance. On the testnet, DUSD is asset #1. There is nothing to import: an asset a user receives appears. Verified against the live chain in the September audit (block 2).
DMS itself
The native balance, from pallet-balances, with 18 decimals. Shown once, with both the Substrate address (vx…, prefix 2026) and the EVM address (0x…) that map to the same funds.
NFTs
The NFT suite — pallet-uniques collections, pallet-emp-nft, pallet-dynamic-nft, pallet-music-nft, pallet-sbt — is read from state. Eoonia shows the items an account owns, with media resolved through the storage layer. Dynamic NFTs (the product passports Empoorio Warehouse mints) show their current traits, since those live on chain and change.
Credentials — KryptoOS
An account's did:emp and its anchored credentials from pallet-identity-ssi. The chain registered its first DID on 14 September 2026; the display code was ready before the data was.
One correction worth recording: the ecosystem had five incompatible DID formats in circulation, two of them inside Eoonia itself for the same user (did:emp: from the pallet versus did:empoorio: from apps). Unified on the pallet's did:emp:.
Royalties, permits and other rules
Eoonia does not need to know a token implements permit or royalties — those are runtime rules that apply to every asset. When the user transfers an NFT, the royalty is applied by the chain; when they sign a permit, it is pallet-permit for any asset. The wallet's job is to decode and display, which it does from metadata.
The asset the wallet hides
Carbon credits (pallet-carbon-credits) appear if an account holds them. But minting them requires a root origin in runtime 208+, so Eoonia does not show a mint button. A button that always fails is worse than no button — a rule the audit applied in several places.
The wrapped token that is not shown as DMS
A wrapped DMS exists on the Sepolia Ethereum testnet with a bridge escrow of zero. Eoonia's price service returns 0 for it rather than the native price, and 25 documents across the ecosystem that implied it was redeemable were corrected in August 2026. If you see it in an Ethereum wallet, it is a test artefact.
For dApp developers
If you issue an asset through pallet-emp-assets with metadata, Eoonia users see it with no action on your part. If you deploy an ERC-20 through Frontier instead, it behaves like any Ethereum token — the EVM view supports it, but you lose the native display and the runtime-level rules.
Based on the Eoonia audit block 2 (2026-09-07), the KryptoOS audit (DID formats) and PALLET_REFERENCE.md.