This article explains how to use a Ledger bitcoin wallet for receiving, sending, and managing UTXOs — with a focus on address types (Legacy, P2SH-wrapped SegWit, and Native SegWit), how the device interacts with software wallets, and practical coin-control options. I’ve spent months testing hardware wallets and have used them with both the manufacturer’s companion app and third-party software. What I’ve found: the device keeps private keys offline while host apps manage UTXOs.
Who this is best for
Who should look elsewhere
(See related setup and recovery guides: [setup-initial], [restore-recovery].)
Bitcoin uses the UTXO (unspent transaction output) model: each incoming payment creates an output you later spend. The hardware wallet stores private keys in its secure element. Transaction construction happens in the host app (companion desktop/mobile wallet); the unsigned transaction is sent to the device for signing, and the device returns signatures only — private keys never leave the hardware wallet (see [security-architecture]).
Short example. You receive three payments to your account. Those are three UTXOs. When you send, the wallet chooses which UTXOs to spend and may create a change UTXO. Simple.
Why UTXO behavior matters: fee estimation, privacy, and the ability to consolidate outputs. Want granular control? You’ll need a wallet that exposes coin control.
(For derivation details and address generation, this site’s [derivation-paths] and [seed-phrase] pages are helpful.)
| Address type | Example prefix | Compatibility | Trade-off |
|---|---|---|---|
| Legacy (P2PKH) | 1... | Universally accepted | Larger tx size → higher fees |
| P2SH-wrapped SegWit (P2SH-P2WPKH) | 3... | High compatibility (older services) | Moderate fee savings vs legacy |
| Native SegWit (Bech32, P2WPKH) | bc1... | Best fee efficiency; some old services may not accept | Best for lower fees and modern wallets |
Bech32 (bc1) addresses are defined in BIP-173 and are the recommended modern format for many wallets and services (see BIP-173: https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki). Native SegWit typically produces smaller serialized transactions, which means lower fees compared with legacy addresses.
Step-by-step: receive bitcoin
Why verify on-device? Host software can be compromised. The on-device screen is the final ground truth for which address is actually controlled by your keys.
How to check Ledger wallet balance
Step-by-step: send bitcoin (simple flow)
(If you need step-by-step for initial setup or firmware safety checks, see [setup-initial], [firmware-updates], and [verify-firmware].)
Ledger’s companion app emphasizes simplicity and does not expose granular coin control (this is by design for most consumer workflows). But what if you want to: 1) avoid consolidating small UTXOs, 2) optimize fees, or 3) manage privacy? Use a third-party wallet that supports hardware wallets and coin control, such as Electrum. Electrum’s hardware wallet docs explain how to use a hardware wallet as a signer while Electrum handles UTXO selection (https://electrum.readthedocs.io/).
Step-by-step (conceptual) to use a hardware wallet with Electrum
And yes, this is more complex than the default app. But it gives precise control over which UTXOs you spend.
A passphrase (often described as a 25th word) creates hidden wallets beyond the seed phrase. It’s a valid privacy and security tool: different passphrases yield completely different addresses derived from the same seed phrase (BIP-39 + passphrase behavior). But the downsides are severe if mismanaged: lose the passphrase and you lose access to funds. I believe the passphrase should only be used by experienced users with tested recovery procedures (metal backups, documented procedures). See [passphrase-25th-word] and [backup-and-recovery].
If you’re adding a bitcoin account in the host app, you’ll usually choose which address type to use for that account. For broad compatibility today, many users pick P2SH-wrapped SegWit or natvie SegWit for lower fees. But compatibility with a specific exchange or service should be confirmed first.
(Reference: BIP-141, BIP-173; general SegWit background: https://bitcoin.org/en/glossary/segwit)
But remember: usability matters. If a workflow is so complicated you won’t use it, it won’t protect you. Balance security with procedures you can maintain.
Q: Can I recover my crypto if the device breaks?
A: Yes — with your seed phrase and optional passphrase you can restore on a compatible wallet (see [restore-recovery]). Test restores on a new device or emulator before relying on them in an emergency.
Q: What happens if the company goes bankrupt?
A: Your keys belong to you. Hardware vendors provide tools to manage keys; bankruptcy doesn’t erase your seed phrase or prevent restores to other compatible wallets. See [company-risk] for scenarios and planning.
Q: Is Bluetooth safe for a hardware wallet?
A: Bluetooth is convenient but increases the attack surface compared with USB. For long-term cold storage, prefer a wired or air-gapped workflow if possible. See [connectivity-usb-bluetooth-nfc].
Understanding addresses, UTXOs, and SegWit choices makes a big difference in fees, privacy, and recovery options when you use a Ledger bitcoin wallet. In my testing, confirming addresses on-device and using a third-party wallet for coin control were the two habits that improved safety and flexibility the most.
Ready for hands-on setup or recovery testing? Start with the initial setup and recovery walkthroughs: [setup-initial], [restore-recovery], and if you want UTXO control, read [third-party-wallets] and the Electrum guidance.
(Interested in multi-signature for inheritance or higher security? See [multisig] and [cold-storage-strategies].)