slip-0173: register HRP mk for Mnemonic Key (BIP 32 xpub backup)#2012
Open
bg002h wants to merge 1 commit intosatoshilabs:masterfrom
Open
slip-0173: register HRP mk for Mnemonic Key (BIP 32 xpub backup)#2012bg002h wants to merge 1 commit intosatoshilabs:masterfrom
bg002h wants to merge 1 commit intosatoshilabs:masterfrom
Conversation
bg002h
added a commit
to bg002h/mnemonic-key
that referenced
this pull request
Apr 29, 2026
PR filed: satoshilabs/slips#2012 Branch: bg002h:slip-0173-register-mk-hrp (off upstream master) Diff: 1 row addition to slip-0173.md between `Lightning Network` and `Zcash`, mirroring md1's PR #2011 shape (single mainnet HRP column, no testnet/regtest variants since mk1 testnet handling lives in the xpub.version field, not the HRP). Updates: - design/FOLLOWUPS.md::slip-0173-register-mk-hrp marked `resolved 2026-04-29 — PR filed at #2012`. Tier closed; awaiting upstream SatoshiLabs review tracked externally. Parallel to md1's `slip-0173-register-md-hrp` (PR #2011, also in external-review state). - design/AUDIT_hrp_mk_collision.md §"Pending: SLIP-0173 registration" replaced with §"SLIP-0173 registration (filed)" pinning PR #2012 and noting the rebase contingency if #2011 merges first. If md1's PR #2011 merges first, mk1's PR #2012 needs a one-line rebase to insert `mk` after `md` rather than after `Lightning Network`. Both PRs are mergeable in either order without that conflict otherwise.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Registers the HRP
mkfor the Mnemonic Key (MK) format — a steel-engravable backup format for individual BIP 32 extended public keys (xpubs). Spec + reference implementation at https://github.com/bg002h/mnemonic-key.Format scope: not a cryptocurrency network. MK encodes individual xpubs into Bech32-style strings prefixed
mk1...for engraving on steel backup plates, designed to engrave alongside the sibling Mnemonic Descriptor (MD, HRPmd) policy card for foreign-xpub multisig recovery. The engraved card carries one xpub plus declarative metadata (Policy ID stubs, optional master fingerprint, derivation path); keys remain in BIP 39 seed words.HRP collision vet performed prior to selection (2026-04-29, recorded in
design/AUDIT_hrp_mk_collision.md):mmMiden,myMyriad; closest 1-Hamming-distance neighbours aremscodex32 BIP 93,mdMnemonic Descriptor,mm,my)ms) — distinct frommk; cross-HRP false-positive validation prevented by BIP 173 HRP-mixing (≈ 2⁻⁶⁵ collision probability per cross-HRP mistype)md) — sibling format from the same project; deliberate 1-Hamming-distance pair to surface the family relationship without sharing the HRPlnbc,lntb,lnbcrt,lnsb,lno,lni,lnr) — distinctex,lq,el,tlq,ert) — distinctnpub,nsec,note, etc.) — distinctCross-format separation beyond HRP-mixing:
mkandmduse independent NUMS-derived target residues drawn from different domain strings (shibbolethnumskeyandshibbolethnumsrespectively), so even an HRP-collision-prone construction would still need a constant collision to silently misvalidate.Status: BIP draft is currently Pre-Draft, AI + reference implementation, awaiting human review. Latest release:
mk-codec-v0.1.1.Companion filing: PR #2011 registers
mdfor the sibling Mnemonic Descriptor format. Both filings share the same author, project, and design lineage. If #2011 merges first this PR will need a one-line rebase to insertmkaftermdrather than afterLightning Network; happy to do that on request.Filing this defensive registration to close off future collision risk from independent projects.