Fungible tokens on EmpoorioChain (an ERC-20-style asset — a token where every
unit is interchangeable, e.g. a stablecoin or a reward token) are managed by
pallet-emp-assets, compiled into the runtime at index 23.
pallet-emp-assets is wired into the runtime as an alias to the upstream
Parity pallet-assets crate, not the bespoke, extrinsic-by-extrinsic
documented crate that appears in some of the project's internal pallet
documentation. It genuinely works and is live at index 23, but its exact
extrinsic names and parameters should be verified against live chain
metadata rather than assumed from any hand-written extrinsic list —
including the general descriptions on this page.
What you can generally do
At a capability level, pallet-emp-assets gives you the kind of operations
you'd expect from a Substrate assets pallet:
- Create a new asset class (an "asset ID" plus basic parameters like minimum balance).
- Mint new units of an asset to an account.
- Burn units of an asset from an account.
- Transfer asset balances between accounts.
- Approve a delegate to transfer a limited amount on your behalf, and revoke that approval later.
- Freeze / thaw, either at the level of a single account or the whole asset class, to pause transfers.
- Set metadata (name, symbol, decimals) and manage authorities (who can mint, freeze, or administer the asset).
Treat this as a description of the shape of what's available, not a literal
API reference — do not copy exact method names or argument lists from this
page into production code without checking api.tx.assets (or your SDK's
generated bindings) against a live node first.
What's different from an account-derived token model
EmpoorioChain does not use a program-derived-address / Associated
Token Account pattern. Asset balances are stored in a straightforward
(asset_id, AccountId32) storage map — there's no separate "token account"
you create or close ahead of holding a balance, and no wrapped-native-token
concept: EmpoorioChain's native DMS token is used directly for balances and
transaction fees, so there's nothing equivalent to a wrapped native token
pattern to sync.
Is this page helpful?