MIME-Version: 1.0
References: <Lm_5F74G9G21ydrFPovvmtHWpNXcbVzZibmU80oNqFRehJjcll89-t7OXqS5Fooe0cTNxGreIREMql3Li2xUCe2T5NVyss3-CrLzISO09HY=@notatether.com>
In-Reply-To: <Lm_5F74G9G21ydrFPovvmtHWpNXcbVzZibmU80oNqFRehJjcll89-t7OXqS5Fooe0cTNxGreIREMql3Li2xUCe2T5NVyss3-CrLzISO09HY=@notatether.com>
From: Erik Aronesty <erik@q32.com>
Date: Mon, 8 May 2023 08:58:28 -0400
Message-ID: <CAJowKgJaG8ZnZMuVTSmyhMxZKb4pcMF1XM+WH8j64Gasoy1kcw@mail.gmail.com>
To: Ali Sherief <ali@notatether.com>, 
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000a29aaf05fb2e3259"
Subject: Re: [bitcoin-dev] [Mempool spam] Should we as developers reject
 non-standard Taproot transactions from full nodes?
Precedence: list

--000000000000a29aaf05fb2e3259
Content-Type: text/plain; charset="UTF-8"

probably easier just to reject any transaction where the fee is higher than
the sum of the outputs


On Mon, May 8, 2023, 7:55 AM Ali Sherief via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> Hi guys,
>
> I think everyone on this list knows what has happened to the Bitcoin
> mempool during the past 96 hours. Due to side projects such as BRC-20
> having such a high volume, real bitcoin transactions are being priced out
> and that is what is causing the massive congestion that has arguable not
> been seen since December 2017. I do not count the March 2021 congestion
> because that was only with 1-5sat/vbyte.
>
> Such justifiably worthless ("worthless" is not even my word - that's how
> its creator described them[1]) tokens threaten the smooth and normal use of
> the Bitcoin network as a peer-to-pear digital currency, as it was intended
> to be used as.
>
> If the volume does not die down over the next few weeks, should we take an
> action? The bitcoin network is a triumvirate of developers, miners, and
> users. Considering that miners are largely the entities at fault for
> allowing the system to be abused like this, the harmony of Bitcoin
> transactions is being disrupted right now. Although this community has a
> strong history of not putting its fingers into pies unless absolutely
> necessary - an example being during the block size wars and Segwit - should
> similar action be taken now, in the form of i) BIPs and/or ii) commits into
> the Bitcoin Core codebase, to curtail the loophole in BIP 342 (which
> defines the validation rules for Taproot scripts) which has allowed these
> unintended consequences?
>
> An alternative would be to enforce this "censorship" at the node level and
> introduce a run-time option to instantly prune all non-standard Taproot
> transactions. This will be easier to implement, but won't hit the road
> until minimum next release.
>
> I know that some people will have their criticisms about this,
> absolutists/libertarians/maximum-freedom advocates, which is fine, but we
> need to find a solution for this that fits everyone's common ground. We
> indirectly allowed this to happen, which previously wasn't possible before.
> So we also have a responsibility to do something to ensure that this kind
> of congestion can never happen again using Taproot.
>
> -Ali
>
> ---
>
> [1]:
> https://www.coindesk.com/consensus-magazine/2023/05/05/pump-the-brcs-the-promise-and-peril-of-bitcoin-backed-tokens/
> <https://www.coindesk.com/consensus-magazine/2023/05/05/pump-the-brcs-the-promise-and-peril-of-bitcoin-backed-tokens/?outputType=amp>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

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

<div dir=3D"auto">probably easier just to reject any transaction where the =
fee is higher than the sum of the outputs<div dir=3D"auto"><br></div><div d=
ir=3D"auto"><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr"=
 class=3D"gmail_attr">On Mon, May 8, 2023, 7:55 AM Ali Sherief via bitcoin-=
dev &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-de=
v@lists.linuxfoundation.org</a>&gt; wrote:<br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex"><div style=3D"font-family:Arial,sans-serif;font-size:14px">Hi guys,=
</div><div style=3D"font-family:Arial,sans-serif;font-size:14px"><br></div>=
<div style=3D"font-family:Arial,sans-serif;font-size:14px">I think everyone=
 on this list knows what has happened to the Bitcoin mempool during the pas=
t 96 hours. Due to side projects such as BRC-20 having such a high volume, =
real bitcoin transactions are being priced out and that is what is causing =
the massive congestion that has arguable not been seen since December 2017.=
 I do not count the March 2021 congestion because that was only with 1-5sat=
/vbyte.</div><div style=3D"font-family:Arial,sans-serif;font-size:14px"><br=
></div><div style=3D"font-family:Arial,sans-serif;font-size:14px">Such just=
ifiably worthless (&quot;worthless&quot; is not even my word - that&#39;s h=
ow its creator described them[1]) tokens threaten the smooth and normal use=
 of the Bitcoin network as a peer-to-pear digital currency, as it was inten=
ded to be used as.</div><div style=3D"font-family:Arial,sans-serif;font-siz=
e:14px"><br></div><div style=3D"font-family:Arial,sans-serif;font-size:14px=
">If the volume does not die down over the next few weeks, should we take a=
n action? The bitcoin network is a triumvirate of developers, miners, and u=
sers. Considering that miners are largely the entities at fault for allowin=
g the system to be abused like this, the harmony of Bitcoin transactions is=
 being disrupted right now. Although this community has a strong history of=
 not putting its fingers into pies unless absolutely necessary - an example=
 being during the block size wars and Segwit - should similar action be tak=
en now, in the form of i) BIPs and/or ii) commits into the Bitcoin Core cod=
ebase, to curtail the loophole in BIP 342 (which defines the validation rul=
es for Taproot scripts) which has allowed these unintended consequences?</d=
iv><div style=3D"font-family:Arial,sans-serif;font-size:14px"><br></div><di=
v style=3D"font-family:Arial,sans-serif;font-size:14px">An alternative woul=
d be to enforce this &quot;censorship&quot; at the node level and introduce=
 a run-time option to instantly prune all non-standard Taproot transactions=
. This will be easier to implement, but won&#39;t hit the road until minimu=
m next release.</div><div style=3D"font-family:Arial,sans-serif;font-size:1=
4px"><br></div><div style=3D"font-family:Arial,sans-serif;font-size:14px">I=
 know that some people will have their criticisms about this, absolutists/l=
ibertarians/maximum-freedom advocates, which is fine, but we need to find a=
 solution for this that fits everyone&#39;s common ground. We indirectly al=
lowed this to happen, which previously wasn&#39;t possible before. So we al=
so have a responsibility to do something to ensure that this kind of conges=
tion can never happen again using Taproot.</div><div style=3D"font-family:A=
rial,sans-serif;font-size:14px"><br></div><div style=3D"font-family:Arial,s=
ans-serif;font-size:14px">-Ali</div><div style=3D"font-family:Arial,sans-se=
rif;font-size:14px"><br></div><div style=3D"font-family:Arial,sans-serif;fo=
nt-size:14px">---</div><div style=3D"font-family:Arial,sans-serif;font-size=
:14px"><br></div><div style=3D"font-family:Arial,sans-serif;font-size:14px"=
>[1]:=C2=A0<span><a rel=3D"noreferrer nofollow noopener noreferrer" href=3D=
"https://www.coindesk.com/consensus-magazine/2023/05/05/pump-the-brcs-the-p=
romise-and-peril-of-bitcoin-backed-tokens/?outputType=3Damp" target=3D"_bla=
nk">https://www.coindesk.com/consensus-magazine/2023/05/05/pump-the-brcs-th=
e-promise-and-peril-of-bitcoin-backed-tokens/</a></span></div><div style=3D=
"font-family:Arial,sans-serif;font-size:14px"><div>
    </div>
   =20
            <div>
       =20
            </div>
</div>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank" =
rel=3D"noreferrer">bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer noreferrer" target=3D"_blank">https://lists.linuxfoundati=
on.org/mailman/listinfo/bitcoin-dev</a><br>
</blockquote></div>

--000000000000a29aaf05fb2e3259--