Ledger Live Supported Networks vs Token Standards Explained
Ledger Live Supported Crypto Assets Guide begins with a direct check: open the companion app, connect the hardware signer, go to the manager, and read the official token and network directory there. That in-app directory is where the exact roster is maintained; any blog post, video, or spreadsheet can be outdated or altered. If a coin or token does not appear in the manager, do not create a custom account for it or send funds to an address you cannot verify on the device screen.
The hardware signer generates and stores private keys inside a secure element chip. Those keys never leave the device. The desktop and mobile companion app prepares accounts, displays balances, installs coin-specific firmware apps, and builds transactions. Every transfer must be confirmed physically on the signer’s screen, where you check the recipient address, amount, and network before approving. This separation is the core safety mechanism: the app can be compromised, but it cannot move funds without the device’s confirmation.
Compatibility depends on more than a ticker symbol. A native coin uses its own network rules, while a token usually lives on a host chain and requires the correct app, account type, and address format. Two tokens with the same name can exist on different networks. Sending a token to an address on the wrong network can result in permanent loss. Before any transfer, confirm three things on the signer: the network name, the recipient address, and the contract address when the token requires one.
Use the official download page and support documentation to check coverage, firmware updates, and third-party integrations. The app may show a token through a partner service rather than native account support; in that case, the partner’s terms, identity checks, and custody model apply. Never share the 24-word recovery phrase with anyone, including support staff. No legitimate support channel will ask for it. If a website, message, or phone call requests those words, treat it as a theft attempt.
How to Check Which Coins and Tokens Ledger Live Supports for Your Ledger Device
Use the manufacturer’s official compatibility page together with the app catalog inside the companion program, and confirm both against the firmware installed on the hardware unit before adding any account.
Open the official website on a computer or phone, locate the compatibility matrix, and search for the exact ticker or token name. Do not trust search engine snippets, forum posts, or exchange listings; those sources lag behind the official registry and may describe a different network or contract address. If the matrix says a coin needs a dedicated device app, note that name, because the companion program will ask for it during account creation.
Inside the companion program, go to the manager section, connect the hardware unit, and let the program read the installed firmware. The manager displays only the device apps that the present firmware can run. If a requested network or token standard is absent, updating firmware or the companion program may reveal it, but only when the manufacturer publishes that compatibility. Never install an unrelated app to force an account; a mismatch can cause the companion program to create an address that the device cannot sign for.
For tokens, check the parent network and the contract address. Many tokens do not have their own device app; they live inside the account of the underlying chain. The companion program may show them only after the correct network app is installed and the account is added. Verify that the token’s contract matches the one in the official registry, because a lookalike ticker can point to a worthless or malicious contract.
Mobile and desktop versions of the companion program can differ in visible accounts, token detection, and manager access. Check the same coin on both platforms if you use them, and rely on the official release notes for changes. A desktop-only feature may not appear on a phone, so absence on one screen does not always mean the hardware unit cannot handle the network.
If a coin or token is missing, do not send funds to an address from a third-party interface unless you first confirm that the hardware unit can sign transactions for that network and that the companion program will recognize the resulting account. Test with a small amount, verify the receiving address on the device screen, and consult the manufacturer’s support pages for exact app names, firmware requirements, and token standards. Lists and app catalogs change, so repeat the check after every firmware or companion program update.
Supported Coin Networks vs. Token Standards: ERC-20, BEP-20, SPL, and More
Always confirm the token standard before initiating a transfer; sending an ERC-20 token to a BEP-20 address, if both share the same 0x prefix, leads to irreversible loss. The hardware wallet derives addresses from your seed phrase per network, while the companion application creates separate accounts for each standard. For ERC-20 and BEP-20, the device displays the token contract address during transaction confirmation; for SPL, the app requires the associated token account address. Verify these details on the device screen, not just in the app.
Networks are base blockchains like Ethereum or Solana; token standards like ERC-20, BEP-20, and SPL are contract rules on those chains.
When you install a network app on the hardware wallet, you gain the ability to sign transactions for that chain’s native coin. The device’s secure element generates and stores private keys; they never leave the chip. Token standards require additional steps: for ERC-20 and BEP-20, the companion application often auto-detects token contracts, but you must still add the token as a custom entry if it is not listed. For SPL, the process involves creating an associated token account, which the app may handle automatically after you add the Solana network. The device itself never stores token contracts; it only signs messages that the app constructs. This separation means a compromised computer cannot alter the token standard or recipient address without your physical approval on the device screen. Always cross-check the contract address on a trusted block explorer before approving.
Never assume two tokens with the same ticker share a network. A USDT on Ethereum (ERC-20) and USDT on Tron (TRC-20) are distinct; sending one to the other’s address destroys the funds. The companion app lets you add multiple accounts for the same token ticker across different networks, each with its own receiving address. Use the device screen to verify the network name and contract address for every token transfer.
Why Some Crypto Assets Need a Separate Ledger Live App or Third-Party Wallet
Use the device’s native companion app for coins whose blockchain logic is built into it; for everything else, install a dedicated third-party client or a separate app module that can speak to the hardware signer.
A dedicated network app must be installed on the device before any transaction can be signed for that chain. The main desktop/mobile software bundles only a subset of such modules. A third-party interface can request installation of the correct module and then format transfers, staking operations or contract calls for on-screen approval.
Differences in account models, address formats, memo and tag requirements, signature schemes, transaction serialization, fee markets, contract interfaces and derivation paths explain why one interface cannot handle every chain. The hardware signer parses only what its installed app module understands; if the module cannot decode a payload, the device may fall back to blind signing, which shows raw bytes rather than readable details. A separate client supplies the missing parsing logic, builds the payload, and sends it to the device for physical confirmation. Without that layer, a balance can appear in an explorer while remaining unusable from the main software.
Check the vendor’s compatibility page and install the correct network module before moving funds.
The table below contrasts three routes: a native module inside the vendor’s companion application, a dedicated third-party client, and an external desktop or mobile interface that connects to the hardware signer. Each route changes who prepares the transaction, how much of the payload the device can display, and which party controls updates.
| Route | Key location | Transaction builder | Device confirmation | Main trade-off |
|---|---|---|---|---|
| Native companion module | Keys remain in secure element | Vendor software | Full parsed details when module recognizes chain | Limited chain coverage; new networks arrive after module updates |
| Third-party dedicated client | Keys remain in secure element | Third-party software | Depends on client’s parser; verify device screen | Broader reach; higher trust burden and phishing risk |
| External desktop or mobile interface | Keys remain in secure element | External application | Often partial; blind signing may occur | Flexible for niche chains; requires manual checks |
Third-party interfaces introduce specific failure modes: lookalike download pages, malicious transaction builders, address swapping in the clipboard, and fake help-desk messages that request recovery words. Verify every receive address on the device screen, compare the first and last characters, and send a test transaction before large transfers. Use only download links published on the vendor’s official site, and treat any request for the recovery phrase as fraud.
For chains with memo or tag fields, confirm the third-party client places that data in the correct field and that the device screen shows it before approval. For staking, review validator identity, lock-up conditions and slashing risk, because rewards vary and withdrawal rules differ by network. For token contracts, limit approvals to the amount needed and revoke unused allowances through a trusted interface. For UTXO chains, inspect change outputs and fee priority on the device. Keep firmware and network modules current through official channels; if a coin lacks native integration, do not send it to a device address until the proper module and companion interface are ready.
Adding a Supported Asset Account in Ledger Live: Steps and Device Requirements
Connect the signer, unlock it, and install the network-specific application before creating its account in the companion.
Then open the companion, choose the account creation option, pick the network or token, and select the connected device; keep the device unlocked and the relevant application open while the companion reads the public address. The device must have a screen for physical verification, a secure element that generates and stores private keys, current firmware, sufficient free storage for the network application, and either a USB cable or Bluetooth link depending on model. For a token that shares another chain’s address, add the account under the host network rather than installing a separate application; verify the receive address on the device screen before naming the account. If the network application is missing or storage is full, remove an unused app, reconnect the device, and retry; never enter the recovery phrase into the companion or any website.
What to Do When a Coin Is Missing from Ledger Live’s Asset List
Check the parent network account first. A token such as an ERC-20 or BEP-20 unit will not appear as an independent entry unless the underlying chain’s account already exists in the companion application. Open the accounts overview, confirm that an account for that base network (e.g., Ethereum) is present, and add it if missing by connecting the signing device and installing the network application.
If the base account exists, verify that the specific token has been added as a custom entry. Many digital currencies that run on another chain require manual inclusion because the interface does not automatically detect every contract address. Locate the official contract address from the project’s documentation, then use the add token function in the accounts section. The signing device will display a confirmation request; approve it only after matching the address character by character on the device screen.
Perform these three checks in sequence:
- Confirm the network application is installed on the device.
- Verify the account for that network is visible in the overview.
- Check whether the token requires a custom contract address.
Missing native coins often indicate that the corresponding network application has not been installed on the hardware. Connect the device, open the manager section, and search for the network by name. Install the application, then return to the accounts tab and add the account. The device screen will ask for confirmation; press the physical button to approve. After synchronization, the balance should appear.
Follow these steps to add a missing network account:
- Connect the hardware and unlock it with the PIN.
- Open the manager and install the network application.
- Return to accounts and select add account.
- Choose the network from the list and confirm on the device.
Network upgrades or chain splits can temporarily remove a coin from the interface. When a blockchain undergoes a protocol change, the manufacturer may need to release an updated network application. Check the official release notes for the companion software and the device firmware. Do not attempt to add the coin manually during this period; wait for the official integration to resume normal visibility.
Privacy-focused coins or tokens with unusual derivation paths may require manual configuration. Some networks use non-standard address formats or require a specific account index. Consult the manufacturer’s official documentation for that network. If the documentation describes a custom derivation path, enter it in the advanced settings of the account addition screen. The device will display the derived address for verification before any transaction.
Finally, cross-check the manufacturer’s official list of integrated networks and tokens on its website. Third-party lists or forum posts may be outdated or incorrect. If the coin does not appear in the official list, the interface cannot manage it directly; you would need to use a different wallet that recognizes that blockchain. Never share the recovery phrase with anyone claiming to add a missing coin.
Q&A:
Which cryptocurrencies can I hold and send through Ledger Live?
Ledger Live works with a large set of coins and tokens, but the exact list depends on the app version and your device. Native accounts are available for Bitcoin, Ethereum, Solana, Cardano, XRP, Litecoin, Bitcoin Cash, Dogecoin, Polkadot, Kusama, Cosmos, Tezos, Tron, Polygon, BNB Smart Chain, Avalanche C-Chain, and others. Token support varies by network: ERC-20 tokens on Ethereum, BEP-20 tokens on BNB Smart Chain, SPL tokens on Solana, and similar standards on some other chains. Open Ledger Live, choose Add account, and search for the asset. If it appears, you can create an account and manage it with your Ledger device. If it does not appear, Ledger Live cannot manage that asset directly in the current release.
Why does a token show up in my Ethereum account but I cannot send it?
This often happens with ERC-20 tokens. Ledger Live may display a token balance because it reads data from the Ethereum network, yet sending that token requires the right token account and enough ETH for gas. Add the token account inside Ledger Live if the app offers it, then make sure the Ethereum app is open on your device and that the receiving address supports the same token standard. If Ledger Live does not list the token for sending, you can connect your Ledger device to a compatible third-party wallet, such as MetaMask or Rabby, and use that wallet to move the token. Always verify the contract address before you send anything.
Can I stake crypto in Ledger Live, and which assets support staking?
Staking in Ledger Live is available for selected networks, and the list changes as providers add or remove services. Common staking options include Ethereum, Solana, Cosmos, Polkadot, Kusama, Tezos, Tron, and Cardano, but not every asset can be staked directly in the app. Some networks require a minimum amount, a specific validator, or an unbonding period. For Ethereum, you may see options for pooled staking through a provider. For Solana, you can delegate to a validator from Ledger Live. Before you stake, check the fees, lockup rules, and reward rate shown in the app. If an asset is not listed under Earn or Stake, you may need to use a compatible third-party wallet or staking service that works with your Ledger device. Keep in mind that staking can involve slashing risk, lockup periods, and market price changes.
How do I add a new asset to Ledger Live if it is not in the default list?
Use the Add account button in Ledger Live and search for the asset by name or ticker. If the asset is supported, Ledger Live will guide you through installing the needed app on your Ledger device and creating an account. For tokens, you may need to add the parent network account first, then add the token account. If the search returns nothing, that asset is not supported for direct management in Ledger Live at that time. You can still use your Ledger device with other wallets that support the asset. For example, use MetaMask for many EVM networks, Phantom for Solana, Keplr for Cosmos chains, or a similar wallet for another network. The address and private keys remain protected by your Ledger device, but the third-party wallet controls the interface and transaction building.
What is the difference between an asset that Ledger Live supports natively and one that only works through a third-party wallet?
Native support means Ledger Live itself can create accounts, show balances, send, receive, and sometimes stake or swap the asset. The app has built-in integration for that coin or token, and your Ledger device signs transactions after you confirm them on-screen. Third-party wallet support means Ledger Live may not offer a full account interface for that asset. Instead, you connect your Ledger device to another wallet, and that wallet handles the display, address book, fee settings, and transaction construction. Your private keys stay on the Ledger device, so the third-party wallet never sees them. The trade-off is that you depend on that wallet’s own asset list, network support, and security practices. Before you use a third-party wallet, confirm that it supports the exact network and token standard you plan to use. A token on one chain may have the same ticker as a token on another chain but a different contract address and different risks.
Which coins and tokens can I manage in Ledger Live, and how do I check whether a specific asset is available?
Ledger Live works with a broad list of coins and tokens, and the list depends on the Ledger Live version and the network apps installed on your device. To check one asset, open Ledger Live, go to Accounts, choose Add account, and search for the coin or token by name or ticker. If the app offers an account for it, follow the prompts; if no result appears, Ledger Live does not currently provide an account for that asset. You can also compare against Ledger’s official supported-assets page. A hardware wallet may secure an asset through a third-party wallet while Ledger Live itself does not list that asset. Those are separate levels of support.
My ERC-20 token is not showing after I added my Ethereum account. Does that mean Ledger Live does not support the token, or did I miss a step?
First, confirm that the token sits on Ethereum mainnet and that your Ledger device has the Ethereum app installed. In Ledger Live, open Accounts, choose Add account, and search for the token by name, ticker, or contract address. Many ERC-20 tokens can be added as token accounts under the Ethereum account; some tokens are absent from Ledger Live’s token list, and those will not appear through the standard Add account flow; the Ethereum account itself can still work. Check that Ledger Live and device firmware are current, and compare the contract address against a block explorer so you are looking at the right token rather than a same-ticker copy on another chain. If the token remains missing, review Ledger’s official supported-assets page. Ledger Live may not track that token directly; in that case, a compatible third-party wallet connected to your Ledger device can often manage it while the keys stay on the device. Do not send tokens to an address from a different network just because the ticker matches.
