Address
0x0a01700000000000000000000000000000000004
The Token Registry precompile exposes the x/tokenregistry module’s conversion methods,
which move balances between an ERC20 contract and its paired Cosmos coin denom.
Conversions require both module-wide transfers and the specific token pair to be enabled.
Pair registration and enablement are permissioned operations performed by the chain
operators and are not part of this interface.
Supported Methods
Conversions
This precompile is transaction-only; registry state is read through the Cosmos gRPC/REST
query service of
x/tokenregistry.
Events
transferToCore and transferToEVM deliberately emit no precompile event — the
post-tx settlement hook emits the standard ERC20 Transfer event instead.
Two-Stage Conversion Model
Conversions do not settle inside the precompile call:- Precompile stage — all preconditions are validated and a pending conversion intent
is written. The method returns
staged = true. - Post-tx hook stage — the mint/burn and ERC20 transfer are executed and the ERC20
Transferevent is emitted.
true return value therefore means “validated and queued”, not
“balance already moved” — do not read balances back within the same call and expect the
conversion to be reflected.
Only one pending conversion intent is allowed per transaction, so a single transaction
cannot chain two conversions.
Transaction Examples
Set the current testnet EVM JSON-RPC endpoint and precompile address:Security note: Use a keystore or hardware wallet for real operations. Do not pass raw private keys directly in shell commands.