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
|
Return-Path: <gsanders87@gmail.com>
Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137])
by lists.linuxfoundation.org (Postfix) with ESMTP id 9A1BFC002B
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 2 Feb 2023 20:47:43 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp4.osuosl.org (Postfix) with ESMTP id 81AC941D22
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 2 Feb 2023 20:47:43 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 81AC941D22
Authentication-Results: smtp4.osuosl.org;
dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com
header.a=rsa-sha256 header.s=20210112 header.b=jsUTjY9Z
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level:
X-Spam-Status: No, score=-1.848 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,
FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001,
HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 2xAd6K7dGNqu
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 2 Feb 2023 20:47:41 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 6A83F41D21
Received: from mail-ej1-x62e.google.com (mail-ej1-x62e.google.com
[IPv6:2a00:1450:4864:20::62e])
by smtp4.osuosl.org (Postfix) with ESMTPS id 6A83F41D21
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 2 Feb 2023 20:47:41 +0000 (UTC)
Received: by mail-ej1-x62e.google.com with SMTP id gr7so9606467ejb.5
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 02 Feb 2023 12:47:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;
h=cc:to:subject:message-id:date:from:in-reply-to:references
:mime-version:from:to:cc:subject:date:message-id:reply-to;
bh=dwdg4B13RebDHmNJQM+jlU9ssehEOHOICOkpJSsTmlQ=;
b=jsUTjY9Z60KdL3YhYWFTucugyDOUROya75O/roKBKgfWQ+GpDslLH+grOrGgVZ7o69
2/EF+GzzBZEvfIOCmTWkn1Brp+snnAt8HqPo0YtiZoU4sX4g92kxvUJ5IxMs5RufRnu/
pKIlvBN0dD8hmanPOZ+GqxQVM7zaUndaJZTrJ3AP4FQ8dxr8uG8ai3uIVWKMx9x5r1Lx
hPseWlCZ/pIwnOgBFUoJHkMFo6/1XFqtvos4M5cRpdAF7DIN/UCcClPYFtTyuxoKsNfM
evVYYXzzCj9IV5DetUNnl6mwzYWhCJV3QmiZYNm4G0zIpMLmOKg2vuP3ET2DAxZmQcFe
C68g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20210112;
h=cc:to:subject:message-id:date:from:in-reply-to:references
:mime-version:x-gm-message-state:from:to:cc:subject:date:message-id
:reply-to;
bh=dwdg4B13RebDHmNJQM+jlU9ssehEOHOICOkpJSsTmlQ=;
b=RmbyQ8FJleLV3DavKUvNxxM669giKbqOYH18RneB9Lc3hZm0gTgenfHAvw6EH5qefU
NEp1CtKu1gSB5IIqdQWrnHF/NYuqsIk+w5IwUIDJZJxxpKXqI3C4CLlC4CUoyAXu6mHC
CJKRz/Q3X4Yoj3Dj9MrQ93n63IXgTCmWUgKPPyG4Eomz1SWJVNx/99tcdcg23Qx63b9a
F7vxFF0RGJ8WqSV49S2yXgvNymCKcIL2SEAvxzrNZ+t8MrG0GWlcZO4kX1aVT/19FY+n
8WWjGMzQXGYLPoz3Fpcfv0GHe5m2LA8KkvfmQ7DyMktmr129Pt4Por1guRts/VunVjpD
tyGw==
X-Gm-Message-State: AO0yUKVDOov8PKNH3xhZEv322d4BCqZPT/z9SQ0Q+Mfq02HUX3zS3vmJ
Lbqh1CwjnaMwX+N02CN83HnbE7T7am8JtB9tZGtcyDfy
X-Google-Smtp-Source: AK7set80AxS8kmfGM6ZJoij/CO/lFDd5ggOsxXxHlMCgr2xwBgAceONNiv6q1+j0Z3fjXZZPtHiuRooyTM1Wc4oupz4=
X-Received: by 2002:a17:906:1806:b0:882:4e87:8848 with SMTP id
v6-20020a170906180600b008824e878848mr2635472eje.86.1675370859321; Thu, 02 Feb
2023 12:47:39 -0800 (PST)
MIME-Version: 1.0
References: <CAB3F3DvH3FnK8krykbcRVKc-z8F4yjt9mzYHevpYxaWkH4w9tw@mail.gmail.com>
<CAD5xwhgFBQ-ScyBU5=WnREGsN-T=Nv=oR6vOsnHJ-ZMzDF8Vqg@mail.gmail.com>
<CAPfvXf+N8aF+bqjGzpfDrhCYg7ngciSDCpUnCMHD+k5F+m3oWA@mail.gmail.com>
<CAB3F3DuDODUxB5aK4VFWa8sKFCkZfOj6Vjb+Wp39opyt8MNnEA@mail.gmail.com>
<CAB3F3DtrSFPmperGJJAUDZj7vt9aHgvkc0b5Pts3+mq5fTuWXA@mail.gmail.com>
<CAB3F3DvToF_fia+X5SQi-L=BDYGLpzr8nNHqjtFBUjLMbyPE9Q@mail.gmail.com>
<Y9vOGVMJx1b9CPYq@petertodd.org>
<CAB3F3Du2XsHCh5o5S84XKKizTkrTFJJ-j42-qunyuSRkwX7H_Q@mail.gmail.com>
<Y9vRjQVnZzA8Bx/s@petertodd.org>
<CAB3F3DvumE-r+LGm8ivooPD9qfzFs-NK9Ve06Ew1EMAifSx8dw@mail.gmail.com>
<Y9wbjsmPO+nyM267@petertodd.org>
In-Reply-To: <Y9wbjsmPO+nyM267@petertodd.org>
From: Greg Sanders <gsanders87@gmail.com>
Date: Thu, 2 Feb 2023 15:47:28 -0500
Message-ID: <CAB3F3Ds7Ux8MWnY-9Agehpk0hZx_xgeFmZG7hUjMkfe48T5GPA@mail.gmail.com>
To: Peter Todd <pete@petertodd.org>
Content-Type: multipart/alternative; boundary="000000000000efde0805f3bdaca7"
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Ephemeral Anchors: Fixing V3 Package RBF
againstpackage limit pinning
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, 02 Feb 2023 20:47:43 -0000
--000000000000efde0805f3bdaca7
Content-Type: text/plain; charset="UTF-8"
> OP_TRUE is the obvious way to do this, and it results with a 1 on the
stack,
which plays better with other standardness rules.
What other standardness rules? MINAMALIF? How does that interact with the
proposal?
On Thu, Feb 2, 2023 at 3:22 PM Peter Todd <pete@petertodd.org> wrote:
> On Thu, Feb 02, 2023 at 01:36:24PM -0500, Greg Sanders wrote:
> > Quickly checked, it fails a number of standardness tests in
> unit/functional
> > tests in Bitcoin Core, at least.
> >
> > OP_2 was actually Luke Jr's idea circa 2017 for about the same reasons, I
> > just independently arrived at the same conclusion.
>
> Well, frankly I really don't like the idea of using OP_2 just to avoid
> changing
> some unit tests. We're doing something that many people will use for years
> to
> come, that's unnecessarily obscure just because we don't want to spend a
> bit of
> some modifying some tests to pass.
>
> OP_TRUE is the obvious way to do this, and it results with a 1 on the
> stack,
> which plays better with other standardness rules. OP_2 means we *also* may
> need
> to special case having a 2 on the stack in certain implementations of other
> standardness rules.
>
> --
> https://petertodd.org 'peter'[:-1]@petertodd.org
>
--000000000000efde0805f3bdaca7
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">> OP_TRUE is the obvious way to do this, and it results=
with a 1 on the stack,<br>which plays better with other standardness rules=
.=C2=A0<div><br></div><div>What other standardness rules? MINAMALIF? How do=
es that interact with the proposal?</div></div><br><div class=3D"gmail_quot=
e"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Feb 2, 2023 at 3:22 PM Pet=
er Todd <<a href=3D"mailto:pete@petertodd.org" target=3D"_blank">pete@pe=
tertodd.org</a>> wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">On Thu, Feb 02, 2023 at 01:36:24PM -0500, Greg Sanders wrote:<br=
>
> Quickly checked, it fails a number of standardness tests in unit/funct=
ional<br>
> tests in Bitcoin Core, at least.<br>
> <br>
> OP_2 was actually Luke Jr's idea circa 2017 for about the same rea=
sons, I<br>
> just independently arrived at the same conclusion.<br>
<br>
Well, frankly I really don't like the idea of using OP_2 just to avoid =
changing<br>
some unit tests. We're doing something that many people will use for ye=
ars to<br>
come, that's unnecessarily obscure just because we don't want to sp=
end a bit of<br>
some modifying some tests to pass.<br>
<br>
OP_TRUE is the obvious way to do this, and it results with a 1 on the stack=
,<br>
which plays better with other standardness rules. OP_2 means we *also* may =
need<br>
to special case having a 2 on the stack in certain implementations of other=
<br>
standardness rules.<br>
<br>
-- <br>
<a href=3D"https://petertodd.org" rel=3D"noreferrer" target=3D"_blank">http=
s://petertodd.org</a> 'peter'[:-1]@<a href=3D"http://petertodd.org"=
rel=3D"noreferrer" target=3D"_blank">petertodd.org</a><br>
</blockquote></div>
--000000000000efde0805f3bdaca7--
|
