Sealminer A4 Ultra Hydro
Bitcoin & Bitcoin Cash ASIC Miner
886TH
HASHRATE
9.45W/TH
EFFICIENCY
8373W
POWER
£830.18
EST. MONTHLY
NO PAYBACK
EST. ROI
This guide explains BIP 93 codex32 seeds 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 93 is a Draft Informational proposal for encoding BIP 32 master seed material in a checksummed base32 form called codex32. It adds a BCH checksum and optional Shamir secret sharing, allowing a secret to be stored directly or divided into as many as 31 shares.
- Why it matters: Codex32 offers strong transcription checks and flexible threshold backups, but a checksum cannot replace custody discipline. Safe adoption requires verified generation, separated shares, documented thresholds and repeated offline recovery drills.
- Current position: BIP 93 is a Draft Informational proposal for encoding BIP 32 master seed material in a checksummed base32 form called codex32.
BIP 93 codex32 seeds in simple English
BIP 93 codex32 seeds: BIP 93 remains Draft. It encodes BIP 32 seed bytes and optional shares. It is not a BIP 39 mnemonic, wallet descriptor, passphrase system or key-stretching scheme.
Simple example
A node operator is checking BIP 93 codex32 seeds. The human-readable part is ms, followed by 1, a threshold digit, four-character identifier, share index, payload and 13-character checksum.
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.
Status and purpose
BIP 93 remains Draft. It encodes BIP 32 seed bytes and optional shares; it is not a BIP 39 mnemonic, wallet descriptor, passphrase system or key-stretching scheme.
String structure
The human-readable part is ms, followed by 1, a threshold digit, four-character identifier, share index, payload and 13-character checksum. Strings must be entirely upper- or lowercase.
Thresholds and shares
A split uses a threshold from 2 to 9 and up to 31 distinct shares. The special share index s denotes an unshared secret; threshold 0 is recommended for that form.
Checksum properties
The BCH checksum detects any error affecting at most eight characters and supports correction of up to four substitutions, eight erasures or thirteen consecutive erasures under the specified rules.
Human correction
Software may suggest a corrected string but should not proceed automatically without confirmation. A checksum proves transcription consistency, not authenticity or freedom from malicious replacement.
Design limits
Codex32 deliberately omits passphrases, key hardening and multi-level share splitting to retain hand-computable operations. High-quality randomness and trustworthy generation remain essential.
Recovery ceremony
Generate and verify with audited software, distribute shares across independent failure domains, rehearse threshold recovery offline, compare a derived public identifier and document succession without copying the secret. 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 93 codex32 seeds?
BIP 93 codex32 seeds: BIP 93 remains Draft. It encodes BIP 32 seed bytes and optional shares.
For BIP 93 codex32 seeds, what should a beginner know about status and purpose?
BIP 93 remains Draft. It encodes BIP 32 seed bytes and optional shares.
For BIP 93 codex32 seeds, what should a beginner know about string structure?
The human-readable part is ms, followed by 1, a threshold digit, four-character identifier, share index, payload and 13-character checksum.
For BIP 93 codex32 seeds, what should a beginner know about thresholds and shares?
A split uses a threshold from 2 to 9 and up to 31 distinct shares.
Conclusion
Codex32 offers strong transcription checks and flexible threshold backups, but a checksum cannot replace custody discipline. Safe adoption requires verified generation, separated shares, documented thresholds and repeated offline recovery drills.
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.