1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
|
Return-Path: <ali@notatether.com>
Received: from smtp4.osuosl.org (smtp4.osuosl.org [IPv6:2605:bc80:3010::137])
by lists.linuxfoundation.org (Postfix) with ESMTP id C848CC002D
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 4 Aug 2022 12:19:07 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp4.osuosl.org (Postfix) with ESMTP id 90CB741793
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 4 Aug 2022 12:19:07 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 90CB741793
Authentication-Results: smtp4.osuosl.org; dkim=pass (2048-bit key,
unprotected) header.d=notatether.com header.i=@notatether.com
header.a=rsa-sha256 header.s=protonmail header.b=ZrBNzOYH
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001,
SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from smtp4.osuosl.org ([127.0.0.1])
by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id NhTFQ2vUDBRK
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 4 Aug 2022 12:19:04 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org EC67B409EA
Received: from mail-4022.proton.ch (mail-4022.proton.ch [185.70.40.22])
by smtp4.osuosl.org (Postfix) with ESMTPS id EC67B409EA
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 4 Aug 2022 12:19:02 +0000 (UTC)
Date: Thu, 04 Aug 2022 12:18:56 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=notatether.com;
s=protonmail; t=1659615540; x=1659874740;
bh=L8uzgwV1FOWmaulUzbZgMK7o8hg8UucDdm6PbTIFA5k=;
h=Date:To:From:Cc:Reply-To:Subject:Message-ID:In-Reply-To:
References:Feedback-ID:From:To:Cc:Date:Subject:Reply-To:
Feedback-ID:Message-ID;
b=ZrBNzOYHYdn1ID+OpiTA4ndEuNP0Z8nmpC8kIaB4Ifr1StAoAKmFDVpat45ejF02E
lvYBXiq3dfWO42CpUAIF9FYpFrUpSZHyC8fv4Qnf6tOtp6PkCoRoQK9ZWWfVT3YUUO
UO6qEnugTjYtMIERwEGdQnkI0rBkY4WUbCwgrXIQmgDxzb4h22pReT9swIsKxZrocc
RJUyDyOSQYIQVAIWDJBdh4db7ESq+fccmCgNHTw9rlDEBie35xnFpuRKyWnF/JeA9t
DYrw69Y1anKawZ0bRdbvRjhcDcyqSCJlotIyScZgDbCOS4NpTBwxBVq29lEZA4eGOW
DVB+BJyRb7O7A==
To: bitcoin-dev@lists.linuxfoundation.org
From: Ali Sherief <ali@notatether.com>
Reply-To: Ali Sherief <ali@notatether.com>
Message-ID: <20220804121851.7e4zoqxaaolseazn@artanis>
In-Reply-To: <4Lz70s3l79z4x2h7@mail-41103.protonmail.ch>
References: <4Lz70s3l79z4x2h7@mail-41103.protonmail.ch>
Feedback-ID: 34210769:user:proton
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Thu, 04 Aug 2022 15:49:51 +0000
Cc: luke_bipeditor@dashjr.org
Subject: [bitcoin-dev] BIP-notatether-signedmessage
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2022 12:19:07 -0000
Hi,
I have created a new BIP, called notatether-signedmessage. It can be viewed=
at https://github.com/ZenulAbidin/bips/blob/master/bip-notatether-signedme=
ssage.mediawiki.
For those who want a quick summary, it defines a step-by-step process for s=
igning and verifying messages from legacy, native/nested segwit, and taproo=
t addresses. It does not define a new signature format itself, except in th=
e case of Taproot. For those addresses, I have defined a signature format t=
hat 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 algorith=
m using only the signature - and the header byte is added for backwards com=
patibility. Otherwise, it completely integrates BIP137 signatures.
I am planning to move that format to its own BIP as soon as possible, in li=
eu that it is unacceptable to define formats in an Informational BIP.
Please leave your comments in this mailing list. CC'ing BIP editors.
- Ali
|