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
|
Return-Path: <jlrubin@mit.edu>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133])
by lists.linuxfoundation.org (Postfix) with ESMTP id 9FA7AC000E
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 4 Jul 2021 17:30:33 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp2.osuosl.org (Postfix) with ESMTP id 80ED14014F
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 4 Jul 2021 17:30:33 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3,
SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from smtp2.osuosl.org ([127.0.0.1])
by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id LadhqgIEgx-7
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 4 Jul 2021 17:30:32 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11])
by smtp2.osuosl.org (Postfix) with ESMTPS id 6488C400C4
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 4 Jul 2021 17:30:32 +0000 (UTC)
Received: from mail-il1-f181.google.com (mail-il1-f181.google.com
[209.85.166.181]) (authenticated bits=0)
(User authenticated as jlrubin@ATHENA.MIT.EDU)
by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 164HUU4F007586
(version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT)
for <bitcoin-dev@lists.linuxfoundation.org>; Sun, 4 Jul 2021 13:30:30 -0400
Received: by mail-il1-f181.google.com with SMTP id g3so15106436ilj.7
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 04 Jul 2021 10:30:30 -0700 (PDT)
X-Gm-Message-State: AOAM5314Th6ZiaxCzoNazysorjMM3lF2idLPdqflf4TDCtVktWVb79fY
Xu+Z6uOy5zjakLlwjORr4OzqhFjZW2js2oTLU6Y=
X-Google-Smtp-Source: ABdhPJxhNRD80l8LDPR7NkiiyR9tQP8+Ah4jrG7Xdgpp/+wqYq40cFnkfOgcHJlsUeXQGHsz7HGwzPGS9glIOowML1M=
X-Received: by 2002:a92:3009:: with SMTP id x9mr7387976ile.49.1625419830173;
Sun, 04 Jul 2021 10:30:30 -0700 (PDT)
MIME-Version: 1.0
References: <CAD5xwhjmu-Eee47Ho5eA6E6+aAdnchLU0OVZo=RTHaXnN17x8A@mail.gmail.com>
<CAMZUoK=-jrH+fr=tUTHmLojm2-Ff99KYm9H97yhd=7bcOVG=fg@mail.gmail.com>
<CAD5xwhg0N1byx-G2tk=jjmZSHSBirpaX6OHTnh_x9iDEVF8PrQ@mail.gmail.com>
<CAMZUoKnYAKum63fRUNJD-zAZX_p3MoFULGWRE7J2QkO69nOe8g@mail.gmail.com>
In-Reply-To: <CAMZUoKnYAKum63fRUNJD-zAZX_p3MoFULGWRE7J2QkO69nOe8g@mail.gmail.com>
From: Jeremy <jlrubin@mit.edu>
Date: Sun, 4 Jul 2021 10:30:18 -0700
X-Gmail-Original-Message-ID: <CAD5xwhgtsqAX99NJRU6t-s14aF7frGZxFCL3-c9iBOYrkN_A_w@mail.gmail.com>
Message-ID: <CAD5xwhgtsqAX99NJRU6t-s14aF7frGZxFCL3-c9iBOYrkN_A_w@mail.gmail.com>
To: "Russell O'Connor" <roconnor@blockstream.com>
Content-Type: multipart/alternative; boundary="00000000000096a79605c64f8b10"
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] CHECKSIGFROMSTACK/{Verify} BIP for Bitcoin
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: Sun, 04 Jul 2021 17:30:33 -0000
--00000000000096a79605c64f8b10
Content-Type: text/plain; charset="UTF-8"
I don't really see the point of CHECKSIGFROMSTACKADD since it's not bound
to the txdata? When might you use this?
And yes -- "Add OP_CHECKSIGFROMSTACK and OP_CHECKSIGFROMSTACKVERIFY to
follow the semantics from bip340-342 when witness program is v1." is a bit
light on detail for what the BIP would end up looking like. If you're able
to open up the design process a bit more on that it would be good as I
think there are some topics worth discussing at large before things proceed
with Elements (assuming feature compatibility remains a goal).
The non-prehashed argument seems OK (at the cost of an extra byte...) but
are there specific applications for !=32 arguments? I can't think of a
particular one beyond perhaps efficiency. Can we safely use 0-520 byte
arguments?
Also do you have thoughts on the other questions i posed above? E.g.
splitting R/S could be helpful w/o CAT.
--
@JeremyRubin <https://twitter.com/JeremyRubin>
<https://twitter.com/JeremyRubin>
On Sat, Jul 3, 2021 at 1:13 PM Russell O'Connor <roconnor@blockstream.com>
wrote:
> There is one line written at
> https://github.com/ElementsProject/elements/pull/949/files#r660130155.
>
--00000000000096a79605c64f8b10
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"auto"><div dir=3D"ltr"><div dir=3D"ltr">I don't really see =
the point of CHECKSIGFROMSTACKADD since it's not bound to the txdata? W=
hen might you use this?<br><br>And yes -- "Add OP_CHECKSIGFROMSTACK an=
d OP_CHECKSIGFROMSTACKVERIFY to follow the semantics from bip340-342 when w=
itness program is v1." is a bit light on detail for what the BIP would=
end up looking like. If you're able to open up the des<span class=3D"g=
mail_default" style=3D"">ign process a bit more on that it would be good as=
I think there are some topics worth discussing at large before things proc=
eed with Elements (assuming feature compatibility remains a goal).</span></=
div><div dir=3D"ltr"><br></div><div dir=3D"ltr"><div class=3D"gmail_default=
" style=3D"">The non-prehashed=C2=A0argument seems OK (at the cost of an ex=
tra byte...) but are there specific applications for !=3D32 arguments? I ca=
n't think of a particular one beyond perhaps efficiency. Can we safely =
use 0-520 byte arguments?</div><div class=3D"gmail_default" style=3D""><br>=
</div><div class=3D"gmail_default" style=3D"">Also do you have thoughts on =
the other questions i posed above? E.g. splitting R/S could be helpful w/o =
CAT.</div><br></div><div dir=3D"ltr">--<br><div><div dir=3D"ltr" data-smart=
mail=3D"gmail_signature"><div dir=3D"ltr"><a href=3D"https://twitter.com/Je=
remyRubin" target=3D"_blank" rel=3D"noreferrer">@JeremyRubin</a><a href=3D"=
https://twitter.com/JeremyRubin" target=3D"_blank" rel=3D"noreferrer"></a><=
/div></div></div><br></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" =
class=3D"gmail_attr">On Sat, Jul 3, 2021 at 1:13 PM Russell O'Connor &l=
t;<a href=3D"mailto:roconnor@blockstream.com" target=3D"_blank" rel=3D"nore=
ferrer">roconnor@blockstream.com</a>> wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;bo=
rder-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">=
<div dir=3D"ltr"><div>There is one line written at <a href=3D"https://githu=
b.com/ElementsProject/elements/pull/949/files#r660130155" target=3D"_blank"=
rel=3D"noreferrer">https://github.com/ElementsProject/elements/pull/949/fi=
les#r660130155</a>.</div></div>
</blockquote></div></div></div>
--00000000000096a79605c64f8b10--
|
