Bitcoin Address Types & Hardware Wallets: SegWit, Native SegWit, and Change Addresses
Why address types matter for Bitcoin on a hardware wallet
If you hold Bitcoin in self-custody with a hardware wallet, address type decides two practical things: fees and compatibility. Shorter witness data (SegWit) reduces transaction size and therefore fees. Different address formats also affect whether older services accept deposits. I believe most users will benefit from using modern address types, but there are trade-offs.
A hardware wallet keeps private keys on a secure element so addresses are derived from your seed phrase and (optionally) passphrase. The device displays the exact address you should use. Verifying that address on the device screen is the single most effective defense against malware that alters addresses on your computer.
Common Bitcoin address types (quick reference)
Here are the address types you'll encounter. I prefer concrete examples, so the prefixes and short trade-offs are shown.
| Address type |
Example prefix |
What it means |
When to use |
| Legacy (P2PKH) |
1... |
Old-style Bitcoin addresses. Widely compatible, larger fees. |
If you must send to a very old wallet or service that doesn't support SegWit. |
| Wrapped SegWit (P2SH-P2WPKH) |
3... |
SegWit benefits, but inside a P2SH wrapper for compatibility. |
Good default when unsure about recipient compatibility. |
| Native SegWit (bech32, P2WPKH) |
bc1... |
Modern format offering the smallest fees and clearer signing semantics. |
Best for lower fees and modern services (but check acceptance). |
A few technical names (BIPs) tie these to derivation paths: BIP-44 (legacy), BIP-49 (wrapped SegWit), BIP-84 (native SegWit). You don't need to memorize the numbers; just know that address type = different derivation path = different addresses.
Why your hardware wallet may show different addresses
Short answer: because it should. Longer answer: a few different systems are at play, and mixing them up makes people panic.
Receive vs change addresses: When someone sends you BTC, the wallet often creates a fresh "receive" address to avoid address reuse. After you send a transaction from that account, the wallet will also create a "change" address (an internal address that returns change back to your account). Change addresses are normal and are part of how Bitcoin's UTXO model works.
Different account types: If you create a new account in your wallet app (for example, an account using native SegWit instead of wrapped SegWit) the addresses will look totally different because derivation paths differ.
Multiple interfaces: The companion app may show an address while the hardware device shows another during verification (for example, the app shows a bech32 address but the device shows a wrapped SegWit one). This usually means you selected a different account type or the app created an address using a different derivation path. Verify on-device and reconcile the account type in your app settings.
But don't panic when an address changes — the protections exist to improve privacy and reduce reuse. And if an address changes and you didn't expect it, follow the troubleshooting checklist below.
Step-by-step: How to receive Bitcoin safely on a hardware wallet
How to (step by step) receive BTC with confidence.
- Open the Bitcoin account in your wallet companion app. (If you need help with initial setup, see the setup guide and nano-s-setup-step-by-step.)
- Select the account that matches the address type you intend to use (legacy, wrapped SegWit, or native SegWit).
- Click "Receive" in the app — the app will generate an address and show a QR code.
- Immediately verify that same address on your hardware wallet screen. The device is the authority. If the strings differ, do not proceed.
- Copy or share the address (or the QR). Wait for the transaction and confirmations.
Why verify on the device? Because the private keys never leave the secure element, and the device's screen is the only place you can trust to show the real address derived from your keys (malware can swap addresses in the app). If you want extra security, use an air-gapped signing workflow or check the derivation path in the app.
If your device asks to confirm the address type or account index, make sure it matches what you expect. Firmware updates can change UX; if your device behaves unexpectedly after an update, consult /firmware-updates-bootloader.
Should you use SegWit or Native SegWit? (practical guidance)
Short: Native SegWit (bech32) is generally more fee-efficient and future-friendly. But compatibility matters.
- Use native SegWit if the sender/exchange/service accepts bc1 addresses. You'll save on fees and benefit from clearer signature encoding.
- Use wrapped SegWit (P2SH) when the counterparty might not accept bech32.
Example: If a particular exchange or custodial service only accepts P2SH, send there using a P2SH-wrapped address. If you're moving funds between your own accounts or to a modern exchange, go bech32.
Advanced: derivation paths, passphrase effects, and multisig notes
A few advanced points for people building secure setups.
Derivation paths: Every address type has a derivation path. Switching address type creates a different sequence of addresses. If an account looks empty after you switch types, you likely selected a different derivation path. Check the companion app's account settings or consult the wallet-integration-hub for compatibility notes.
Passphrase (the 25th word): Enabling a passphrase creates a hidden account. Addresses from a hidden account will be entirely different from your main account. If you use a passphrase, document your personal process carefully (see /passphrase-25th-word).
Multisig: Multisig setups can use any address type that the signers’ software supports. Multisig helps reduce single-point-of-failure risk but adds complexity (see /multisig-setup).
Troubleshooting checklist (quick fixes)
- Address on app ≠ address on device: Do not send. Reconnect, re-open the Bitcoin app on the device, and verify again.
- Addresses change after sending: Normal — these are change addresses. Check transaction outputs in a block explorer.
- Account empty after switching type: Switch back to the original address type (derivation path) or check /multiple-accounts.
- Device behavior odd after update: Check /firmware-updates-bootloader and ensure the firmware was signed.
- Suspect a compromised computer: Use an air-gapped flow for receiving or verify addresses on another trusted machine.
FAQ: real user questions about addresses and hardware wallets
Q: Can I reuse an address?
A: You can, but avoid it — reuse reduces privacy and makes transaction graph analysis easier. Modern best practice is to use a fresh receive address for each incoming payment.
Q: Will I lose funds if my device shows a different address?
A: No — funds belong to private keys derived from your seed phrase. Different displayed addresses typically indicate different derivation paths or change addresses. But if the device and app disagree, pause and troubleshoot before sending.
Q: Is bech32 safe to use?
A: Yes. Bech32 is a modern address format with benefits in fee efficiency and error detection. Just confirm the recipient accepts it.
Q: What if I enabled a passphrase and now addresses differ?
A: A passphrase creates separate hidden accounts. If you forget which passphrase you used, those funds may be inaccessible. See /passphrase-25th-word and /seed-phrase-management for recovery planning.
Conclusion and where to go next
Different-looking addresses are usually normal. They come from deliberate design choices that improve privacy and reduce fees. Verify every receive address on your hardware wallet screen, match the account type you intended, and keep firmware and companion apps up to date (check /firmware-updates-bootloader for guidance).
If you want a guided walkthrough of the initial setup and receive flow, see the setup-unboxing and the nano-s-setup-step-by-step pages. For troubleshooting transaction or sync issues, visit /receive-send-issues and /troubleshooting-index.
Ready to apply this? Start by opening your Bitcoin account in the companion app, choose the address type you prefer, and always confirm the address on the device screen before sharing it.
