This guide explains BIP 46 fidelity bond addresses 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 46 is a Draft application specification for deterministic timelocked fidelity-bond addresses. It derives 960 keys on a dedicated branch, maps each index to the first second of a month from January 2020 through December 2099 and commits the key and absolute lock time in a P2WSH CHECKLOCKTIMEVERIFY script.
- Why it matters: BIP 46 makes fidelity-bond recovery deterministic, but the long-lived timelocks demand exact derivation, time handling and script reconstruction. Operators must distinguish proof of locked value from control of a hot certificate identity.
- Current position: BIP 46 is a Draft application specification for deterministic timelocked fidelity-bond addresses.
BIP 46 fidelity bond addresses in simple English
BIP 46 fidelity bond addresses: Fidelity bonds make identities costly by locking capital for time and enable third parties to verify the sacrifice.
Simple example
A node operator is checking BIP 46 fidelity bond addresses. BIP 46 is Draft even though JoinMarket uses the scheme. Implement month calculation in UTC and test leap years, first-second boundaries and the year-2038 limit on 32-bit time representations.
Key terms in plain English
- BIP:
- Bitcoin Improvement Proposal: a document describing a proposed rule, standard or process. Its status must be checked separately.
- Consensus:
- The shared rules full nodes use to decide whether blocks and transactions are valid.
- UTXO:
- An unspent transaction output: a piece of bitcoin that can be used as an input to a later transaction.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Purpose and status
Fidelity bonds make identities costly by locking capital for time and enable third parties to verify the sacrifice. BIP 46 is Draft even though JoinMarket uses the scheme.
Key path
Derived keys use m/84 hardened/0 hardened/0 hardened/2/index. The change value two separates bonds from ordinary receive and change paths; network coin type must still be handled correctly.
Fixed search space
Indexes 0 through 959 map to monthly locks from January 2020 to December 2099. There is no gap limit: recovery scans all 960 candidates.
Lock script
The witness script pushes the Unix lock time, runs CHECKLOCKTIMEVERIFY and DROP, then checks the derived public-key signature. The P2WSH output is witness version zero plus its SHA256 hash.
Cold certificates
The bond key can sign a certificate key, which then signs a service endpoint. Compromise of the online certificate permits temporary impersonation but should not unlock the bond funds.
Time hazards
Implement month calculation in UTC and test leap years, first-second boundaries and the year-2038 limit on 32-bit time representations. Funds cannot be spent before consensus lock conditions are met.
Recovery and proof
Back up seed and scheme identity, derive every index, scan history and UTXOs, reconstruct witness scripts and verify certificate messages, outpoints, values, expiry periods and signatures independently. Build a revision-pinned evidence pack on an isolated node, wallet or protocol harness. Record source commit, binary hash, network, chain identity, configuration and dependencies.
Frequently asked questions
What is the main point of BIP 46 fidelity bond addresses?
BIP 46 fidelity bond addresses: Fidelity bonds make identities costly by locking capital for time and enable third parties to verify the sacrifice.
For BIP 46 fidelity bond addresses, what should a beginner know about purpose and status?
Fidelity bonds make identities costly by locking capital for time and enable third parties to verify the sacrifice.
For BIP 46 fidelity bond addresses, what should a beginner know about key path?
Derived keys use m/84 hardened/0 hardened/0 hardened/2/index.
For BIP 46 fidelity bond addresses, what should a beginner know about fixed search space?
Indexes 0 through 959 map to monthly locks from January 2020 to December 2099.
Conclusion
BIP 46 makes fidelity-bond recovery deterministic, but the long-lived timelocks demand exact derivation, time handling and script reconstruction. Operators must distinguish proof of locked value from control of a hot certificate identity.
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.



Join the ASIC Mining Discussion
Members can read and join the discussion
Log in to read comments from other miners. Create a free account if you would like to ask a question or share your experience.
Membership helps us protect the discussion from spam and keep answers useful.