Bitcoin Derivation Paths Explained (BIP44, BIP49, BIP84)
Why one seed phrase shows different Bitcoin addresses (1…, 3…, bc1…). Derivation paths explained — and why they matter when you recover a wallet.
A confusing moment in self-custody: you restore the right seed phrase, but the address — or the balance — doesn't look familiar. Nine times out of ten, the seed is fine and the culprit is the derivation path.
One seed, many addresses
A seed phrase doesn't produce a single address. It produces a whole tree of keys (this is BIP32). A derivation path is the coordinate that selects one branch of that tree. It looks like this:
m / 84' / 0' / 0' / 0 / 0
purpose coin acct change index
- purpose — which address standard (44, 49, 84, 86…).
- coin — 0 for Bitcoin, 60 for Ethereum.
- account — lets you keep separate sub-wallets.
- change — 0 for receive addresses, 1 for internal change.
- index — the 1st, 2nd, 3rd… address.
Change the path and you get a completely different — but equally valid — address from the same words.
The three Bitcoin address types
| Standard | Path prefix | Address looks like | Name |
|---|---|---|---|
| BIP44 | m/44'/0'/0'/0/i | 1… | Legacy (P2PKH) |
| BIP49 | m/49'/0'/0'/0/i | 3… | Wrapped SegWit (P2SH) |
| BIP84 | m/84'/0'/0'/0/i | bc1… | Native SegWit (P2WPKH) |
(Newer wallets may also use BIP86 Taproot, bc1p….) They're all your money —
just encoded differently, with different fees and features. Native SegWit (bc1…)
is the modern default because of lower fees.
Ethereum keeps it simple
Ethereum and most EVM chains use a single path, m/44'/60'/0'/0/i, and one address
format (0x…). One reason ETH recovery is more straightforward than Bitcoin: there's
only one address type to match.
Why this matters for recovery
When you recover a phrase and want to confirm it with a known address, you must
derive that address on the right path. Paste a bc1… address and check it against
BIP84; paste a 1… address and check BIP44. Our recovery tool auto-detects
the address type from its prefix and derives the matching format — and it derives
all of them for display so you can compare. That's also why a recovered phrase can
look "empty": you may simply be on the wrong path.
If your restored wallet shows nothing, before panicking, check:
- The address type (Legacy vs SegWit vs Native SegWit).
- The account index (account 0 vs 1).
- Whether a passphrase was used.
Takeaway
Derivation paths are why "the same seed phrase" can show many faces. For recovery, match the path to your address — or let a tool that derives every common format do it for you. Start from the recovery guide if you're mid-recovery.