MIME-Version: 1.0
References: <CAB3F3DtNWajm669s9a=cs+Dft0PXDu1JHchzEw+yYLmRS+YSYQ@mail.gmail.com>
 <Y1HX3cI7k91pTFUf@petertodd.org>
In-Reply-To: <Y1HX3cI7k91pTFUf@petertodd.org>
From: Greg Sanders <gsanders87@gmail.com>
Date: Thu, 20 Oct 2022 20:07:54 -0400
Message-ID: <CAB3F3DtfHHai2q4s9LehK63iAEMUmkpTWaP8dwJ+N1vU7+EBag@mail.gmail.com>
To: Peter Todd <pete@petertodd.org>
Content-Type: multipart/alternative; boundary="00000000000059374005eb803ccc"
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Relaxing minimum non-witness transaction size
 policy restriction
Precedence: list

--00000000000059374005eb803ccc
Content-Type: text/plain; charset="UTF-8"

I don't doubt the use case(it's why I opened the issue!). I didn't want the
proposal to die in case people found it odd that 61, 62, 63, but not 64
bytes ended up being broadcast able.

Perhaps this is not an issue, especially since this isn't a consensus
change like the Great Consensus Cleanup. Willing to change my proposal and
PR if people have no strong objections.

Greg

On Thu, Oct 20, 2022, 7:21 PM Peter Todd <pete@petertodd.org> wrote:

> On Tue, Oct 11, 2022 at 08:50:07AM -0400, Greg Sanders via bitcoin-dev
> wrote:
> > Hello fellow Bitcoiners,
> >
> > After looking at some fairly exotic possible transaction types, I ran
> into
> > the current policy limit requiring transactions to be 85 non-witness
> > serialized bytes. This was introduced as a covert fix to policy fix
> > for CVE-2017-12842. Later the real motivation was revealed, but the
> > "reasonable" constant chosen was not.
> >
> > I'd like to propose relaxing this to effectively the value BlueMatt
> > proposed in the Great Consensus Cleanup: 65 non-witness bytes. This would
> > allow a single input, single output transaction with 4 bytes of OP_RETURN
> > padding, rather than padding out 21 bytes to get to p2wpkh size.
> >
> > The alternative would be to also allow anything below 64 non-witness
> bytes,
> > but this seems fraught with footguns for a few bytes gain.
>
> What footguns exactly? Spending a single input to OP_RETURN with no
> payload is
> a valid use to get rid of dust in the UTXO set.
>
> --
> https://petertodd.org 'peter'[:-1]@petertodd.org
>

--00000000000059374005eb803ccc
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">I don&#39;t doubt the use case(it&#39;s why I opened the =
issue!). I didn&#39;t want the proposal to die in case people found it odd =
that 61, 62, 63, but not 64 bytes ended up being broadcast able.=C2=A0<div =
dir=3D"auto"><br></div><div dir=3D"auto">Perhaps this is not an issue, espe=
cially since this isn&#39;t a consensus change like the Great Consensus Cle=
anup. Willing to change my proposal and PR if people have no strong objecti=
ons.=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto">Greg</div></d=
iv><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On =
Thu, Oct 20, 2022, 7:21 PM Peter Todd &lt;<a href=3D"mailto:pete@petertodd.=
org">pete@petertodd.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex">On Tue, Oct 11, 2022 at 08:50:07AM -0400, Greg Sanders via bitcoin-dev =
wrote:<br>
&gt; Hello fellow Bitcoiners,<br>
&gt; <br>
&gt; After looking at some fairly exotic possible transaction types, I ran =
into<br>
&gt; the current policy limit requiring transactions to be 85 non-witness<b=
r>
&gt; serialized bytes. This was introduced as a covert fix to policy fix<br=
>
&gt; for CVE-2017-12842. Later the real motivation was revealed, but the<br=
>
&gt; &quot;reasonable&quot; constant chosen was not.<br>
&gt; <br>
&gt; I&#39;d like to propose relaxing this to effectively the value BlueMat=
t<br>
&gt; proposed in the Great Consensus Cleanup: 65 non-witness bytes. This wo=
uld<br>
&gt; allow a single input, single output transaction with 4 bytes of OP_RET=
URN<br>
&gt; padding, rather than padding out 21 bytes to get to p2wpkh size.<br>
&gt; <br>
&gt; The alternative would be to also allow anything below 64 non-witness b=
ytes,<br>
&gt; but this seems fraught with footguns for a few bytes gain.<br>
<br>
What footguns exactly? Spending a single input to OP_RETURN with no payload=
 is<br>
a valid use to get rid of dust in the UTXO set.<br>
<br>
-- <br>
<a href=3D"https://petertodd.org" rel=3D"noreferrer noreferrer" target=3D"_=
blank">https://petertodd.org</a> &#39;peter&#39;[:-1]@<a href=3D"http://pet=
ertodd.org" rel=3D"noreferrer noreferrer" target=3D"_blank">petertodd.org</=
a><br>
</blockquote></div>

--00000000000059374005eb803ccc--