BIP44 Derivation Path

BIP44 derivation path is the Bitcoin Improvement Proposal that standardizes how hierarchical-deterministic (HD) wallets organize the billions of keys they can derive from a single seed. Building on BIP32, which defined the derivation mathematics, BIP44 defines a five-level path structure so that different wallet software can interoperably find the same addresses from the same recovery phrase. It is the reason a seed written down years ago in one application can be typed into a completely different one today and produce the same wallet — arguably the most underappreciated piece of interoperability in Bitcoin.

The five levels

The path format is m / purpose' / coin_type' / account' / change / address_index. Purpose is fixed at 44' to signal that this standard applies. Coin type gives each cryptocurrency its own subtree — 0' for Bitcoin — so keys for different coins derived from one seed never mix. Account splits funds into independent identities, like separate bank accounts under one customer: business at account 0', personal at account 1', with no on-chain connection visible between them. Change is 0 for receiving addresses you hand out and 1 for internal change addresses your wallet pays itself. Address index enumerates the individual addresses, starting at 0 and incrementing as needed. So m/44'/0'/0'/0/5 reads: BIP44 standard, Bitcoin, first account, external chain, sixth address.

Hardened derivation and the apostrophes

The apostrophes mark hardened derivation at the first three levels. Hardened child keys cannot be computed from the parent's extended public key alone — they require the private key — which contains the damage if an extended public key and one child private key ever leak together. The final two levels are unhardened deliberately: it lets a watch-only wallet holding just the account-level xpub derive every receive and change address without any private material, the pattern that makes air-gapped monitoring workable.

Why it matters for recovery

Standardized paths are why seed recovery works across vendors — but also why it sometimes appears to fail. Successor standards assign each address type its own purpose value: BIP49 (m/49') for nested-SegWit, BIP84 (m/84') for native SegWit, and BIP86 (m/86') for Taproot. A wallet restoring a seed under the wrong standard derives valid keys at paths where no funds live, so a correct seed phrase can present an alarming empty balance. This is the single most common cause of recovery panic, and the cure is documentation: record which path standard and script type your wallet uses alongside the seed backup. Modern descriptor-based software embeds this information explicitly, which is the long-term fix.

The sovereign takeaway

BIP44 is a convention, not a consensus rule — Bitcoin itself has no opinion about derivation paths. That makes the convention's near-universal adoption the load-bearing fact: your recovery plan depends on future software honouring today's standards, which is another argument for keeping wallet documentation with your backup rather than trusting memory. The keys descend from the seed you protect with schemes like Shamir's Secret Sharing (SLIP39), live behind a hardware wallet's secure element, and end up as the public-key hashes computed with HASH160 that appear in addresses. The path is simply the map that says where in the tree each of them grows.