From: Pavol Rusnak <stick@satoshilabs•com>
To: Ali Sherief <ali@notatether•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Cc: luke_bipeditor@dashjr•org
Subject: Re: [bitcoin-dev] BIP-notatether-signedmessage
Date: Fri, 5 Aug 2022 11:12:20 +0200 [thread overview]
Message-ID: <CAF90AvmxH-fr1qnL7McdvBs56N5G-q8OYLj+dmBGSVm38F=Urg@mail.gmail.com> (raw)
In-Reply-To: <20220804121851.7e4zoqxaaolseazn@artanis>
[-- Attachment #1: Type: text/plain, Size: 1924 bytes --]
Hi Ali!
Nice work. Since it seems this is a strict superset of BIP137, why not just
focus on things that you are adding (Taproot) while saying your BIP is an
expansion of BIP137?
Your approach make it unnecessarily hard to figure out whether you are
changing anything in handling of ECDSA signature types or not. If it was
clearly stated you are just expanding BIP137 and removes everything that’s
already described in BIP137, it would be much more obvious to everyone.
On Thu 4. 8. 2022 at 17:49, Ali Sherief via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> Hi,
>
> I have created a new BIP, called notatether-signedmessage. It can be
> viewed at
> https://github.com/ZenulAbidin/bips/blob/master/bip-notatether-signedmessage.mediawiki
> .
>
> For those who want a quick summary, it defines a step-by-step process for
> signing and verifying messages from legacy, native/nested segwit, and
> taproot addresses. It does not define a new signature format itself, except
> in the case of Taproot. For those addresses, I have defined a signature
> format that has 1 byte header/recID, 64 bytes signature, and 32 bytes x
> coordinate of a public key. This is required to run the BIP340 Schnorr
> verify algorithm using only the signature - and the header byte is added
> for backwards compatibility. Otherwise, it completely integrates BIP137
> signatures.
>
> I am planning to move that format to its own BIP as soon as possible, in
> lieu that it is unacceptable to define formats in an Informational BIP.
>
> Please leave your comments in this mailing list. CC'ing BIP editors.
>
> - Ali
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--
Best Regards / S pozdravom,
Pavol "stick" Rusnak
Co-Founder, SatoshiLabs
[-- Attachment #2: Type: text/html, Size: 2893 bytes --]
next prev parent reply other threads:[~2022-08-05 9:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4Lz70s3l79z4x2h7@mail-41103.protonmail.ch>
2022-08-04 12:18 ` Ali Sherief
2022-08-04 17:54 ` Ali Sherief
2022-08-04 18:36 ` Peter (Coinkite Inc)
[not found] ` <202208041926.37309.luke@dashjr.org>
2022-08-05 4:05 ` Ali Sherief
2022-08-05 6:51 ` Luke Dashjr
2022-08-05 7:39 ` Ali Sherief
2022-08-05 9:12 ` Pavol Rusnak [this message]
2022-08-05 10:52 ` Ali Sherief
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='CAF90AvmxH-fr1qnL7McdvBs56N5G-q8OYLj+dmBGSVm38F=Urg@mail.gmail.com' \
--to=stick@satoshilabs$(echo .)com \
--cc=ali@notatether$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=luke_bipeditor@dashjr$(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