From: Christopher Allen <ChristopherA@lifewithalacrity•com>
To: Pieter Wuille <pieter.wuille@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] 32-byte public keys in Schnorr and Taproot
Date: Fri, 9 Aug 2019 11:37:13 -0700 [thread overview]
Message-ID: <CACrqygAn0Zq5nseVRUojm0_OLdV=ioPX+1FmUmBvU2NeGzH27w@mail.gmail.com> (raw)
In-Reply-To: <CAPg+sBhDQ5yS-BemRWqSxV7TJaWNFs7d-zD6p5HtquFwUjDdsg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 889 bytes --]
On Fri, Aug 9, 2019 at 11:17 AM Pieter Wuille via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> if we're going to change things, it's perhaps best to do it as cleanly as
> possible and also drop that byte.
>
I personally lean toward just dropping the byte. I like the simplicity and
I really like 32 bytes. 33 seems so over the edge and so odd ;-)
Yes, there may be some prototype implementations out there that did some
extra work, and will need to be revised, but that is always the risk
developers take when writing code when the spec hasn't fully been
implemented yet.
If you do revise the spec, would you consider proposing a format for
sharing public keys in a non-binary form, maybe using bech32? Given some of
the protocols emerging that may use Schnorr public keys in novel ways,
having a single encoding format for them would be useful.
-- Christopher Allen
[-- Attachment #2: Type: text/html, Size: 1286 bytes --]
next prev parent reply other threads:[~2019-08-09 18:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-09 18:16 Pieter Wuille
2019-08-09 18:37 ` Christopher Allen [this message]
2019-08-11 6:08 ` 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='CACrqygAn0Zq5nseVRUojm0_OLdV=ioPX+1FmUmBvU2NeGzH27w@mail.gmail.com' \
--to=christophera@lifewithalacrity$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=pieter.wuille@gmail$(echo .)com \
/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