public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "'Ben Westgate' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] [BIP Proposal] Add BIP-0093 (Codex32) as application to BIP-0085
Date: Sun, 31 Aug 2025 15:25:47 -0700 (PDT)	[thread overview]
Message-ID: <774faeb9-6c6b-4545-8071-56ec03e78cd0n@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2351 bytes --]



Hello bitcoin-dev,

I’m Ben Westgate, a contributor interested in deterministic wallet backups 
and seed management.

Per BIP-0002, I propose listing *BIP-0093 (codex32)* 
<https://github.com/bitcoin/bips/blob/master/bip-0093.mediawiki> as an 
application of
*BIP-0085 (Deterministic Entropy from BIP32 Keychains) 
<https://github.com/bitcoin/bips/blob/master/bip-0085.mediawiki>*, similar 
to the existing BIP39 application. This allows wallets to derive codex32 
backups from BIP-0032 master keys.

*Summary* 

   - 
   
   Application number: 93'
   - Derivation path: 
   m/83696968'/93'/{hrp}'/{threshold}'/{n}'/{byte_length}'/{id0}'/{id1}'/{id2}'/{id3}'/{index}' 
   
Codex32, defined in BIP-93, is a human-readable encoding with checksumming 
and share indexing designed for SSS backups of BIP-0032 seeds. This PR 
proposes a deterministic way to generate codex32 strings using BIP-85.

*Rationale* 

   - 
   
   Mirrors the existing BIP-85 application for BIP-39.
   - 
   
   Codex32 offers error correction, hand verification, identifiers, and 
   secret sharing features compared to BIP-39.
   - 
   
   Adds a standardized way for wallets to generate codex32 backups from 
   BIP-85-derived entropy
   - 
   
   Test vectors and reference implementation are linked to in the PR.
   
*Risks and alternatives* 

   - 
   
   Wallet adoption of codex32 is still limited, though a draft PR #32652 
   <https://github.com/bitcoin/bitcoin/pull/32652?utm_source=chatgpt.com> 
   for importing codex32 strings to Bitcoin Core has support.
   - Codex32 implementers could use the BIP-85 dice application, but 
   defining a direct application improves interoperability.

PR: 
https://github.com/bitcoin/bips/compare/master...BenWestgate:bips:codex32 
<https://github.com/bitcoin/bips/compare/master...BenWestgate:bips:codex32?utm_source=chatgpt.com>

Feedback is welcome.
Best regards,
Ben Westgate

-- 
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/774faeb9-6c6b-4545-8071-56ec03e78cd0n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 2856 bytes --]

             reply	other threads:[~2025-08-31 22:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-31 22:25 'Ben Westgate' via Bitcoin Development Mailing List [this message]
2025-09-01  8:41 ` [bitcoindev] Re: [BIP Proposal] Add BIP-0093 (Codex32) as application to BIP-0085 Javier Mateos
2025-09-01 18:37   ` 'Ben Westgate' via Bitcoin Development Mailing List
2025-09-02  2:30     ` Javier Mateos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=774faeb9-6c6b-4545-8071-56ec03e78cd0n@googlegroups.com \
    --to=bitcoindev@googlegroups.com \
    --cc=BenWestgate@Protonmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox