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
|
Return-Path: <jl2012@xbt.hk>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id EEE86C84
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 25 May 2019 07:53:43 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from sender-of-o53.zoho.com (sender-of-o53.zoho.com [135.84.80.218])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 5CED5A9
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 25 May 2019 07:53:43 +0000 (UTC)
ARC-Seal: i=1; a=rsa-sha256; t=1558770820; cv=none; d=zoho.com; s=zohoarc;
b=EXACs+OiWfbpD9MQ5g6Z5+r4Q4Efiv9ENNsq4evTvnjFO2wZWRrIId5eavT5h2EDNgyDtvA+woBcdAmtXOSYyLy/Ggp7rkTjBKjV7aGhGahh7xGWZKXsvHq+e+qztORe5tuGzqTtXNw991XGl4CeaHX3CCp43xlkLo+Oz8BzskE=
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zoho.com;
s=zohoarc; t=1558770820;
h=Content-Type:Cc:Date:From:In-Reply-To:MIME-Version:Message-ID:References:Subject:To:ARC-Authentication-Results;
bh=Hs2Y8QZW44hyZZFYTGDwbaNKgSyECPNLMBd9bXQZk+g=;
b=S1AOmHN7gtE2WJzCAxNtnkeRkSbnrXX2qbdXaqTZatgxRf6gYSdiDQ/rujAkePj40irKmpoePrc0s9pAYCB7I5frj/U4FqBDgoDOIUb6pn+/ZZ3e7Rl3mI8cN1pgY9ar1G/nmGGtpPTkeKn9alG9jIB3NddpcEKKBzYZhtePi1A=
ARC-Authentication-Results: i=1; mx.zoho.com; dkim=pass header.i=xbt.hk;
spf=pass smtp.mailfrom=jl2012@xbt.hk;
dmarc=pass header.from=<jl2012@xbt.hk> header.from=<jl2012@xbt.hk>
Received: from [192.168.1.2] (1-64-133-115.static.netvigator.com
[1.64.133.115]) by mx.zohomail.com
with SMTPS id 1558770818450679.8265088863286;
Sat, 25 May 2019 00:53:38 -0700 (PDT)
From: Johnson Lau <jl2012@xbt.hk>
Message-Id: <EB79DBDB-9C29-4699-9A06-27D1A2896661@xbt.hk>
Content-Type: multipart/alternative;
boundary="Apple-Mail=_83376121-14C6-4E7F-8110-0F1D06623EA9"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Sat, 25 May 2019 15:53:34 +0800
In-Reply-To: <CAD5xwhhsk_4+C3dROGhBZqjmiqmOO+hGYR9qawbJ9MDW0so4=Q@mail.gmail.com>
To: Jeremy <jlrubin@mit.edu>
References: <77218514-9118-4FE2-8F7F-7BB215CF2BB6@xbt.hk>
<CAD5xwhhsk_4+C3dROGhBZqjmiqmOO+hGYR9qawbJ9MDW0so4=Q@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-ZohoMailClient: External
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,HTML_MESSAGE,
RCVD_IN_DNSWL_NONE 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, 25 May 2019 12:05:39 +0000
Cc: bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Safety of committing only to transaction outputs
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, 25 May 2019 07:53:44 -0000
--Apple-Mail=_83376121-14C6-4E7F-8110-0F1D06623EA9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8
> On 25 May 2019, at 4:59 AM, Jeremy <jlrubin@mit.edu> wrote:
>=20
> Hi Johnson,
>=20
> As noted on the other thread, witness replay-ability can be helped by =
salting the taproot key or the taproot leaf script at the last stage of =
a congestion control tree.
>=20
The salt will be published when it is first spent. Salting won=E2=80=99t =
help if the address is reused.
> I also think that chaperone signatures should be opt-in; there are =
cases where we may not want them. OP_COSHV is compatible with an =
additional checksig operation.
>=20
> There are also other mechanisms that can improve the safety. Proposed =
below:
>=20
> OP_CHECKINPUTSHASHVERIFY -- allow checking that the hash of the inputs =
is a particular value. The top-level of a congestion control tree can =
check that the inputs match the desired inputs for that spend, and =
default to requiring N of N otherwise. This is replay proof! This is =
useful for other applications too.
It is circular dependent: the script has to commit to the txid, and the =
txid is a function of script
>=20
> OP_CHECKFEEVERIFY -- allowing an explicit commitment to the exact =
amount of fee limits replay to txns which were funded with the exact =
amount of the prior. If there's a mismatch, an alternative branch can be =
used. This is a generally useful mechanism, but means that transactions =
using it must have all inputs/outputs set.
>=20
This restricts replayability to input with same value, but is still =
replay-able, just like ANYPREVOUT committing to the input value
> Best,
>=20
> Jeremy
> --
> @JeremyRubin <https://twitter.com/JeremyRubin> =
<https://twitter.com/JeremyRubin>
--Apple-Mail=_83376121-14C6-4E7F-8110-0F1D06623EA9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=utf-8
<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><br =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On 25 May 2019, at 4:59 AM, Jeremy <<a =
href=3D"mailto:jlrubin@mit.edu" class=3D"">jlrubin@mit.edu</a>> =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
dir=3D"ltr" class=3D""><div class=3D"gmail_default" style=3D"font-family: =
arial, helvetica, sans-serif; font-size: small;">Hi Johnson,</div><div =
class=3D"gmail_default" style=3D"font-family: arial, helvetica, =
sans-serif; font-size: small;"><br class=3D""></div><div =
class=3D"gmail_default" style=3D"font-family: arial, helvetica, =
sans-serif; font-size: small;">As noted on the other thread, witness =
replay-ability can be helped by salting the taproot key or the taproot =
leaf script at the last stage of a congestion control tree.</div><div =
class=3D"gmail_default" style=3D"font-family: arial, helvetica, =
sans-serif; font-size: small;"><br =
class=3D""></div></div></div></blockquote><div><br =
class=3D""></div><div>The salt will be published when it is first spent. =
Salting won=E2=80=99t help if the address is reused.</div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
dir=3D"ltr" class=3D""><div class=3D"gmail_default" style=3D"font-family: =
arial, helvetica, sans-serif; font-size: small;">I also think that =
chaperone signatures should be opt-in; there are cases where we may not =
want them. OP_COSHV is compatible with an additional checksig =
operation.</div><div class=3D"gmail_default" style=3D"font-family: =
arial, helvetica, sans-serif; font-size: small;"><br class=3D""></div><div=
class=3D"gmail_default" style=3D"font-family: arial, helvetica, =
sans-serif; font-size: small;">There are also other mechanisms that can =
improve the safety. Proposed below:</div><div class=3D"gmail_default" =
style=3D"font-family: arial, helvetica, sans-serif; font-size: =
small;"><br class=3D""></div><div class=3D"gmail_default" =
style=3D"font-family: arial, helvetica, sans-serif; font-size: =
small;">OP_CHECKINPUTSHASHVERIFY -- allow checking that the hash of the =
inputs is a particular value. The top-level of a congestion control tree =
can check that the inputs match the desired inputs for that spend, and =
default to requiring N of N otherwise. This is replay proof! This is =
useful for other applications too.<br =
class=3D""></div></div></div></blockquote><div><br =
class=3D""></div><div>It is circular dependent: the script has to commit =
to the txid, and the txid is a function of script</div><div><br =
class=3D""></div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div dir=3D"ltr" class=3D""><div class=3D"gmail_default" =
style=3D"font-family: arial, helvetica, sans-serif; font-size: =
small;"><br class=3D""></div><div class=3D"gmail_default" =
style=3D"font-family: arial, helvetica, sans-serif; font-size: =
small;">OP_CHECKFEEVERIFY -- allowing an explicit commitment to the =
exact amount of fee limits replay to txns which were funded with the =
exact amount of the prior. If there's a mismatch, an alternative branch =
can be used. This is a generally useful mechanism, but means that =
transactions using it must have all inputs/outputs set.</div><div =
class=3D"gmail_default" style=3D"font-family: arial, helvetica, =
sans-serif; font-size: small;"><br =
class=3D""></div></div></div></blockquote><div><br =
class=3D""></div><div>This restricts replayability to input with same =
value, but is still replay-able, just like ANYPREVOUT committing to the =
input value</div><div><br class=3D""></div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div dir=3D"ltr" class=3D""><div =
class=3D"gmail_default" style=3D"font-family: arial, helvetica, =
sans-serif; font-size: small;">Best,</div><div class=3D"gmail_default" =
style=3D"font-family: arial, helvetica, sans-serif; font-size: =
small;"><br class=3D""></div><div class=3D"gmail_default" =
style=3D"font-family: arial, helvetica, sans-serif; font-size: =
small;">Jeremy<br class=3D""></div><div class=3D""><div dir=3D"ltr" =
class=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div =
dir=3D"ltr" class=3D"">--<br class=3D""><a =
href=3D"https://twitter.com/JeremyRubin" target=3D"_blank" =
class=3D"">@JeremyRubin</a><a href=3D"https://twitter.com/JeremyRubin" =
target=3D"_blank" =
class=3D""></a></div></div></div></div></div></blockquote></div><br =
class=3D""></body></html>=
--Apple-Mail=_83376121-14C6-4E7F-8110-0F1D06623EA9--
|
