Solo Mining Calculator: Estimate Odds and Timeframes
Use a solo mining calculator correctly: enter productive hashrate, network conditions, uptime and time horizon, then read expected time and probability without.
Read article
ASIC mining knowledge centre
BIP 32 Hierarchical Deterministic Wallets Explained
BIP 32 Hierarchical Deterministic Wallets made simple. See what the proposal changes, its current status and what it means for Bitcoin users and operators.
This guide explains BIP 32 hierarchical deterministic wallets in plain English. It covers the problem behind the BIP, why it matters and whether the proposal is part of Bitcoin today.
TL;DR
- What it is: BIP 32 hierarchical deterministic wallets derive a tree of keys from compact root material. Extended public keys can generate non-hardened public descendants for watch-only systems, while extended private keys generate the corresponding private branches.
- Why it matters: BIP 32 made reproducible wallet trees and watch-only branches practical, but it concentrates authority and privacy in extended keys. Safe use requires explicit derivation paths, hardened boundaries, descriptors, protected xpubs and rehearsed recovery.
- Current position: BIP 32 hierarchical deterministic wallets derive a tree of keys from compact root material.
BIP 32 hierarchical deterministic wallets in simple English
A BIP is a document that proposes or explains a Bitcoin idea, standard or rule. A BIP number does not mean the idea is active. Some BIPs are widely used, while others are drafts or historical proposals.
You do not need to read code to understand the main point. Start with the status, the problem being addressed and the practical effect on ordinary users, wallets, miners or node operators.
Simple example
Think of the transaction as a form passed between several authorised signers. Each person or device checks the same payment details before adding approval. Passing the form around does not make the payment safe unless every signer checks what it contains.
Key terms in plain English
- BIP:
- Bitcoin Improvement Proposal: a document describing a proposed rule, standard or process. Its status must be checked separately.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
From random key pools to a key tree
Older wallets generated many unrelated private keys and needed repeated backups as the pool changed. BIP 32 begins with one master secret and chain code, then derives child nodes identified by indexes. A backed-up root can reproduce the defined tree, provided the wallet also knows which paths, scripts, accounts and scan ranges were used.
What an extended key contains
An extended key serialises a version, depth, parent fingerprint, child number, chain code and key data. Extended private keys contain private key material; extended public keys contain a public point. Network-specific prefixes help display, but software must validate the full payload and intended network rather than trusting familiar first characters.
Normal and hardened derivation
Normal child derivation allows an extended public key to derive public descendants, enabling watch-only address generation. Hardened derivation uses the parent private key and cannot be reproduced from the parent xpub. This boundary is central to account structures. A leaked parent xpub plus a corresponding non-hardened child private key can compromise the parent branch.
Watch-only is not privacy neutral
An xpub cannot normally sign, but it can reveal every address and transaction in its derivable branch. Sharing it with a shop server, explorer or accountant links activity that separate addresses were meant to keep apart. Store xpubs as sensitive financial data, scope branches narrowly and document every system that receives them.
Backups need path and script context
A seed or master extended private key may reproduce keys, yet funds remain hard to find if the wallet forgets derivation paths, script type, account boundaries and gap limits. Output descriptors capture that policy more precisely. Recovery documentation should include network, receive and change branches, birthday and supported address formats without exposing secrets unnecessarily.
Use in multisignature wallets
Multisignature wallets can combine independently derived cosigner keys at matching paths. Key order, origin fingerprints, hardened boundaries and script policy must agree. One cosigner xpub is not a full backup of the wallet. Every participant needs the complete public policy and enough independent private backups to satisfy the intended recovery quorum.
How specialists test it
Developers test the proposal with made-up data on an isolated test network. They check normal cases and deliberately invalid cases. Different implementations should reach the same result before anyone relies on the proposal.
Frequently asked questions
What is BIP 32?
BIP 32 derive a tree of keys from compact root material. Extended public keys can generate non-hardened public descendants for watch-only systems, while extended private keys generate the corresponding private branches.
Is BIP 32 active or supported today?
BIP 32 derive a tree of keys from compact root material.
Why does BIP 32 matter?
BIP 32 made reproducible wallet trees and watch-only branches practical, but it concentrates authority and privacy in extended keys. Safe use requires explicit derivation paths, hardened boundaries, descriptors, protected xpubs and rehearsed recovery.
Do beginners need to use the technical details?
No. Most readers only need to understand the idea and its current status. Developers and node operators can use the primary sources when they need the exact technical rules.
Conclusion
BIP 32 made reproducible wallet trees and watch-only branches practical, but it concentrates authority and privacy in extended keys. Safe use requires explicit derivation paths, hardened boundaries, descriptors, protected xpubs and rehearsed recovery.
Primary sources
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
On this page
Search More Guides
BIP-110 Explained: Rules, Signalling and Why It Closed
BIP-110 Explained made simple. See the main facts, costs, risks and practical checks before you make a decision.
Read article
Bitcoin Core 29.4 Release: Chainstate Disk I/O Guide
Bitcoin Core 29.4 guide covering repeated chainstate rewrites, regular compaction, LevelDB seek compaction, transaction-data lifetime and wallet sizing fixes.
Read article
Need Advice for Your Mining Setup?
Use our guidance to build your shortlist, then speak to our team when you want help comparing hardware, power, hosting or repairs.