Why it exists
BIP 32 defines hierarchical deterministic wallets: one root can reproducibly generate a tree of private and public keys. A wallet can issue fresh addresses without requiring a new secret backup for every key, while keeping different accounts or roles on separate branches.
How it works
An extended key combines a key with a chain code. Child derivation uses both, together with a child index. An extended public key, commonly called an xpub, can derive non-hardened public descendants without exposing the private signing keys.
Hardened derivation requires private-key information and blocks that public-only derivation route. Apostrophes in paths such as m/84'/0'/0' mark hardened steps. Higher-level standards choose what the branches mean; BIP 32 itself does not decide the address format or account purpose.
A practical example
A merchant can give an account xpub to a checkout server. The server derives a different receiving address for each order, while a separate signer retains the private keys. The server can observe the branch but cannot sign payments from the xpub alone.
What to keep in mind
An xpub exposes linked addresses and transaction history. More seriously, a parent xpub combined with a corresponding non-hardened descendant private key can compromise private keys higher in that branch. Keep private child keys secret and preserve the correct wallet derivation information.
Status & implementation
Bitcoin Core documents BIP 32 support since 0.13.0. That establishes implementation in Core, not support for every account convention or backup format layered above it. The official BIP status is Deployed.
Specification status: Deployed · Sources checked 13 November 2026
