Sending crypto from Ledger means verifying the recipient address, choosing the correct blockchain network, and approving directly on the device.
The private key never leaves the Secure Element chip — only the signed transaction output reaches the blockchain, and every send requires Physical Confirmation.
| Send Component | Role | Risk if Wrong |
|---|---|---|
| Recipient Address | Destination wallet on the blockchain | Permanent fund loss |
| Blockchain Network | Chain that routes the transaction | Permanent fund loss |
| Asset App (on device) | Signing capability for the asset | Transaction fails |
| Network Fee | Payment to blockchain validators | Transaction gets stuck |
| Secure Screen | On-device verification display | Attacker substitution undetected |
Cold Storage SigningThe Secure Element isolates private keys inside a tamper-resistant chip. Even if the connected computer is fully compromised, an attacker can only observe the unsigned transaction request — the signing key stays inaccessible.
Three inputs must be verified before any send: the correct recipient address, a matching blockchain network, and a sufficient native token balance to cover the gas fee. Missing any one causes the transaction to fail or results in permanent loss.
| Asset to Send | App Required | Network |
|---|---|---|
| Bitcoin (BTC) | Bitcoin app | Bitcoin native |
| Ethereum (ETH) | Ethereum app | Ethereum mainnet |
| USDT / USDC (ERC-20) | Ethereum app | Ethereum |
| Solana (SOL) | Solana app | Solana native |
| BNB (BEP-20) | Ethereum app | BNB Chain |
| Cardano (ADA) | Cardano app | Cardano native |
| Common Mismatch | Result |
|---|---|
| USDT ERC-20 sent to TRC-20 address | Permanent loss |
| ETH sent to BNB Chain address | Permanent loss |
| USDC on Polygon sent to Ethereum deposit | Exchange-dependent — may not credit |
| BTC sent to ETH address | Permanent loss |
Sending a small test transaction before transferring large amounts is the most reliable way to verify address and network compatibility.
Unsigned transaction data goes from Ledger Wallet app into the Secure Element chip. The chip signs using the stored private key and returns only the signed output — the key itself never leaves the device.
| Security Feature | Ledger Hardware Wallet | Software Wallet |
|---|---|---|
| Key storage | Offline Secure Element chip | Internet-connected device memory |
| Transaction signing | Inside isolated chip | On exposed device memory |
| Malware key access | Not possible | Possible |
| On-device verification | Hardware display | Computer screen — manipulable |
| Physical approval | Required — button press | Not required |
The Secure Element carries EAL5+ certification for Nano S Plus and Nano X, and EAL6+ for Flex and Stax — the same standard used in biometric passports and bank cards.
Connect via USB-C cable and unlock the device with your PIN.
For example, the Ethereum app for ETH or any ERC-20 token.
Navigate to Accounts, choose the account and asset, then click Send.
Paste the destination address — never type manually — select the network if applicable, and enter the amount.
Pick Low, Medium, or High, then review the full summary — amount, address, network, and fee.
Check every character of the address on the hardware display, then press both buttons to broadcast.
Always Verify on the DeviceClipboard Malware can replace a copied address between paste and approval with no visible indication on the computer. The hardware display is the only surface that reflects what the Secure Element will actually sign.
| USDT Network | Standard | Avg Gas Fee (2026) | Speed |
|---|---|---|---|
| TRC-20 (Tron) | TRC-20 | Very low | Fast |
| BEP-20 (BNB Chain) | BEP-20 | Very low (~$0.01) | Fast |
| ERC-20 (Ethereum) | ERC-20 | ~$0.39–$0.67 | 1–5 min |
TRC-20 offers the lowest gas fee but requires the recipient to explicitly support Tron deposits. Ledger Wallet app lists USDT as separate assets per network — always confirm the destination network with the recipient before sending.
Log into the exchange, note the exact blockchain network, and copy the deposit address — never retype it.
If the exchange shows a tag, memo, or payment ID, note it separately.
Paste the address, match the network, enter amount and tag if required.
Confirm every detail on the hardware display, then press both buttons to broadcast.
Destination Tags MatterXRP, Stellar, BNB Chain, and EOS commonly require a destination tag or memo when sending to exchange addresses. Omitting it means the exchange receives funds that aren’t credited to any account.
| Fee Tier | Confirmation Speed | Best For | Risk |
|---|---|---|---|
| Low | Slower — minutes to hours | Non-urgent transfers | May stay stuck during congestion |
| Medium | Standard — minutes | Most everyday transfers | Balanced speed and cost |
| High | Fastest — seconds to minutes | Urgent transfers | Higher cost but reliable |
Bitcoin fees are measured in satoshis per byte. Ethereum uses Gwei under the EIP-1559 dynamic pricing model. Solana and BNB Chain fees stay consistently very low — fee tier selection matters most for Bitcoin and Ethereum transfers. Ledger itself charges no sending fee.
| Asset | Network | Avg Confirmation | Finality |
|---|---|---|---|
| BTC | Bitcoin | ~60 minutes | 6 blocks |
| ETH | Ethereum | 15 sec – 5 min | 12–15 blocks |
| USDC | Base | Seconds – 1 min | Fast |
| SOL | Solana | ~400 milliseconds | Near-instant |
| BNB | BNB Chain | ~3 seconds | Fast |
These are the two most common attack vectors targeting the address entry step. Both aim to replace the legitimate destination with an attacker’s address before authorization — the hardware display defeats both since it shows data generated directly from the Secure Element.
| Attack Step | What Happens |
|---|---|
| 1 | Attacker identifies a frequently used destination in the target’s history |
| 2 | Creates a wallet matching the first and last 4–6 characters |
| 3 | Sends a dust transaction to plant the fake address in history |
| 4 | Target copies from history — sends large amount to attacker |
| 5 | Verifying on hardware display before approval catches the substitution |
Always copy destination addresses directly from exchange deposit pages or official wallet interfaces — never from transaction history.
| Error | Symptom | Fix |
|---|---|---|
| Wrong Asset App open | “Please open [app]” prompt | Open the correct Asset App on the device |
| Gas fee too low | Transaction pending indefinitely | Speed up via fee bump or RBF |
| Wrong blockchain network | Funds not received | Permanent loss — verify before every transfer |
| Invalid destination address | Transaction rejected | Check address format matches the chain |
| Missing destination tag | Funds received but not credited | Contact exchange support |
Open Ledger Wallet app, connect the device, open the correct Asset App, click Send, enter the destination address and amount, select the fee tier, verify everything on the hardware display, then press both buttons to authorize.
Yes — this is mandatory, not optional. The hardware display shows the address the Secure Element will sign, making it the only display that can’t be altered by Clipboard Malware or Address Poisoning. If it doesn’t match, press the left button to reject.
Bitcoin takes roughly 60 minutes across 6 confirmations. Ethereum takes 15 seconds to 5 minutes. Solana confirms in about 400 milliseconds. BNB Chain and Tron confirm within seconds.
It’s permanent and irreversible on every blockchain. Ledger is non-custodial and cannot reverse any confirmed transaction — verifying every character on the hardware display before authorization is the single most important step.
For Bitcoin, use Replace-By-Fee to rebroadcast at a higher rate. For Ethereum, use the Speed Up option to raise the gas fee at the same nonce. Solana and BNB Chain transactions typically confirm without intervention.
Yes. Ledger can authorize through MetaMask via USB-C, WalletConnect-compatible dApps, or Electrum for Bitcoin. Every method routes signing through the Secure Element and requires Physical Confirmation on the hardware display.
