From: Ali Sherief <ali@notatether•com>
To: Luke Dashjr <luke@dashjr•org>
Cc: "bitcoin-dev@lists•linuxfoundation.org"
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP-notatether-signedmessage
Date: Fri, 05 Aug 2022 07:39:38 +0000 [thread overview]
Message-ID: <Kooyh1Wd0qc2Z5wXutB6dZqImcZN2WiZJHVxKbby3x1_glXfppmpDwW7Q8ON44yrznIVdQHlWpmM0Kh32PzyiHyRtcVlBBtJWfrk0PW3e9Y=@notatether.com> (raw)
In-Reply-To: <202208050651.54991.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 2082 bytes --]
> IMO, there is no benefit to an additional message signing standard, especially
> one that doesn't address the problems with the current standard or (at
> present) BIP322.
In that case, I propose the following:
- I scrap the Taproot/Schorr and the two extensions inside the BIP, which will leave it with only parts and formats which have already been standardized (effectively, the legacy and segwit addresses).
Because here's the thing: The reason why wallets are not implementing sign/verify correctly is because there is no reference manual for doing so. This informational BIP is supposed to solve that problem by providing only a list of instructions for computing ECSDA sign/verify correctly.
Also, it is not visible right now, but there will also be a reference implementation so that wallet developers can actually code them correctly, as you've stated.
- Ali
On Fri, Aug 5, 2022 at 9:51 AM, Luke Dashjr <luke@dashjr•org> wrote:
> On Friday 05 August 2022 04:05:56 Ali Sherief wrote:
>> Yeah, I have a specific reason to advance this first (emphasis on the word
>> first).
>>
>> I briefly mentioned in the BIP that BIP322 has superior message
>> verification capabilities. This is true, but it suffers from the drawback
>> that wallets are not using it.
>
> Likely because it is a draft and incomplete.
>
>> Message signatures are highly relied upon in some places (just to name a
>> few, at many mining pools e.g. Slushpool, and the Bitcointalk forum),
>
> I'm not aware of any using the current message signatures _correctly_.
> Note they are not useful for proving that you sent a transaction, nor have the
> ability to send a transaction or access to bitcoins.
>
>> This BIP is kind of like a "bumper car", in that it forces compliance with
>> previous BIPs that extend the message signing format, in particular BIP137.
>
> BIPs can't force anything, they're just documentation.
>
> IMO, there is no benefit to an additional message signing standard, especially
> one that doesn't address the problems with the current standard or (at
> present) BIP322.
>
> Luke
[-- Attachment #2: Type: text/html, Size: 2581 bytes --]
next prev parent reply other threads:[~2022-08-05 7:39 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 [this message]
2022-08-05 9:12 ` Pavol Rusnak
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='Kooyh1Wd0qc2Z5wXutB6dZqImcZN2WiZJHVxKbby3x1_glXfppmpDwW7Q8ON44yrznIVdQHlWpmM0Kh32PzyiHyRtcVlBBtJWfrk0PW3e9Y=@notatether.com' \
--to=ali@notatether$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=luke@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