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
|
Return-Path: <roconnor@blockstream.com>
Received: from hemlock.osuosl.org (smtp2.osuosl.org [140.211.166.133])
by lists.linuxfoundation.org (Postfix) with ESMTP id 5F369C016F
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 2 May 2020 21:16:04 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by hemlock.osuosl.org (Postfix) with ESMTP id 471EA8879D
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 2 May 2020 21:16:04 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
Received: from hemlock.osuosl.org ([127.0.0.1])
by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id 5-0argF7bXhE
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 2 May 2020 21:16:03 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from mail-io1-f51.google.com (mail-io1-f51.google.com
[209.85.166.51])
by hemlock.osuosl.org (Postfix) with ESMTPS id 8ACFD88780
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 2 May 2020 21:16:03 +0000 (UTC)
Received: by mail-io1-f51.google.com with SMTP id j8so4081988iog.13
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 02 May 2020 14:16:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=blockstream-com.20150623.gappssmtp.com; s=20150623;
h=mime-version:references:in-reply-to:from:date:message-id:subject:to
:cc; bh=yS6992f3v+N1nAspMU9G4frmEvI6aGmlII46UER2MgI=;
b=gmuWQCcy0/nOv3jGogPbVaPFhuH4uz8e+KtSOXRbUaVVrTzNcgwXR7Mmh8g6UMEZsv
c8th/emGwiGLLkllfE6geSuHXld2N1xhlArDFrgxKNxLDfmkFGVtWWlvJEL2+yTiTcHt
aKKD8XF9TysatPo9yHlOuTV3a/PIUBDxf2h1+ML8eVvJNDcCnpf5tEPIgwG//Pqm/OdQ
9T2rNE2PoIYvwwDnin5UkTxm/l6FGq+6ddDwrSvCrXVWeCkec+At/agaALVd1oyzb7dO
qRjfr1r7AYHyDeaJYbpYW0h7yeEaERiFKv+4wRrYonkm0OtW4APZ35mjbrNiKWTQlxsf
AhFg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:references:in-reply-to:from:date
:message-id:subject:to:cc;
bh=yS6992f3v+N1nAspMU9G4frmEvI6aGmlII46UER2MgI=;
b=P/GDJapkWzmnZGDSSCtRXwQDZ2fyLl/KbpF7vBrjq6CwYffsfqfErjF8GGGX59kvuH
c5FVbPz2VrG5XllGyrQeT8g4PGI98wCEVX6NQV73PoW7GJq/SLV4viLQ2qH9dLoqa5b6
a38AOonUm3H5KaZvYJ4jriBlS7rxsADetRp4PLkL5S57DE2WDtPPaiiYGnpA3XuxAL4A
dlRitL6UvULowvn994+u+PalErHr8zHfAMgB45uGdlO73ICdVi+uvShNy1KWpLOVR909
GIhdseZD49YYzHIHa2Wx5OcYC1Xz4VmGiPSv1dBv6166L/TKO6AygE1zutl98YP6T1wH
GcZA==
X-Gm-Message-State: AGi0PuZf5QssYKgLPWZr33/vlE/NN3A7zAuOnhJEysVzuBTKi57R02ko
PpPLVh0DSreRAy1Uv0B+K3/bpTq1MdZEIY2Xgv0NuQ==
X-Google-Smtp-Source: APiQypJRJh7xoKSpuaTZkLCH4w9we6HDUymELiwfaFGuMuJIMSfle2NOm9nNCy31nE+caaQN+eYHwdzWnX/MuBPWrbQ=
X-Received: by 2002:a6b:e413:: with SMTP id u19mr9358631iog.206.1588454162734;
Sat, 02 May 2020 14:16:02 -0700 (PDT)
MIME-Version: 1.0
References: <CACvH2e=3s2kZWnytMySTv8U4pny3i0rEWas7NxzLxf5J7BewTg@mail.gmail.com>
<CAMZUoKm9sogtKS0YqOz8JNNbiiwBdkPbdEvf67yzcJr1BZ7_wA@mail.gmail.com>
<20200502142602.rj7q2m32ew6trh6u@erisian.com.au>
In-Reply-To: <20200502142602.rj7q2m32ew6trh6u@erisian.com.au>
From: "Russell O'Connor" <roconnor@blockstream.com>
Date: Sat, 2 May 2020 17:15:51 -0400
Message-ID: <CAMZUoKmrD78naPBcfGsfr_OxyYiWM+G47sWtpNGP+u-9r4MjXA@mail.gmail.com>
To: Anthony Towns <aj@erisian.com.au>
Content-Type: multipart/alternative; boundary="0000000000001cb04505a4b0ce8b"
Cc: jonasd.nick@gmail.com,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
Pieter Wuille <pieter.wuille@gmail.com>
Subject: Re: [bitcoin-dev] BIP-341: Committing to all scriptPubKeys in the
signature message
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: Sat, 02 May 2020 21:16:04 -0000
--0000000000001cb04505a4b0ce8b
Content-Type: text/plain; charset="UTF-8"
On Sat, May 2, 2020 at 10:26 AM Anthony Towns <aj@erisian.com.au> wrote:
>
> except that we'd arguably still be missing:
>
> is this a coinbase output? (Coin.fCoinBase)
> what was the height of the coin? (Coin.nHeight)
>
> Maybe committing to the coinbase flag would have some use, but committing
> to the height would make it hard to chain unconfirmed spends, so at
> least that part doesn't seem worth adding.
>
To add to this point, the height of the coin is something that is *not*
currently covered by any signature mode and including it would constitute a
change of an entirely different caliber; a change that I would strongly
caution against for your above reason and more.
The coinbase output flag is currently covered by the signature as the
outpoint hash has the required information (its prevout index of 0xFFFFFFFF
is only legal in a coinbase transaction). While I'm not particularly
enthusiastic about making it easier to distinguish coinbase outputs from
other outputs, and I worry a little about alternative designs for
implementing the Bitcoin protocol where this information is not so readily
available, I suppose I won't really oppose adding it. However, I don't
think anyone is seriously proposing it.
-
--0000000000001cb04505a4b0ce8b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail=
_attr">On Sat, May 2, 2020 at 10:26 AM Anthony Towns <<a href=3D"mailto:=
aj@erisian.com.au">aj@erisian.com.au</a>> wrote:<br></div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid=
rgb(204,204,204);padding-left:1ex"><br>
except that we'd arguably still be missing:<br>
<br>
=C2=A0 =C2=A0 is this a coinbase output? (Coin.fCoinBase)<br>
=C2=A0 =C2=A0 what was the height of the coin? (Coin.nHeight)<br>
<br>
Maybe committing to the coinbase flag would have some use, but committing<b=
r>
to the height would make it hard to chain unconfirmed spends, so at<br>
least that part doesn't seem worth adding.<br></blockquote><div><br></d=
iv><div>To add to this point, the height of the coin is something that is *=
not* currently covered by any signature mode and including it would constit=
ute a change of an entirely different=C2=A0 caliber; a change that I would =
strongly caution against for your above reason and more.</div><div><br></di=
v><div>The coinbase output flag is currently covered by the signature as th=
e outpoint hash has the required information (its prevout index of 0xFFFFFF=
FF is only legal in a coinbase transaction).=C2=A0 While I'm not partic=
ularly enthusiastic about making it easier to distinguish coinbase outputs =
from other outputs, and I worry a little about alternative designs for impl=
ementing the Bitcoin protocol where this information is not so readily avai=
lable, I suppose I won't really oppose adding it.=C2=A0 However, I don&=
#39;t think anyone is seriously proposing it.<br><li></li></div></div></div=
>
--0000000000001cb04505a4b0ce8b--
|
