Quick primer
This page focuses on day-to-day transactions: sending, receiving and what happens when a wallet gives you the same address twice. I write from hands-on testing over several months and from daily use since 2017. Expect clear steps, security checks you can actually use, and links to setup, firmware and backup guides.
(Image placeholder: hardware wallet screen showing a receive address)
How sending works (ledger wallet send bitcoin)
In short: the companion app builds the transaction, the hardware wallet signs it inside its secure element, and you confirm details on the device screen before anything is broadcast. The private keys never leave the hardware wallet.
Step by step: how to send with ledger
- Open your desktop or mobile wallet integration and unlock the account you use for Bitcoin. (If you need setup directions, see nano-x-setup.)
- Create a new transaction: paste the recipient address, enter the amount, and choose a fee.
- Initiate the send. The wallet will ask you to connect and open the Bitcoin app on your hardware wallet.
- On the device you will see a summary: asset, amount, fee, and (critically) the receiving address. Verify each line.
- Press the physical buttons to approve the transaction. Confirmations are local. This is where you physically confirm the send.
Verify everything. Short sentence. Always double-check the full address on the device, not just on your computer screen. And if anything doesn’t match, cancel and start over.
What I've found: most mistakes happen when users trust only the host app. The device is your last line of defense. Confirm transaction ledger device every time you send.
Receiving crypto and XRP destination tags (ledger wallet receive xrp destination tag)
Receiving is usually simpler, but there are a few gotchas.
- For Bitcoin and most coins: click Receive in the companion app, connect the device, and accept the address shown on-screen. The hardware wallet will display the same address; confirm it matches what the app shows.
- For XRP (Ripple): many exchanges and custodial platforms require a destination tag. A destination tag is an extra numeric identifier attached to the transfer. If the recipient requires a tag, you must provide it in the memo/destination-tag field of the sending platform. If you forget the tag, funds sent to an exchange can become difficult to recover.
Example flow for XRP:
- Obtain the receiving address from the platform or your self-custody account.
- Note the destination tag (a number).
- Initiate the transfer and paste both address and tag into the sender’s form.
Destination tag xrp ledger handling varies by wallet front-ends. Always confirm with the recipient service before sending.
Address changes: why addresses change and how to force a new one (ledger nano s wallet address change)
Why do addresses change? Modern wallets use hierarchical deterministic (BIP-32/BIP-44/BIP-84) derivation so each receive request moves to the next unused index. This improves privacy and prevents address reuse.
If the wallet keeps showing the same address, possible reasons:
- The address hasn't been used yet, so the app still treats it as the current receive address.
- The companion app is caching an address or showing an account that hasn’t incremented the receive index.
How to get a new address (safe, general steps):
- In the companion app, use Receive and ask for the next address. Some apps show a small link or button like Show another address or Next address. If you don’t see that, start a new sub-account or create a new account inside the app.
- If you absolutely must force a different derivation index (advanced users only), use a trusted wallet explorer or advanced settings to change the receive index. This is not for beginners — you can confuse your address history.
But if you’re searching for ledger nano wallet address change force, stop and ask: do you really need to force it? Creating a second account inside the app is safer and simpler.
If you’re stuck, check nano-x-setup or troubleshooting-not-detected for more details.
Confirming transactions on the device (confirm transaction ledger device)
The device display is canonical. Always read the full recipient address, the amount, and the fee on the screen. Don’t rely on a green check in the desktop UI alone. If the on-device address differs from the host, reject the operation.
Tip: scroll slowly across the address on the device and compare the first and last 8–10 characters with the host. That catches many tampering attempts.
Bluetooth vs USB day-to-day UX and security
Bluetooth gives mobility and a cleaner phone experience. USB is simpler and slightly more conservative from a security perspective. Which one you choose depends on your threat model.
- USB: direct connection, no radio. Good for desktop-first users.
- Bluetooth: convenient for mobile setups and on-the-go. But it increases the attack surface (replay attacks are rare and mitigations exist). For a deep dive see connectivity-bluetooth-usb.
I prefer USB indoors and Bluetooth when I’m moving between apps on my phone. That’s personal preference, not a rule.
Common mistakes and quick troubleshooting
- Forgetting the destination tag on XRP transfers. Ouch. Recoveries are a pain.
- Sending small test transactions? Do it. Testing with tiny amounts can save you from big mistakes.
- Reusing addresses for privacy-sensitive funds. Try to request a fresh address when you can.
If the device isn’t detected or an address won’t update, try reconnecting, restarting the companion app, and checking firmware status. Firmware issues are where mistakes can happen; follow how-to-update-firmware-steps and verify signatures via firmware-updates-verification.
Need to recover after loss or breakage? See recover-if-broken and seed-phrase-management.
Mini comparison: address and connection behavior
| Feature |
Nano X (Bluetooth + USB) |
Nano S (USB only) |
Air-gapped (QR/SD) |
| Connection types |
Bluetooth, USB |
USB |
QR/SD (no radio) |
| Address generation |
Derived on host, confirmed on device |
Derived on host, confirmed on device |
Derived and displayed offline |
| Confirm on device |
Yes (screen + buttons) |
Yes (screen + buttons) |
Yes (display or QR) |
| Battery |
Has battery |
No battery |
No battery |
(Comparison is illustrative. See comparison-nano-s-plus for a deeper feature-by-feature breakdown.)
Who this workflow is for (and who should look elsewhere)
Who this suits:
- People who move funds occasionally and want strong non-custodial security.
- Users who like a phone+desktop workflow with a visible on-device confirmation.
Who should look elsewhere:
- Users who want fully air-gapped signing without any radio. (See air-gapped guides.)
- Users who prefer a multisig-only strategy for very large holdings; see multisig-setup for alternatives.
FAQ — real user questions
Q: Can I recover my crypto if the device breaks?
A: Yes — with your seed phrase and recovery steps. Refer to recover-if-broken. Always store your seed phrase safely (see seed-phrase-management).
Q: What happens if the company goes bankrupt?
A: Your private keys are yours. The company’s business outcome doesn’t change your seed phrase. See company-bankrupt for details.
Q: Is Bluetooth safe for a hardware wallet?
A: Bluetooth increases the attack surface slightly, but the on-device confirmations and secure element prevent private-key leakage. Read more at connectivity-bluetooth-usb.
Conclusion and next steps / CTA
Daily sending and receiving work smoothly once you build a habit: always verify the on-device address, confirm transaction ledger device, and treat destination tags with care. If you want a guided setup, check the full setup walkthrough at nano-x-setup, reinforce backups at seed-phrase-management, and make sure your firmware is current via firmware-updates-verification. For comparisons and deeper reads, visit comparison-table and where-to-buy-safely.
Safe transactions start with small tests and consistent checks. But don’t let fear freeze you — practical habits protect your crypto over the long run.
