From: Pieter Wuille <pieter.wuille@gmail•com>
To: Thomas Voegtlin <thomasv@electrum•org>,
Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] proposal: extend WIF format for segwit
Date: Sat, 16 Sep 2017 19:29:41 -0700 [thread overview]
Message-ID: <CAPg+sBgukwdRvfFcgdusrXoo8RiXm8OEL-WvHzjpiD8_HU5KmQ@mail.gmail.com> (raw)
In-Reply-To: <34198916-cde9-c84d-ca41-9feb8956bd80@electrum.org>
[-- Attachment #1: Type: text/plain, Size: 869 bytes --]
On Sep 15, 2017 01:56, "Thomas Voegtlin via bitcoin-dev" <
bitcoin-dev@lists•linuxfoundation.org> wrote:
Note 3: we could also use a bech32 format for the private key, if it is
going to be used with a bech32 address. I am not sure if such a format
has been proposed already.
I've been working on an "extended bech32" format with 12 character checksum
rather than 6, for private keys and other things that need stronger
protection. It would guarantee correcting 4 errors, where normal bech32 can
only detect (but not correct) 4.
The rationale is that in the case of an address, if an error is detected,
you can ask the receiver for a corrected version. As that option doesn't
exist for private keys you want something stronger.
This has been a low-priority thing for me, though, and the computation work
to find a good checksum is significant.
Cheers,
--
Pieter
[-- Attachment #2: Type: text/html, Size: 1639 bytes --]
next prev parent reply other threads:[~2017-09-17 2:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 8:55 Thomas Voegtlin
2017-09-17 2:29 ` Pieter Wuille [this message]
2017-09-17 8:10 ` Thomas Voegtlin
2017-09-17 14:42 ` AJ West
2017-09-17 15:36 ` Mark Friedenbach
2018-04-04 6:06 ` Karl Johan Alm
2018-04-10 2:54 ` Karl-Johan Alm
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=CAPg+sBgukwdRvfFcgdusrXoo8RiXm8OEL-WvHzjpiD8_HU5KmQ@mail.gmail.com \
--to=pieter.wuille@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=thomasv@electrum$(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