Overview
This guide explains how Bitcoin works with a ledger wallet, covering address types (legacy, SegWit, Taproot), how SegWit is configured, what Ordinals mean for wallet users, and safe ways to handle hard forks such as claiming Bitcoin Cash. The goal is practical: clear steps, security trade-offs, and real troubleshooting notes from hands-on testing. I believe that anyone holding cryptocurrency should understand the differences between addresses and how they affect fees, compatibility, and privacy.
(If you want a quick setup primer first, see getting-started-setup and ledger-live-download-install.)
Bitcoin address types: Legacy, SegWit, Taproot
Short answer: different addresses = different rules and fees. Longer answer follows.
- Legacy (P2PKH): older format, begins with a 1. Broad compatibility but higher fees.
- Nested SegWit (P2SH-P2WPKH): starts with a 3. Works with services that don’t understand native SegWit.
- Native SegWit (bech32/P2WPKH): starts with bc1. Lower fees and modern.
- Taproot (P2TR): newer format (bc1p...). Enables advanced scripts and smaller transaction sizes for certain uses.
| Address type |
Example prefix |
Compatibility |
Fee behavior |
| Legacy (P2PKH) |
1 |
Very compatible |
Higher average fees |
| Nested SegWit (P2SH) |
3 |
Compatible with older services |
Lower than legacy |
| Native SegWit (bech32) |
bc1 |
Modern wallets & exchanges |
Lowest typical fees |
| Taproot (P2TR) |
bc1p |
Newest; increasing support |
Potential savings on advanced scripts |
Why does this matter for a ledger wallet? The device stores the private keys and can derive multiple address types depending on the derivation path and account you add in your management software (for example, in Ledger Live or a third-party wallet). Different address types map to different derivation standards (BIP-44, BIP-49, BIP-84, BIP-86, etc.).
SegWit on your ledger wallet: setup & troubleshooting
How to add a SegWit Bitcoin account (high-level):
- Open your device and unlock it.
- Launch the Bitcoin app on the device.
- In Ledger Live (or a compatible wallet), choose Add Account → Bitcoin → select the address type (SegWit/native SegWit) → confirm.
If the account creation fails or your ledger wallet shows zero balance bitcoin, check these points:
- Did you pick the correct address type? Funds sent to a bech32 address won't show up under a legacy account (they're different derivation paths).
- Is the Bitcoin app open on the device during sync? Some desktop apps require the device to be unlocked and app-open.
- Are you connected to the correct network (mainnet vs testnet)? Sounds basic, but it happens.
- Have you added the account under the right derivation path? See advanced-derivation-paths.
If you still see a zero balance, follow the troubleshooting checklist in zero-balance-and-sync-issues and the firmware checklist at firmware-update-verify.
Ordinals and inscriptions: what a hardware wallet can (and can't) do
Ordinals and inscriptions place arbitrary data onto individual sats (satoshis). That means the blockchain records the inscription, but a hardware wallet itself doesn't index or display that content. In my testing, the device will sign a transaction that spends a UTXO whether it contains an inscription or not — it has no way to preview the inscription.
Practical steps to reduce risk:
- Use a dedicated account/address for receiving inscriptions. Don't mix those UTXOs with your spending funds.
- Use a third-party wallet that indexes inscriptions in watch-only mode to view them (see third-party-compatibility).
- Exercise coin control: never sweep all UTXOs blindly if one may contain an inscription you intend to keep.
And yes, you can manage inscription UTXOs with a ledger wallet — but the viewing and indexing will come from external tools, not the device itself.
Forks and claiming forked coins (Bitcoin Cash example)
When a chain forks, you may technically hold coins on both resulting chains. That does not mean you should rush to "claim bitcoin cash ledger" by pasting your seed into a random website.
Safe workflow (recommended):
- Update and verify your device firmware first (see firmware-update-verify).
- Create a fresh receiving address on a new account and move your original-chain BTC there (this protects the private keys used on the forked chain).
- Use a watch-only setup (export the xpub) or an air-gapped signing process to interact with the fork chain later. See air-gapped-signing.
- If you do claim coins on the forked chain, use a new device or an offline signing method; never paste your seed phrase into an online wallet.
Splitting BCH from BTC? The term "split" usually means moving one chain's coins separately after the fork. The safest path is to move your BTC first (as above). If you must sign on the forked chain, do so on a device you don't use for everyday BTC, and make sure you understand replay protection and how the fork implemented it.
Multiple accounts and why your bitcoin address changed
Bitcoin wallets use hierarchical deterministic derivation. That means each time you request a receive address, the wallet often gives a new one (for privacy). So, "why did my bitcoin address change?" Because address rotation is intended.
If you want multiple wallets or accounts (for savings, spending, ordinals, taxes), create separate accounts in Ledger Live or use different derivation paths. Some users ask about "multiple bitcoin wallets ledger nano s" — yes, a single hardware wallet supports multiple accounts and multiple address types. Manage them deliberately so you know which holds what.
See multiple-accounts-and-wallets and privacy-addresses-utxo for workflows.
Security notes: passphrase, firmware, and backups
- Seed phrase rules: 12 vs 24 words (BIP-39) — longer is more entropy, but both are supported by many wallets. See seed-phrase-basics.
- Passphrase (the optional 25th word) adds a hidden account. I use it sparingly (and documented offline). Be aware: if you forget the passphrase, there is no recovery.
- Firmware: always verify firmware signatures and follow firmware-update-verify. Updates patch holes and add features.
- Backups: use metal backup plates and consider SLIP-39/Shamir for distributed recovery. See backup-metal-slip39 and shamir-slip39-guide.
But don't rush into complex setups without testing restores (on a spare device or in a simulated recovery). What I've found: a backup is only useful if you can restore from it reliably.
FAQ
Q: Can I recover my crypto if the device breaks?
A: Yes — with the seed phrase (recovery phrase). Store that phrase offline and practice a restore process. See recovery-when-device-breaks.
Q: What happens if the company goes bankrupt?
A: Your private keys are yours if you use a non-custodial hardware wallet. The company’s status doesn't change your seed, but support and firmware updates could be affected. See company-bankruptcy-and-business-risk.
Q: Is Bluetooth safe for a hardware wallet?
A: Bluetooth has an attack surface. For everyday transactions, it is often convenient and reasonable, but for very large, long-term holdings consider USB or air-gapped signing. See walletconnect-bluetooth and connections-usb-bluetooth-nfc.
Q: My ledger wallet shows zero balance bitcoin — what now?
A: Confirm the right account/address type, open the Bitcoin app on-device during sync, check derivation paths, and follow the steps in zero-balance-and-sync-issues.
Conclusion & next steps
Managing Bitcoin with a hardware wallet involves small but meaningful choices: which address type to use, whether to enable a passphrase, how to separate inscription UTXOs, and how to claim forked coins safely. In my testing, deliberately separating accounts (one for spending, one for long-term storage, a third for ordinals) reduces accidental loss.
If you’re ready, start with bitcoin-setup and read the step-by-step walkthroughs at walkthrough-nanos-step-by-step or multiple-accounts-and-wallets. And if you need help troubleshooting, check ledger-live-troubleshoot-updates and common-mistakes.
Want a printable checklist for secure fork-claiming or Ordinals handling? See the linked pages above and consider creating a simple written plan before you sign any transaction.
