From: Luke Dashjr <luke@dashjr.org>
To: Ali Sherief <ali@notatether.com>
Cc: "bitcoin-dev@lists.linuxfoundation.org"
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP-notatether-signedmessage
Date: Fri, 5 Aug 2022 06:51:52 +0000 [thread overview]
Message-ID: <202208050651.54991.luke@dashjr.org> (raw)
In-Reply-To: <oqwpWAHa9lo-RuyC8iwnUDDMmMmQjM3i3a2wuXkN0t3GeoGdTnHoHPH90_KkaVsogyrn2hTFbUN6XKR364K3jOnplsBoKW2AaWJZfBKBqz4=@notatether.com>
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
next prev parent reply other threads:[~2022-08-05 6:52 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 ` [bitcoin-dev] BIP-notatether-signedmessage 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 [this message]
2022-08-05 7:39 ` Ali Sherief
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=202208050651.54991.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=ali@notatether.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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