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
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
|
Return-Path: <sjors@sprovoost.nl>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 4C3228FF
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 9 Dec 2017 12:57:57 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com
[66.111.4.27])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 5367A1A6
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 9 Dec 2017 12:57:56 +0000 (UTC)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
by mailout.nyi.internal (Postfix) with ESMTP id 6E2362070C;
Sat, 9 Dec 2017 07:57:55 -0500 (EST)
Received: from frontend2 ([10.202.2.161])
by compute1.internal (MEProxy); Sat, 09 Dec 2017 07:57:55 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sprovoost.nl; h=
content-type:date:from:in-reply-to:message-id:mime-version
:references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=
fm1; bh=AXe6d/h9f82VXMFzbyF5uEsd08TNWGWSLxwL0pro1q4=; b=Rjl0tbGZ
ZjFw1saP/nkmYORUt4I4y/eWsH279Mo/ov6iPCL1KkGHwGs7UE0FNZYoTkLo4S2B
EM4ZZVN9FEomJSEX7gJeDxBBcU9KUCbUb+4x0r/Cl7LVvuOEWi4YymZ8wtpN3cJu
HBHmf9ayENaxn7zyAnjsgycjzMFFO4yG8VdFsx5dM9d3vKIz+3kxNtVPuLcesbvO
HfYFrmhcr1+vFT23SykERHPOCkisPK+UpU7epV5yFL7VTC3RM11VmtqSGhw7N8/k
56oFR33zr7XRkt3HdTX0es2iNSBcPVANJoFnrUXYs4Lgu/IPkOpCMwr8Q1U9swrc
AGBUyu0/pXFtuQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
messagingengine.com; h=content-type:date:from:in-reply-to
:message-id:mime-version:references:subject:to:x-me-sender
:x-me-sender:x-sasl-enc; s=fm1; bh=AXe6d/h9f82VXMFzbyF5uEsd08TNW
GWSLxwL0pro1q4=; b=jK2qpaDM6oeaiQ9m3737laV5iSiyS9jJ7e7FaCam7AToQ
r7EsFNAm6XnPcS3rSFMvCQUITU5TixiD0CpI8mRQip5MOOFXxcaLP66oegsObEYV
gmX6o15ua6fwn5mMRgeArTAZ3tzAu8dgD9MmWnoHHoSR7+8I2EBVXLFX5HU06SdH
/8gpRXQJFUTRdGtJReX574QA6zG74y8oW6EkNJqQJDdT0MGmMlnEDzb/hbcEEssr
qICchZjGO93MSbtqAe3H9sHcSMNqkbpO0oUEWmW4iEqoDcc5K9g/J2qtk96Lb5AL
BXnFjOiqfixYNcI1az5qpbpFreDF6W/YbTxgSN7nQ==
X-ME-Sender: <xms:090rWj_cgkbak65DI1TSxwqXe9BfE-QGE7iwr_KFkbskUEQqiKDZ1w>
Received: from [192.168.178.108] (54693d0f.cm-12-2a.dynamic.ziggo.nl
[84.105.61.15])
by mail.messagingengine.com (Postfix) with ESMTPA id 932FD24536;
Sat, 9 Dec 2017 07:57:54 -0500 (EST)
From: Sjors Provoost <sjors@sprovoost.nl>
Content-Type: multipart/signed;
boundary="Apple-Mail=_1E94DC79-33A7-48B9-BC12-506FF1090FC6";
protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Date: Sat, 9 Dec 2017 13:57:52 +0100
References: <CAAUFj10gEPBS3nTZ6aJn4UazhcJKPni6_pYGWwOs+QNeDo9NaA@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
DKBryant@gmail.com
In-Reply-To: <CAAUFj10gEPBS3nTZ6aJn4UazhcJKPni6_pYGWwOs+QNeDo9NaA@mail.gmail.com>
Message-Id: <69F75C75-6E51-4189-B3AE-032573B49A92@sprovoost.nl>
X-Mailer: Apple Mail (2.3445.4.7)
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham
version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Sat, 09 Dec 2017 14:28:13 +0000
Subject: Re: [bitcoin-dev] Sign / Verify message against SegWit P2SH
addresses.
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
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: Sat, 09 Dec 2017 12:57:57 -0000
--Apple-Mail=_1E94DC79-33A7-48B9-BC12-506FF1090FC6
Content-Type: multipart/alternative;
boundary="Apple-Mail=_924940A3-557F-4C07-8EE5-C6676A048BF0"
--Apple-Mail=_924940A3-557F-4C07-8EE5-C6676A048BF0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=us-ascii
I would like to see this specifically for P2SH-PWPKH and/or native =
SegWit bech32 addresses.
Use cases I can think of are "I'm the whale in charge of these funds, =
listen to me" and some form of polling.
It's nice if funds aren't excluded from these type of functionalities =
just because they have a complicated redeem script. So something more =
generic like the Elements implementation / suggestion Greg Maxwell =
referred to in the Github thread would be nice too.
Is it also useful or possible to sign a message proving you are able to =
redeem some arbitrary branch in a MAST-like tree of scripts? What about =
being a minority part of a multisig?
All these features have privacy trade-offs, as well as perhaps security =
trade-offs, e.g. when you reveal a public key that was otherwise hidden =
behind a hash (i.e. if someone were to break secp256k1, they'd first =
organize a popular poll).
There's no BIP for the current message signing mechanism either afaik.
Sjors
> Op 8 dec. 2017, om 19:25 heeft Dan Bryant via bitcoin-dev =
<bitcoin-dev@lists.linuxfoundation.org> het volgende geschreven:
>=20
> I know there are posts, and an issue opened against it, but is there =
anyone writing a BIP for Sign / Verify message against a SegWit address?
>=20
> I realize it is not a feature in wide use, but I think it still serves =
an important purpose, such as when proof of assets are requested.
>=20
> ref: https://github.com/bitcoin/bitcoin/issues/10542 =
<https://github.com/bitcoin/bitcoin/issues/10542>
>=20
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
--Apple-Mail=_924940A3-557F-4C07-8EE5-C6676A048BF0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=us-ascii
<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">I =
would like to see this specifically for P2SH-PWPKH and/or native =
SegWit bech32 addresses.<div class=3D""><br class=3D""></div><div =
class=3D"">Use cases I can think of are "I'm the whale in charge of =
these funds, listen to me" and some form of polling.</div><div =
class=3D""><br class=3D""></div><div class=3D"">It's nice if funds =
aren't excluded from these type of functionalities just because they =
have a complicated redeem script. So something more generic like the =
Elements implementation / suggestion Greg Maxwell referred to in the =
Github thread would be nice too.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Is it also useful or possible to sign a =
message proving you are able to redeem some arbitrary branch in a =
MAST-like tree of scripts? What about being a minority part of a =
multisig?</div><div class=3D""><br class=3D""></div><div class=3D"">All =
these features have privacy trade-offs, as well as perhaps security =
trade-offs, e.g. when you reveal a public key that was otherwise hidden =
behind a hash (i.e. if someone were to break secp256k1, they'd first =
organize a popular poll).<br class=3D""><div class=3D""><br =
class=3D""></div><div class=3D"">There's no BIP for the current message =
signing mechanism either afaik.<br class=3D""><div class=3D""><br =
class=3D""></div><div class=3D"">Sjors<br class=3D""><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">Op 8 =
dec. 2017, om 19:25 heeft Dan Bryant via bitcoin-dev <<a =
href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" =
class=3D"">bitcoin-dev@lists.linuxfoundation.org</a>> het volgende =
geschreven:</div><br class=3D"Apple-interchange-newline"><div =
class=3D""><div dir=3D"ltr" class=3D"">I know there are posts, and an =
issue opened against it, but is there anyone writing a BIP for Sign / =
Verify message against a SegWit address?<div class=3D""><br =
class=3D""></div><div class=3D"">I realize it is not a feature in wide =
use, but I think it still serves an important purpose, such as when =
proof of assets are requested.<br class=3D""><div class=3D""><br =
class=3D""></div><div class=3D"">ref: <a =
href=3D"https://github.com/bitcoin/bitcoin/issues/10542" =
class=3D"">https://github.com/bitcoin/bitcoin/issues/10542</a></div></div>=
<div class=3D""><br class=3D""></div></div>
_______________________________________________<br class=3D"">bitcoin-dev =
mailing list<br class=3D""><a =
href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" =
class=3D"">bitcoin-dev@lists.linuxfoundation.org</a><br =
class=3D"">https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev<=
br class=3D""></div></blockquote></div><br =
class=3D""></div></div></div></body></html>=
--Apple-Mail=_924940A3-557F-4C07-8EE5-C6676A048BF0--
--Apple-Mail=_1E94DC79-33A7-48B9-BC12-506FF1090FC6
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE7ZvfetalXiMuhFJCV/+b28wwEAkFAlor3dAACgkQV/+b28ww
EAkzxhAAuRhAdzXrPE+/xxdeltSDHRq5LArPA+mfY730kmUA/Kksc6AE3TlZWef+
Cgcf3Yngb5Uvj64QP4qw1h7LiDTmvW67Yd8e1Yac7WxZR4ArMWZ4gf61gc2J4Jzl
+i4Yp56MJdy6MJ/MDvNIjKi801FMKgDzDDsbn/4sBVUiJhzdG8xhw6WlYU0XWwFc
PPxAoaV1VoXcRwJuS7NJfHDTU81QciUYELeLLPydgpx2CjzFsmRFv7+Dkg85df3/
ZiCdvLMJ1gx4+IdN0jzlPiM/w7i0R8Y+9tpxSoBp5EtXq7zGHtbZs/icqrl8NBE7
/Bvb+EMi1iczJ8dRh+sBbc430ehvdYPGpfq6t5uaWQb5rm6snVezX9z16L0OIhpy
x4JlfOkSTgNdbrKlXfIAUVzafe4BHWXsfxXnXxEtdXBqpjKmJOySuYUaL/+j1V+L
pr2LdFh1xte07Al+nIEhLllA7TISf7p0aAYr+rCqv1ili5J4HfB0p1vb2fOJSf7e
6VEfDWjNkk2b7QkWVcHmg5eo2Gl0yQ0aR+0lRrsYAx8Dd1EYiKCZ41zuQ6Ap+bSe
S+VYbI22s2TZbuMAuI1MVJREKTXbH7oNrR8bYdS69zLt4d8L30azJYoPjy+GjDMg
Vwc0/MCihtY13Ie3MCE+R+r0oo+I1c9cRaeFAueqIy/LWF6KUsc=
=buoc
-----END PGP SIGNATURE-----
--Apple-Mail=_1E94DC79-33A7-48B9-BC12-506FF1090FC6--
|
