What is a Derivation Path?
A derivation path is the route from an HD wallet’s master key down to one specific private key and address. It looks like a file path because it works like one:
m/44'/60'/0'/0/0
m— the master key (derived from your seed phrase)44'— purpose: BIP-44 multi-account hierarchy60'— coin: 60 is Ethereum (0 is Bitcoin legacy, 501 is Solana)0'— account number0— external (receiving) vs internal (change) chain- final
0— the address index: your first address
Same seed, different path = different address. Every wallet agrees on these numbers through the BIP-32/44 standards, which is why importing a seed into a new wallet usually finds the same addresses.
Why Users Run Into It
The classic support question — “I imported my seed and my balance is zero” — is usually a derivation path issue:
- An old wallet used a legacy path (common with 2014-2017 era Bitcoin wallets or MEW/ETH classics like
m/44'/60'/0') - The new wallet defaults to a standard path and looks at a different branch
- The funds are safe, sitting at addresses on the other branch
Most modern wallets (MetaMask, Ledger Live, Phantom) handle this automatically or expose a “custom derivation path” setting for exactly this case.
Security Notes
- Derivation paths are not secrets. Knowing your path tells an attacker nothing without your seed.
- An attacker with your seed phrase doesn’t need to guess paths — standard wallets sweep every common branch automatically.
- Hardware wallets show the path (or the address) on-device when verifying. Always verify receive addresses on the device screen, not just in the browser.