Token Support
Ensure your tokens display with proper names and amounts instead of raw contract addresses.
The Problem
Without token support, users see:
- Contract addresses instead of token names
- Raw wei values instead of formatted amounts
- Hexadecimal data instead of readable information
With token support, users see:
- Token symbols (USDT, UNI, AAVE)
- Formatted amounts (1,000 USDT instead of 1000000000)
- Collection names for NFTs
Good news: Token support is automatic once your token is in the Ledger database. No metadata files needed.
Supported Token Types
Quick Check: Is Your Token Supported?
Check Ledger’s supported assets list by token name, symbol, or contract address.
Send a small test amount. If supported, you’ll see the token symbol. If not, you’ll see the contract address.
Each chain needs separate support. A token on Ethereum might not be supported on Polygon yet.
Add Your Token
If your token isn’t supported yet:
Submit to Support
Contact Ledger Support with your token information.
Wait for Review
Tokens are reviewed and added in weekly batches (typically 1-2 weeks).
Verify Addition
Check the supported assets list or test a transaction once notified.
Token addition is subject to review. Tokens must have legitimate use case, sufficient liquidity, and regulatory compliance.
Optional: Add Token Icon
Make your token more recognizable in Ledger Live:
- • Format: PNG or SVG
- • Size: 64x64px (PNG) or scalable (SVG)
- • Background: Transparent
- • File size: Under 50KB
- • Fork ledger-live repo
- • Add icon to
assets/icons/ - • Follow naming convention
- • Submit pull request
Using Tokens in Your Metadata
When your contract interacts with tokens, reference them in your Clear Signing metadata:
Static Token (Known Address)
{
"formats": {
"amount": {
"type": "token_amount",
"token": {
"contract": "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48",
"decimals": 6,
"symbol": "USDC"
}
}
}
}Dynamic Token (Variable Address)
{
"formats": {
"amount": {
"type": "token_amount",
"token": {
"selector": "$.params.token", // Reference to token address in transaction
"decimals_selector": "$.params.decimals" // Optional: dynamic decimals
}
}
}
}NFT Collections
{
"formats": {
"nft_info": {
"type": "nft_name",
"collection": "0xBC4CA0EdA7647A8aB7C2061c2E118A18a936f13D",
"token_id": "$.params.tokenId"
}
}
}Troubleshooting
Token shows as “Unknown Token”
Token needs to be added to Ledger database. Follow the request process above.
Incorrect decimal places shown
Report to support with correct decimal value. This indicates wrong token data in database.
NFT metadata not loading
Ensure NFT contract implements standard metadata methods (tokenURI for ERC-721, uri for ERC-1155).
Next Steps
Token support is completely free. No fees, no partnership required. Just submit your token details and help make Web3 safer for everyone.
