Methodology

Every chapter is built from a pinned revision of the bitcoin/bips repository. The current source is commit 3a10b5b, read on 1 October 2026. File hashes are recorded in a lock file, and links in each chapter open the exact lines that support a statement.

Some BIPs publish their test vectors in other repositories. Those files are fetched at an explicit commit and hashed too:

• trezor/python-mnemonic/vectors.json at b57a5ad, cited by BIP 39
• bip32JP/bip32JP.github.io/test_JP_BIP39.json at 5a43706, cited by BIP 39

What has been checked

Each chapter’s figures draw only reviewed recipes, and every exact value they show comes from a tested model, computed at build time or in your browser. The models use the audited @noble libraries for hashing and elliptic-curve arithmetic. The tests check them against the proposals’ own vectors:

• BIP 39: all 24 English and 24 Japanese reference vectors, from entropy to words to seed, and the pinned wordlist’s hash.
• BIP 32: all 17 derivation chains embedded in the BIP, all 16 invalid extended keys (each for its stated reason), and the master keys of all 24 BIP 39 English vectors.
• BIPs 141 and 143: the two SIGHASH_ALL witness examples, byte for byte: serialization, signing preimage and digest.
• BIPs 173 and 350: every Bech32, Bech32m and SegWit address vector, including the stage at which each invalid one is stopped.
• BIP 174: all 20 invalid and 10 valid PSBTs, the published role trace (combining in either order, extraction) and unknown-field preservation.
• All 165 evidence quotes across 5 chapters appear verbatim at their cited lines, and every sample is tied to a pinned source line or vector file.

What has not

• Every chapter is hand-authored. Each has had one independent technical review whose findings were applied, but none has formal sign-off; all are marked as drafts.
• No automated writing pipeline is connected yet.
• The models are teaching models. They check structure and encodings against published vectors; they are not wallets, signers or full conformance suites, and they say nothing about ownership, balance, or whether a payment is safe.
• No screen-reader session or accessibility audit has been performed beyond the checks recorded in the project.

Privacy

Pages load no third-party scripts, fonts or analytics. Figures run entirely in your browser, accept no free-text addresses, keys, recovery phrases or PSBTs, and never send what you do in them anywhere. Nothing on this site signs or broadcasts a transaction.