public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: <eric@voskuil•org>
To: "'pithosian'" <pithosian@i2pmail•org>, <bitcoindev@googlegroups.com>
Subject: RE: [bitcoindev] BIP39 Extension for Manual Seed Phrase Creation
Date: Wed, 4 Jun 2025 11:26:33 -0400	[thread overview]
Message-ID: <04c301dbd565$0e07ffa0$2a17fee0$@voskuil.org> (raw)
In-Reply-To: <20250525214153.163D47C0BC6@smtp.postman.i2p>

> > A standard for encoding entropy
> 
> In my view, this is exactly what BIP 39 already is. It's a specification for
> encoding Base2048 numbers with a checksum, similar to Base58. The
> character set is a list of words, but fundamentally the only real difference
> between it, and Base2, Base10, Base16, etc is the checksum.

I'm not following the thread, but I'd like to lend full support to the above statement.

base 2^n, 10, 16, 32, 58, 64, 85, 2048:

https://github.com/libbitcoin/libbitcoin-system/tree/master/src/radix
https://github.com/libbitcoin/libbitcoin-system/tree/master/include/bitcoin/system/impl/radix

specifically base_2048:

https://github.com/libbitcoin/libbitcoin-system/blob/master/src/radix/base_2048.cpp

base_2048 encodings with checksum applied:

https://github.com/libbitcoin/libbitcoin-system/tree/master/src/wallet/mnemonics

specifically bip39:

https://github.com/libbitcoin/libbitcoin-system/blob/master/src/wallet/mnemonics/mnemonic.cpp

best,
e

-- 
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/04c301dbd565%240e07ffa0%242a17fee0%24%40voskuil.org.


  reply	other threads:[~2025-06-04 15:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250523131541.1521C7C0DB0@smtp.postman.i2p>
2025-05-24 20:56 ` pithosian
2025-05-25 14:26   ` nerdyrugbyguy
     [not found]   ` <20250525154052.28C0E7C1013@smtp.postman.i2p>
2025-05-25 21:41     ` pithosian
2025-06-04 15:26       ` eric [this message]
2025-06-04 17:45       ` 'Russell O'Connor' via Bitcoin Development Mailing List
2025-05-23 11:25 Eric Kvam
2025-05-23 14:29 ` Kyle Honeycutt
     [not found]   ` <09A940A2-122A-445E-82EA-1B4E32AC7E34@gmail.com>
2025-05-23 20:45     ` 'Russell O'Connor' via Bitcoin Development Mailing List
2025-05-24 12:33       ` Eric Kvam

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='04c301dbd565$0e07ffa0$2a17fee0$@voskuil.org' \
    --to=eric@voskuil$(echo .)org \
    --cc=bitcoindev@googlegroups.com \
    --cc=pithosian@i2pmail$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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