Coin Types
Last updated
Was this helpful?
Last updated
Was this helpful?
This section provides a comprehensive explanation on how to understand and use coin types, particularly within EVM (Ethereum Virtual Machine) compatible chains. We will reference formal specifications such as for non-EVM coins and ENSIP-11 for EVM compatible chains.
Coin types are identifiers used to uniquely specify the address encoding types of various cryptocurrencies, particularly in the context of deterministic wallets. These identifiers ensure that addresses for different types of coins are distinct and non-colliding.
For non-EVM compatible chains, coin types are assigned according to the standard. This document lists various coin types and their respective cryptocurrencies.
For EVM compatible chains, the ENSIP-11 specification extends the basic multi-coin resolution principles introduced in ENSIP-9. ENSIP-11 provides a systematic way to derive and manage coin types for EVM chains.
ENSIP-11 dedicates a designated range for coin types for EVM chains, ensuring they do not collide with non-EVM coin types.
The primary motivation of ENSIP-11 is to avoid redundant requests for adding EVM compatible chains into SLIP 44 because most of these chains inherit Ethereum's address encoding type.
MSB Reserved: The most-significant bit (MSB) is reserved for EVM chain IDs.
Coin Type Derivation: Compute the coin type for EVM chains by bitwise-ORing the chain ID with 0x80000000
:
Reverse Operation: To infer the chain ID from a coin type, bitwise-AND the coin type with 0x7fffffff
:
To compute the new coin type for an EVM chain (e.g., chain ID 61):
Some EVM chains have specific considerations:
AVAX: AVAX has multiple chain address formats, only c
chain is EVM compatible.
RSK: RSK requires additional validation.
These chains will continue using coin types as defined in SLIP44.
The following EVM compatible coin types were defined before this new standard and should be appended with _LEGACY
for backward compatibility:
NRG
POA
TT
CELO
CLO
TOMO
EWT
THETA
GO
FTM
XDAI
ETC
When these are displayed, append _LEGACY
to the coin type and mark them as read-only.
An implementation is provided in the .