A derivation path is the human-readable roadmap that an HD (hierarchical deterministic) hardware wallet follows to generate your private keys and, therefore, addresses. Think of it as the GPS coordinates for each account and address derived from your one seed phrase. Derivation paths are defined by standards such as BIP-32, BIP-39 and BIP-44 (links below) and look like this:
m/44'/0'/0'/0/0
Short sentence. Long one that explains: m (master seed), 44' (purpose — BIP-44), 0' (coin type — Bitcoin is 0, Ethereum is 60), account index, change (0 = external/receiving, 1 = internal/change), and address index (the individual address). For formal specs see BIP-32, BIP-39, BIP-44: https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki, https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki, https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki.
(Placeholder: diagram showing m/44'/coin_type'/account'/change/index labeled.)
I believe understanding this stack explains why one seed phrase can produce many different address sets depending on the path chosen.
| Purpose / Standard | Example path (Bitcoin) | Address format | Typical use case |
|---|---|---|---|
| BIP44 (legacy) | m/44'/0'/0'/0/0 | P2PKH (1...) | Older wallets, backwards compatibility |
| BIP49 (wrapped segwit) | m/49'/0'/0'/0/0 | P2SH-P2WPKH (3...) | Services that prefer backwards-compatible segwit |
| BIP84 (native segwit) | m/84'/0'/0'/0/0 | bech32 (bc1...) | Modern wallets minimizing fees and improving privacy |
| Ethereum (BIP44 coin_type 60) | m/44'/60'/0'/0/0 | EVM address (0x...) | Ethereum and most ERC-20/DeFi wallets |
Sources: BIP-44, BIP-49, BIP-84 (see https://github.com/bitcoin/bips for each BIP). Note that some blockchains (e.g., Solana, Cardano) use ed25519/SLIP-0010 derivation variants (see SLIP-0010: https://github.com/satoshilabs/slips/blob/master/slip-0010.md). But paths can vary by app.
Short answer: different wallets can use different derivation paths or address formats, and that produces different addresses from the same seed.
Common causes:
What do you do when an address you used earlier no longer appears in your wallet? Read on.
And yes, seeing a new address in the UI while your balance is unchanged is often normal (many wallets rotate receiving addresses for privacy).
But remember: do not enter your seed phrase into untrusted devices or websites. Ever.
Ethereum uses the BIP44 coin_type 60 by convention (registered in SLIP-0044: https://github.com/satoshilabs/slips/blob/master/slip-0044.md). Many hardware wallets and companion apps show multiple Ethereum accounts by incrementing the address_index (m/44'/60'/0'/0/0, m/44'/60'/0'/0/1, ...). This is why you might see “multiple ETH wallets on ledger” in the UI — they are multiple addresses derived from the same seed under the same path.
In my testing, I often restore a seed and then scroll through a dozen account entries before finding the one used for an older transaction. It’s tedious, but that’s how HD derivation works.
If you connect your hardware wallet to a browser extension (see metamask-setup) or a third-party app (third-party-wallets), make sure the app is set to use the same derivation path and shows advanced account indexes.
Multisig setups depend on matching derivation paths and extended public keys (xpubs). If one cosigner uses BIP84-derived xpubs and another uses BIP44, the resulting multisig addresses will not match and the wallet will not recognize funds. See multisig-compatibility and multisig-setup for detailed guidance.
When setting up or restoring a multisig wallet, confirm the derivation path and script type with every cosigner before proceeding.
And don't panic if addresses don't appear — usually the keys are still there; the UI just needs the right path, passphrase, and indexes.
Q: "Ledger wallet address changed—can I still use my old address?" A: Yes. Any address derived from your seed phrase (and passphrase, if used) remains valid forever. If an address disappears from the UI, funds sent there are still accessible when you restore the same seed with the same derivation path and passphrase. If the address belonged to a different path or passphrase you don’t control, you cannot access those funds.
Q: "Why did my address change when I restored the device into a different app?" A: Because the app likely used a different derivation path or account index, or you omitted the passphrase. Try restoring again with advanced options or use an app that supports custom derivation paths (advanced-cli or third-party-wallets).
Q: "Can a hardware wallet manufacturer going bankrupt cause me to lose funds?" A: No — your keys are derived from your seed phrase. As long as you have the seed phrase and any passphrase, you can restore into compatible software/hardware. See company-failure-recovery for a checklist.
Derivation paths explain why addresses can differ across wallets. Matching the original path, account index and passphrase will recover the same addresses from your seed phrase. I noticed that once you understand the m/44'/coin'/account'/change/index pattern, a lot of mystery disappears.
Next steps: if you need a guided restore, check restore-recovery and review seed-phrase-management. For hands-on recovery work, use air-gapped tools (air-gapped) or the advanced-cli resources.
If you want quick reading: bitcoin-guide and ethereum-guide both have sections that explain address formats and how they interact with derivation paths.
But if you're still unsure about a specific case (for instance, funds sent to an address that doesn't appear after restore), bring your recovery phrase, the suspected passphrase (if any), and the transaction details when asking for help — that speeds the diagnosis.