Which coins and tokens the app can hold for you

How support actually works

Three independent layers have to line up before you can see and spend a particular asset:

1. The device firmware must know how to derive keys for that network and display its transactions. This is the hard constraint: without firmware support, no app version can help.
2. The app must know how to build, broadcast and display that network's transactions, and where to fetch its data.
3. Your setup — the app version you installed and whether you are on the desktop build or the web build — has to support the pair. A small number of networks and features arrive on desktop first.

Because all three move independently, any list published on a website — including this one — is a snapshot. The list inside the app is generated from what your actual device and app can do right now, which makes it the only one worth trusting for a decision.

The main asset families

Rather than a list that goes stale between releases, it helps to know the categories that coverage falls into and what each one feels like in practice.

Two consequences worth internalising. First, hardware wallet support is not the same as "supports everything a phone wallet does" — models differ, and older models are naturally the last to gain new networks. Second, an asset appearing in the app is a statement about key derivation and transaction building, not a recommendation. Nothing about support implies an opinion on the asset.

Accounts, addresses and address types

One account per coin, or several per purpose

An account in the app is a set of addresses belonging to your wallet for one network. You can create more than one per coin — a common arrangement is a savings account that receives occasionally and a spending account for day-to-day use. Because each account has its own addresses, the separation is real on the blockchain rather than a label applied afterwards.

Address types on Bitcoin and similar chains

UTXO chains have evolved through several address formats, and the app lets you choose where relevant:

• Legacy — the earliest format. Widest compatibility with ancient services, highest transaction fees.
• Nested SegWit — a compatibility middle ground from the transition period.
• Native SegWit — the sensible default for most people: lower fees, wide support.
• Taproot — the newest format, offering the best fee behaviour in some situations and improved privacy properties. Support depends on both the sending and receiving services.

If you are unsure, create one account of each type you need and test with a small amount first. Mixing address types inside one account is not possible by design, and moving between accounts later is an ordinary on-chain transaction with an ordinary fee.

Fresh addresses, always

Receiving generates a new address each time you ask. This is not cosmetic: address reuse is one of the main ways on-chain analysis ties together holdings you intended to keep separate. Handing out a fresh address costs nothing.

Tokens on smart-contract networks

Tokens are not separate networks. A token like an ERC-20 stablecoin or governance token lives on an Ethereum-family chain and is identified by a contract address. In the app, tokens appear as entries under the account of the network that hosts them, and sending one is a transaction on that network — paid for in that network's own coin.

Things that surprise people:

• You need the network's coin for fees. Holding a token with no ETH to pay gas means you cannot move it. This is the single most common stuck-token problem.
• Not every token is displayed automatically. The app recognises standard tokens, but long-tail ones may need to be added by contract address — or may simply not be tracked.
• Spam tokens are normal. Airdropped junk tokens sent to active addresses are an advertising and phishing channel. Ignore them; never visit a link or interact with a contract because a token appeared in your account.
• A wrong contract address is a different token. Verify contract addresses from a source you trust, not from a message that arrived with the tokens.

Staking and rewards

On supported proof-of-stake networks the app can build staking, unstaking and reward operations, with the device signing each one. Availability varies by network and by model, and the set of networks offering staking changes with releases.

Before you stake anything meaningful, understand these points:

• Staked funds are still yours, but they may be locked for a period, so you cannot always exit at will.
• Some staking routes delegate your coins to an operator whose track record and commission matter. Choosing one is an investment decision, not a setting.
• Rewards are income. In most jurisdictions they are taxable as income when received, on top of capital gains later. Talk to an accountant rather than guessing — the app does not do this for you.
• Unstaking is a transaction. It can cost a fee and a network-imposed wait. Plan around it rather than discovering it during a price move.

What the app does not manage

• Balances held on exchanges or custodial apps. Those are the provider's, not your wallet's. The app cannot see or move them, and no recovery backup of yours has any effect on them.
• Assets on networks your firmware does not support. Often there is a workaround via a different wallet that supports the same device, but that is a different tool with its own interface and risks.
• Wrapped and bridged representations. A wrapped token is a claim issued by a smart contract. Holding it involves trusting that contract, and the underlying asset is not in your wallet. Support for a network does not imply support for every wrapper on it.
• NFT marketplaces and DeFi positions. The app is a wallet, not a marketplace or a yield dashboard. Borrowing, lending and liquidity positions generally happen elsewhere and carry contract risk.
• Wallet staking or pass-through products offered by third parties. Those are counterparty arrangements, and your keys never see them.

The principle to carry away: your hardware wallet controls what its backup controls. Anything held elsewhere is somebody else's promise, however stable it has been so far.

Checking before you move funds

1. Update the app and the firmware first. New support arrives in releases, and an old app version will not offer networks your device already handles.
2. Connect the device and open the add-account flow. If the network is listed, you have support; if it is not, stop there.
3. Add the account and generate one receive address. Confirm the app and the device screen show the same address.
4. Send a small test amount from wherever the funds currently are. Wait for it to appear with confirmations.
5. Send a small test out to an address you control, and check the fee was reasonable. Only then move the bulk.
6. Keep the backup situation in mind — moving assets to a new network does not change what your recovery words restore. One backup covers everything the device derived, for every coin.

Keeping support current

• Update the app when it asks. Support for new networks and fixes for existing ones ship there.
• Update firmware deliberately, with a backup in place — see the security guide for the checks that matter.
• Read release notes for changes to networks, address types and staking availability. Deprecations happen quietly.
• Treat third-party "we support X" claims with care. Verify against the app itself rather than a blog post, including ours.

Next steps