LibraryData and agents2023Design paperCorpus record
codex32: Checksummed SSSS-aware BIP32 seeds
BIP 93. Leon Olsson Curr and Pearlwort Sneed.
BIP 93, codex32: Checksummed SSSS-aware BIP32 seeds. We first describe the general checksummed base32 Why use base32 at all? The lack of mixed case makes it more efficient to read out loud, write, type or to put into QR codes.
Status in the source: Draft. A reading of the public specification, not a copy of it and not a certification.
codex32: Checksummed SSSS-aware BIP32 seeds is worth reading for the rule it actually adds: We first describe the general checksummed base32 Why use base32 at all? The lack of mixed case makes it more efficient to read out loud, write, type or to put into QR codes.
- Evidence
- Primary paper
- Re-measured
- No
- Assumptions
- 3
- Records linked
- 3
Code
Source, repository, and what is actually hosted
- BIP 93https://bips.dev/93
- The source URL is not a GitHub repository. No code remote is invented.
- Full text is not mirrored. Public availability is not a licence to copy the file onto this site.
- Add to a reading list
01 Claim ledger
What the paper is allowed to say
Each row is a sentence already in the study. The status is the same on every row: a model claim, not a live measurement.
Claim 01 · Paper model
The rule
We first describe the general checksummed base32 Why use base32 at all? The lack of mixed case makes it more efficient to read out loud, write, type or to put into QR codes.
Claim 02 · Paper model
What was already failing
An interface that is only a name in a repository will be re-implemented differently by every team, which is how shared contracts break.
Claim 03 · Paper model
What the number does not mean
The source marks this draft. It is not a live consensus rule just because it has a number.
Claim 04 · Paper model
What a builder should be able to point at
An implementation either constrains SSSS, BIP32 or it is a different design.
02 Three cuts
Observation, model, falsifier
A desk does not stop at the summary. Each claim is cut three ways, using only this study's own assumptions and checks. Nothing here is a new figure.
01 The rule
Observation
What the study says
We first describe the general checksummed base32 Why use base32 at all? The lack of mixed case makes it more efficient to read out loud, write, type or to put into QR codes.
Model
What has to hold
You are implementing BIP 93 at the status the text itself states: Draft.
Falsifier
What would retire it
What must an implementation of codex32: Checksummed SSSS-aware BIP32 seeds accept, and what may it ignore?
02 What was already failing
Observation
What the study says
An interface that is only a name in a repository will be re-implemented differently by every team, which is how shared contracts break.
Model
What has to hold
The object that has to change is SSSS, BIP32. A neighbouring document with a similar name is not this one.
03 What the number does not mean
Observation
What the study says
The source marks this draft. It is not a live consensus rule just because it has a number.
Model
What has to hold
You are implementing BIP 93 at the status the text itself states: Draft.
04 What a builder should be able to point at
Observation
What the study says
An implementation either constrains SSSS, BIP32 or it is a different design.
Model
What has to hold
The object that has to change is SSSS, BIP32. A neighbouring document with a similar name is not this one.
Falsifier
What would retire it
What must an implementation of codex32: Checksummed SSSS-aware BIP32 seeds accept, and what may it ignore?
03 Sequence
One action, as an operating tape
- 01Open BIP 93 and read the status line before the examples.
- 02Write down the rule in one sentence. A fair version of that sentence is: We first describe the general checksummed base32 Why use base32 at all? The lack of mixed case makes it more efficient to read out loud, write, type or to put into QR codes.
- 03Name the object that changes: SSSS, BIP32.
- 04Ask what an old client, an old contract, or an offline counterparty does. If the document is silent, the silence is part of the design.
04 Load-bearing
The argument, and where a pitch drops it
What the text is allowed to settle
The cut
Bitcoin Improvement Proposal 93 can settle the shape of codex32: Checksummed SSSS-aware BIP32 seeds. It cannot settle whether a later client, a later fork, or a later wallet still does this.
Why it carries weight
If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.
Where it is dropped
A later client, parameter or reward formula is a different object from this paragraph.
What this page will not pretend
The cut
There is no benchmark, no adoption number, and no claim that the mechanism is safe outside the assumptions written in the source.
Why it carries weight
If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.
Where it is dropped
The source marks this draft. It is not a live consensus rule just because it has a number.
05 Register
What has to be true
Model · Not re-measured
You are implementing BIP 93 at the status the text itself states: Draft.
Model · Not re-measured
The object that has to change is SSSS, BIP32. A neighbouring document with a similar name is not this one.
Model · Not re-measured
Status in the header is not adoption.
06 Divergence
What happened after the paper
The source marks this draft. It is not a live consensus rule just because it has a number. Later documents can narrow, replace, or ignore this one. Cite the number you mean.
A later client, parameter set, or reward formula is a different object. Cite this paper for the mechanism. Cite a primary release for the network. This desk has not re-run the proof.
07 Pre-mortem
What to check before you use the idea
- 0 of 3 marked on this browser. A mark is a reading note, not a pass, a rating, or a recommendation.
08 Anatomy
The paper, in the order a builder needs
The problem it names
An interface that is only a name in a repository will be re-implemented differently by every team, which is how shared contracts break.
What the design proposes
- We first describe the general checksummed base32 Why use base32 at all? The lack of mixed case makes it more efficient to read out loud, write, type or to put into QR codes.
- format called codex32 and then define a BIP-0032 master seed encoding using it.
- The normative names to look up in BIP 93 are SSSS, BIP32.
How the mechanism is specified
- Taken from the specification, the next constraint is: format called codex32 and then define a BIP-0032 master seed encoding using it.
- Locate SSSS, BIP32 in BIP 93 and apply it to one transaction or call.
- Then check the failure the class of rule always has: a node that did not upgrade, a reverted call, a replayed signature, or a peer that does not speak the message.
What this page does not treat as proven
- This document does not set a fee, a valuation, or a security proof.
- Status in the header is not adoption.
- The source marks this draft. It is not a live consensus rule just because it has a number.
09 Lexicon
Terms, opened into the record
- BIP 93
- The public text titled codex32: Checksummed SSSS-aware BIP32 seeds.
- Draft
- The document's own label for how finished the text is. It is not a market fact.
10 Repository
Every linked record on this page
Underlined words open a page that already exists: a concept, a protocol profile, a failure record, or another paper. If a word is not underlined, this desk does not have a record for it.
This is Blockchain Lab's reading of a public design paper. It is not the paper, not a copy of it, and not an offer of tokens, equity, custody or a partnership. Later network behaviour can diverge from the text. Nothing here is investment, legal or technical advice.
Research status: Design paper. Last reviewed: 1 October 2026. This is a reading of a public paper, not investment, legal or security advice.