MIME-Version: 1.0
References: <aa916637-befa-795a-caa1-e5ad50ce63c8@electrum.org>
In-Reply-To: <aa916637-befa-795a-caa1-e5ad50ce63c8@electrum.org>
From: Greg Sanders <gsanders87@gmail.com>
Date: Sat, 23 May 2020 11:24:28 -0400
Message-ID: <CAB3F3DuGi_Uc0cf5eGvE9ej2d1RS8CVkf7xGBjR4uRf8jAmQhA@mail.gmail.com>
To: Thomas Voegtlin <thomasv@electrum.org>, 
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="0000000000002a3a4505a65258c0"
Subject: Re: [bitcoin-dev] MIN_STANDARD_TX_NONWITNESS_SIZE and OP_RETURN
Precedence: list

--0000000000002a3a4505a65258c0
Content-Type: text/plain; charset="UTF-8"

AFAIU the number was picked to protect against CVE-2017-12842 covertly.
See: https://github.com/bitcoin/bitcoin/pull/16885
<https://github.com/bitcoin/bitcoin/pull/16885/files> which updated the
text to explicitly mention this fact.

On Sat, May 23, 2020 at 11:20 AM Thomas Voegtlin via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> Hello list,
>
> I have been trying to CPFP a transaction using OP_RETURN, because the
> remaining output value would have been lower than the dust threshold.
>
> The scriptPubkey of the output was OP_RETURN + OP_0, and there was a
> single p2wsh input.
>
> The result is a 60 bytes transaction (without witness), that gets
> rejected because it is lower than MIN_STANDARD_TX_NONWITNESS_SIZE, which
> is equal to 82 bytes.
>
> Why is that value so high? Would it make sense to lower it to 60?
>
>
> Thomas
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

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

<div dir=3D"ltr">AFAIU the number was picked to protect against=C2=A0CVE-20=
17-12842 covertly. See:=C2=A0<a href=3D"https://github.com/bitcoin/bitcoin/=
pull/16885/files">https://github.com/bitcoin/bitcoin/pull/16885</a>=C2=A0wh=
ich updated the text to explicitly mention this fact.</div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, May 23, 2020=
 at 11:20 AM Thomas Voegtlin via bitcoin-dev &lt;<a href=3D"mailto:bitcoin-=
dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.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">Hello l=
ist,<br>
<br>
I have been trying to CPFP a transaction using OP_RETURN, because the<br>
remaining output value would have been lower than the dust threshold.<br>
<br>
The scriptPubkey of the output was OP_RETURN + OP_0, and there was a<br>
single p2wsh input.<br>
<br>
The result is a 60 bytes transaction (without witness), that gets<br>
rejected because it is lower than MIN_STANDARD_TX_NONWITNESS_SIZE, which<br=
>
is equal to 82 bytes.<br>
<br>
Why is that value so high? Would it make sense to lower it to 60?<br>
<br>
<br>
Thomas<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div>

--0000000000002a3a4505a65258c0--