Real-world-asset (RWA) tokens — an ERC-3643-style asset, where transfers are
restricted to eligible, verified holders rather than open to anyone — are
handled by pallet-emp-rwa, compiled into the runtime at index 54.
What you can generally do
At a capability level, expect the kind of operations a permissioned/ compliance-gated token standard provides:
- Issuing a permissioned token class representing an off-chain asset.
- Managing eligibility — attesting or whitelisting which accounts are allowed to hold or receive the token.
- Enforcing transfer restrictions on-chain, rejecting transfers to non-eligible accounts rather than relying on off-chain policy alone.
- Compliance-driven administrative actions (e.g. a designated authority
recovering or force-transferring tokens in a regulatory scenario) are a
common pattern for this class of token standard, so it's worth checking
whether
pallet-emp-rwaexposes something similar — but this hasn't been confirmed extrinsic-by-extrinsic, so verify against live chain metadata rather than assuming a specific call exists.
As with the other token pallets on this site, treat the list above as a
description of the general shape of the pallet, not a literal API
reference. Don't copy exact method names or argument lists into production
code without checking api.tx.empRwa (or your SDK's generated bindings)
against a live node first.
Related compliance pallets
The runtime also compiles a separate pallet-compliance (index 51) and
pallet-sanctions (index 57). How these interact with pallet-emp-rwa has
not been documented as part of this research pass — if your application needs
compliance/sanctions enforcement alongside RWA tokens, check those pallets
directly rather than assuming a specific integration.
Is this page helpful?