Re: [bitcoin-dev] New serialization/encoding format for key material

2018-06-23 Thread Pieter Wuille via bitcoin-dev
On Fri, Jun 15, 2018 at 8:54 AM, Russell O'Connor wrote: > >> For codes designed for length 341 (the first length enough to support >> 512 bits of data): >> * correct 1 error = 3 checksum characters >> * correct 2 errors = 7 checksum characters >> * correct 3 errors = 11 checksum characters >> *

Re: [bitcoin-dev] New serialization/encoding format for key material

2018-06-15 Thread Russell O'Connor via bitcoin-dev
> For codes designed for length 341 (the first length enough to support > 512 bits of data): > * correct 1 error = 3 checksum characters > * correct 2 errors = 7 checksum characters > * correct 3 errors = 11 checksum characters > * correct 4 errors = 15 checksum characters > * correct 5 errors =

Re: [bitcoin-dev] New serialization/encoding format for key material

2018-06-13 Thread Russell O'Connor via bitcoin-dev
On Tue, May 29, 2018 at 5:13 AM, Jonas Schnelli via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > Hi > > If 520 bits are present, first 256 bits are the BIP32 chain code, to > second 264 > bits (33 bytes) define the public key (according to BIP32) > In a 33 byte compressed public

Re: [bitcoin-dev] New serialization/encoding format for key material

2018-06-12 Thread Pieter Wuille via bitcoin-dev
On Sun, Jun 3, 2018 at 2:30 PM, Jonas Schnelli wrote: >> If there is interest, I can construct a code + implementation for any >> of these in a few days probably, once the requirements are clear. > > Yes. Please. Here is an example BCH code for base32 data which adds 27 checksum characters, and

Re: [bitcoin-dev] New serialization/encoding format for key material

2018-06-03 Thread Jonas Schnelli via bitcoin-dev
> I have some concerns about the use of Bech32. It is designed for > detecting 3 errors up to length 1023 (but is then picked specifically > to support 4 errors up to length 89). However, for error correction > this translates to just being able to efficiently correct 1 error > (3/2, rounded down)

Re: [bitcoin-dev] New serialization/encoding format for key material

2018-06-03 Thread Pieter Wuille via bitcoin-dev
On Sun, Jun 3, 2018 at 9:51 AM, Jonas Schnelli via bitcoin-dev wrote: > Hi > > The BIP proposal is now available here: > https://gist.github.com/jonasschnelli/68a2a5a5a5b796dc9992f432e794d719 > > Reference C code is available here: > https://github.com/jonasschnelli/bech32_keys > > Feedback,

Re: [bitcoin-dev] New serialization/encoding format for key material

2018-06-03 Thread Jonas Schnelli via bitcoin-dev
Hi The BIP proposal is now available here: https://gist.github.com/jonasschnelli/68a2a5a5a5b796dc9992f432e794d719 Reference C code is available here: https://github.com/jonasschnelli/bech32_keys Feedback, criticism, etc. welcome! Thanks — Jonas signature.asc Description: Message signed with

Re: [bitcoin-dev] New serialization/encoding format for key material

2018-05-30 Thread Jonas Schnelli via bitcoin-dev
Hi > - Visually Comparing two keys to find if they are same (Important) > - Different wallet software could set different birthday/gap limit. creating > different xpub/xprv for the same set of mathematically derived individual > keys. This removes the decoupling between key and wallet metadata

Re: [bitcoin-dev] New serialization/encoding format for key material

2018-05-30 Thread Gregory Maxwell via bitcoin-dev
On Wed, May 30, 2018 at 6:30 AM, shiva sitamraju via bitcoin-dev wrote: > The idea to add birthdate and gap limit sounds very good and addresses lots > of problems users are facing. > > However, adding birthday to keys breaks two basic properties > > - Visually Comparing two keys to find if they

Re: [bitcoin-dev] New serialization/encoding format for key material

2018-05-30 Thread shiva sitamraju via bitcoin-dev
The idea to add birthdate and gap limit sounds very good and addresses lots of problems users are facing. However, adding birthday to keys breaks two basic properties - Visually Comparing two keys to find if they are same (Important) - Different wallet software could set different birthday/gap