When you set up a Bitcoin wallet and write down your seed phrase, it feels like the hard part is done. But there's a less visible piece of the puzzle that trips up beginners when they try to recover funds or switch wallets: the derivation path. It's a short string of numbers and slashes that tells your wallet software exactly how to generate keys from your seed, and if it's wrong, your Bitcoin can appear to vanish, even when your seed phrase is perfectly intact.
What a derivation path actually is
A derivation path is a structured formula that a Bitcoin wallet uses to turn one master seed into a practically unlimited number of unique private keys and addresses. The path specifies a precise route through a tree of cryptographic keys, and every branch of that tree produces different keys.
A typical derivation path looks like this: m/44'/0'/0'/0/0
Each segment has a specific meaning. The m stands for the master key derived from your seed phrase. The numbers that follow describe the exact path through the hierarchy. The apostrophe symbol after a number denotes a "hardened" derivation, meaning the child key is generated using a one-way function that prevents anyone from deriving parent keys from a child. Without hardening, a leaked child private key could compromise the entire branch.
Here's what each level in m/44'/0'/0'/0/0 represents:
- 44': the purpose, following the BIP44 standard for multi-account wallets
- 0': the coin type (0 is the code for Bitcoin on mainnet)
- 0': the account index, starting at zero
- 0: the change chain (0 for external addresses you share, 1 for internal change addresses)
- 0: the address index, incrementing for each new address generated
Why different wallets use different paths
Not every wallet follows the same standard. The Bitcoin Improvement Proposals (BIPs) that defined derivation paths have evolved over time, and different wallet software has adopted different standards depending on their address format and feature set.
The three most common paths in use today are tied to address types. BIP44 uses the path m/44'/0'/0' and generates legacy addresses starting with the number 1. BIP49 uses m/49'/0'/0' and generates SegWit-compatible addresses starting with 3. BIP84 uses m/84'/0'/0' and generates native SegWit addresses starting with bc1q.
This matters because if you back up your seed phrase and later restore it in a different wallet using the wrong path, that wallet will generate a completely different set of addresses. Your Bitcoin is not lost. It still exists on the blockchain. But the wallet can't see it until you point it at the correct derivation path.
The connection to your seed phrase
Your Bitcoin private key is ultimately derived from your seed phrase through a deterministic process. The seed phrase generates a master key, and the derivation path tells the wallet which branch of the key tree to walk down. Change the path and you get different keys. Same seed, different path, different addresses.
This determinism is actually the point. It means a single 12 or 24-word seed phrase can back up an unlimited number of keys across multiple accounts and address types, as long as you also know which derivation path to use when recovering. Most wallets handle this automatically, but if you ever use a custom or advanced recovery tool, you may need to specify it manually.
When derivation paths cause problems
The most common situation where derivation paths cause trouble is wallet migration. A user creates a wallet with one application, buys Bitcoin, then decides to switch to a different wallet app. They enter their seed phrase into the new app, and the balance shows zero. Panic sets in.
In most cases the funds are safe. The new wallet is simply looking at a different derivation path. The fix is to find the correct path used by the original wallet (usually listed in its documentation or settings) and enter it manually in the recovery tool.
A second problem arises with hardware wallets. Some hardware devices default to a specific path that differs from what a software companion app expects. Always check the path your hardware wallet uses before assuming a zero balance means empty accounts.
If you're in the habit of generating new receiving addresses frequently (which is good practice for privacy), it's worth understanding that each of those addresses sits at a different index at the end of the path, such as .../0/0, .../0/1, .../0/2, and so on. Most wallets scan a gap limit of 20 or more consecutive unused addresses when recovering, so small address gaps won't cause issues. But very large gaps can fool a wallet into stopping the scan too early.
What beginners should record alongside their seed phrase
Security guides rightly focus on storing Bitcoin safely by protecting the seed phrase above all else. But alongside the seed, it's worth noting the derivation path your wallet uses, especially if it's non-standard. You don't need to memorise the path, but recording it with the same care you give your seed phrase removes a painful variable from any future recovery attempt.
Most mainstream wallets, including Electrum, Sparrow, and the major hardware wallet brands, display the derivation path in their settings or advanced recovery screens. Note it down when you first set up the wallet. A minute of documentation now can save hours of confusion later.
Hardened vs non-hardened derivation
The apostrophe notation is worth a brief stop. Hardened derivation (marked with a ' or sometimes an h) means the child key cannot be reverse-engineered to expose a parent key, even if an attacker gets hold of the child's private key. Non-hardened derivation is flexible and lets wallets generate public keys without exposing private keys, which is useful for watch-only wallets that need to track balances without signing capability.
The upper levels of a path (purpose, coin, account) are almost always hardened. The lower levels (change chain and address index) are typically not, which allows a wallet to derive addresses for display purposes without needing to touch private key material at all. This design is one reason a Bitcoin watch-only wallet can show your full balance securely without ever holding a private key.
A practical note on BIP85
One extension of derivation paths worth knowing about is BIP85, which lets a single master seed generate entirely separate child seeds. Instead of deriving individual keys, it derives new seed phrases that can be used in separate wallets. This allows a single backed-up master seed to act as the root for multiple independent wallets, each with their own derivation trees. It's an advanced feature, but it illustrates how far the derivation path concept extends beyond simple address generation.
Derivation paths are one of those technical details that sit quietly in the background until something goes wrong. Knowing what they are and where to find them in your wallet settings turns a potential crisis into a five-minute fix.