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
Precedence: list

--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">&gt; 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 &lt;<a href=3D"mailto:pete@petertodd.org" target=3D"_blank">pete@pe=
tertodd.org</a>&gt; 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=
>
&gt; Quickly checked, it fails a number of standardness tests in unit/funct=
ional<br>
&gt; tests in Bitcoin Core, at least.<br>
&gt; <br>
&gt; OP_2 was actually Luke Jr&#39;s idea circa 2017 for about the same rea=
sons, I<br>
&gt; just independently arrived at the same conclusion.<br>
<br>
Well, frankly I really don&#39;t like the idea of using OP_2 just to avoid =
changing<br>
some unit tests. We&#39;re doing something that many people will use for ye=
ars to<br>
come, that&#39;s unnecessarily obscure just because we don&#39;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> &#39;peter&#39;[:-1]@<a href=3D"http://petertodd.org"=
 rel=3D"noreferrer" target=3D"_blank">petertodd.org</a><br>
</blockquote></div>

--000000000000efde0805f3bdaca7--