Introduction | Developers


Estimated reading time: 2 minutes

How Ledger Live manages tokens

In Ledger Live, there is a main account, and there are sub-accounts.

The main account is where Ledger Live does the main currency transactions.

There is a sub-account for each token. Sub-accounts can be either “token accounts” or “child accounts”, the primary difference being that token accounts share the same address as their parent account, while child accounts have their own address.

These account types are defined in the code in account.ts

Token operations are defined both as operations in the sub-accounts, and as sub-operations in the parent account operations, as defined in operation.ts

How it works

Similarly to transferring native assets, transferring tokens requires the end-user to confirm the transaction details on the Nano devices’ screens. Such verification is a security requirement and must be made available before the application is released by Ledger. Expected information to verify are (at least) : the amount transferred, the token name and/or ticker, the recipient address.

Different tokens imply multiple names, multiple tickers, multiple identifiers and, sometimes, different magnitudes (or decimals). As an example, BAT and USDT tokens are both ERC20 tokens on the Ethereum network and have each their own set of characteristics :

{“ticker”: “BAT”,”name”: “BAT”,”contract_address”: “0x0D8775F648430679A709E98d2b0Cb6250d2887EF”,”decimals”: 18} {“ticker”: “USDT”,”name”: “Tether USDT”,”contract_address”: “0xdAC17F958D2ee523a2206206994597C13D831ec7”,”decimals”: 6}
  • The smart contract address is important as this information will allow the Nano Ethereum or Algorand application to correctly determine the token being transferred and its characteristics.
  • The decimals information is important as an error in its value will result in the wrong amount being displayed on the Nano screen. A user may approve a transaction to transfer 10 USDT, when in reality, they are approving a transaction for 1000 USDT.

Ledger applies a specific signature to the triplet {“ticker”,”contract_address”,”decimals”}. As a consequence, the Nano is able to verify the information has not been tampered with.

How to request a token addition?

Follow the action for:

Other types of tokens are not supported for the moment. This documentation will be updated when new types are supported.

Did you find this page helpful?

How would you improve this page for developers?

Frequently Asked Questions
Getting Started
Theme Features