path: root/b0/d76982dbf9f25154f47f59cbbbd662543df6e1

Return-Path: <ashneverdawn@gmail.com>
Received: from smtp4.osuosl.org (smtp4.osuosl.org [IPv6:2605:bc80:3010::137])
 by lists.linuxfoundation.org (Postfix) with ESMTP id D612AC0032
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 31 Jul 2023 04:12:25 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp4.osuosl.org (Postfix) with ESMTP id A9128409A6
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 31 Jul 2023 04:12:25 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org A9128409A6
Authentication-Results: smtp4.osuosl.org;
 dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com
 header.a=rsa-sha256 header.s=20221208 header.b=LemwDbbb
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: 0.911
X-Spam-Level: 
X-Spam-Status: No, score=0.911 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_FROM=0.001,
 FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, PDS_OTHER_BAD_TLD=1.999,
 RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001,
 T_MIME_MALF=0.01] autolearn=no 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 DGD-NS7Xxkwo
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 31 Jul 2023 04:12:23 +0000 (UTC)
Received: from mail-pg1-x531.google.com (mail-pg1-x531.google.com
 [IPv6:2607:f8b0:4864:20::531])
 by smtp4.osuosl.org (Postfix) with ESMTPS id 5F96240973
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 31 Jul 2023 04:12:23 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 5F96240973
Received: by mail-pg1-x531.google.com with SMTP id
 41be03b00d2f7-55fcc15e109so2338378a12.3
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 30 Jul 2023 21:12:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=gmail.com; s=20221208; t=1690776742; x=1691381542;
 h=to:subject:message-id:date:from:in-reply-to:references:mime-version
 :from:to:cc:subject:date:message-id:reply-to;
 bh=zvAtBo1LpYmQLDLVE74zNGVbOiEDFKdkMdty3dOlUPo=;
 b=LemwDbbbBRu2ppRvpe+9PViIjoELy37JYxHnJOadYTijT5BFPrHyPOcHneAiQZy0rt
 8CDyFXIvgc5CMPCktfx5SCdTAHfznj78I2NCCzYG+sVfdfxT6uPo84VYcFMfPRI7UtF3
 Qu3/jVB/uZgUed9qBTUVJ0c4nfagn3K8eOHRcza+qiwOeRwewVEGMhZ6wertFQn4i9SL
 jKPLcP2Nk6aGonX2bd1TgIFIztYuhNpXeE/40C4VVZGOrepZ9bKpfvjKrE1pO9IavAA/
 P+Px9rFiVUY+0/nstedtbR8DTilS7R8qpMWWpsRcLaIloBKzrOfpkFtvtWKCIYS2ophU
 qKtw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20221208; t=1690776742; x=1691381542;
 h=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=zvAtBo1LpYmQLDLVE74zNGVbOiEDFKdkMdty3dOlUPo=;
 b=I9Mr2/B70MUfk6Rm1G26oKjV+fn4ZPB4Z6GQjqRExowVnIv2R+V9R+Z526ZU18uOjC
 nn010oFIWzfxKvFSb86r17ZE96MW0DT2iTNZ68VTeM3Ql3Rus2u2TwI1qjGAVgLzxoSe
 Nfy4O1Om6byUwg/zQPJv2hFOsn6bnuTrg8JqPDz0lqTwQQsSJZQtMEhWzcDUZAD0HbwM
 pAeUtJpoTNDda8LffYaUCJ8I8SR3/yNz8K4A9v/WR/f4xrtp+tQA0xkdorSBB17PxwdY
 wLFYHufI1r7+wbv1XLD9RQZrXfpjWBz3Z3cyzIofV34XGkRUDGgAkBFfkkBS2WZDYq9p
 sF7g==
X-Gm-Message-State: ABy/qLbN0GzsoZClju0P5/MOBN6YgLRjf/kgshgkEk/GPyGcpHPqn9x2
 N0ITF5WfyaIAft1HttYp67fV4jAms5q94U4ln5y0Q8Yt8tk=
X-Google-Smtp-Source: APBJJlElRGL+fKb6h/VKSOlAQfaD/Z/EEhdauF9hOpRSsnfkPkohaDHpFiHrOMtZtM70mzX4BP035bvRi/zj5i9y6Pw=
X-Received: by 2002:a17:90a:bd88:b0:268:1e95:4e25 with SMTP id
 z8-20020a17090abd8800b002681e954e25mr8449088pjr.17.1690776742146; Sun, 30 Jul
 2023 21:12:22 -0700 (PDT)
MIME-Version: 1.0
References: <mailman.126799.1690753843.956.bitcoin-dev@lists.linuxfoundation.org>
In-Reply-To: <mailman.126799.1690753843.956.bitcoin-dev@lists.linuxfoundation.org>
From: Hugo L <ashneverdawn@gmail.com>
Date: Mon, 31 Jul 2023 00:12:10 -0400
Message-ID: <CAGaGvmNkLS9OuMOcfLb9TTOFvwwY0GW=UYsYyx6y5Rt5Phni1g@mail.gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary="0000000000001c36c40601c0a382"
X-Mailman-Approved-At: Mon, 31 Jul 2023 11:55:13 +0000
Subject: Re: [bitcoin-dev] Concern about "Inscriptions". (ashneverdawn)
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: Mon, 31 Jul 2023 04:12:25 -0000

--0000000000001c36c40601c0a382
Content-Type: text/plain; charset="UTF-8"

I don't think it's anyone's place to judge which types of transactions
should be allowed or not on the network, in fact, when it comes to privacy
and censorship resistance, it would be better if we were not even able to
distinguish different types of transactions from one another in the first
place.

We have limited resources on the blockchain and so they should go to the
highest bidder. This is already how the network functions and how it
ensures it's security.

Rather than thinking about this as "spam", I think it's useful to
objectively think about it in terms of value to the marketplace (fees
they're willing to pay) against cost to the network (storage consumed). It
comes down to supply and demand.

If the rate of growth of the blockchain is too high, Ordinals aren't the
cause, it's rather that the theoretical limit of the amount of storage that
can be added per block isn't sufficiently limited. (Whether they are used
to produce Ordinals or something else)



On Sun, Jul 30, 2023, 5:51 PM , <
bitcoin-dev-request@lists.linuxfoundation.org> wrote:

> Send bitcoin-dev mailing list submissions to
>         bitcoin-dev@lists.linuxfoundation.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> or, via email, send a message with subject or body 'help' to
>         bitcoin-dev-request@lists.linuxfoundation.org
>
> You can reach the person managing the list at
>         bitcoin-dev-owner@lists.linuxfoundation.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of bitcoin-dev digest..."
>
>
> Today's Topics:
>
>    1. Re: Concern about "Inscriptions". (rot13maxi)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 30 Jul 2023 18:34:12 +0000
> From: rot13maxi <rot13maxi@protonmail.com>
> To: L?o Haf <leohaf@orangepill.ovh>, "vjudeu@gazeta.pl"
>         <vjudeu@gazeta.pl>
> Cc: Bitcoin Protocol Discussion
>         <bitcoin-dev@lists.linuxfoundation.org>
> Subject: Re: [bitcoin-dev] Concern about "Inscriptions".
> Message-ID:
>
> <RIqguuebFmAhEDqCY_0T8KRqHBXEfcvPw6-MbDIyWsAWpLenFFeOVx88-068QFZr7xowg-6Zg988HsRCKdswtZC6QUKPXnrTyTAc_l5jphg=@
> protonmail.com>
>
> Content-Type: text/plain; charset="utf-8"
>
> Hello,
>
> > This cat and mouse game can be won by bitcoin defenders. Why ? Because
> it is easier to detect these transactions and make them a standardization
> rule than to create new types of spam transactions.
>
> One of the things discussed during the mempoolfullrbf discussion is that a
> small (~10%) of nodes willing to relay a class of transaction is enough for
> that class of transaction to consistently reach miners. That means you
> would need to get nearly the entire network to run updated relay policy to
> prevent inscriptions from trivially reaching miners and being included in
> blocks. Inscription users have shown that they are willing and able to send
> non-standard transactions to miners out of band (
> https://mempool.space/tx/0301e0480b374b32851a9462db29dc19fe830a7f7d7a88b81612b9d42099c0ae),
> so even if you managed to get enough of the network running the new rule to
> prevent propagation to miners, those users can just go out of band. Or,
> they can simply change the script that is used to embed an inscription in
> the transaction witness. For example, instead of 0 OP_IF?, maybe they do 0
> OP_DUP OP_DROP OP_IF. When the anti-inscription people detect this, they
> have to update the rule and wait for 90%
>  + of the network to upgrade. When the pro-inscription people see this,
> they only have to convince other inscription enthusiasts and businesses to
> update.
>
> The anti-inscription patch has to be run by many more participants (most
> of whom don?t care), while the pro-inscription update has to be run by a
> small number of people who care a lot. It?s a losing battle for the
> anti-inscription people.
>
> If you want to prevent inscriptions, the best answer we know of today is
> economic: the cost of the blockspace needs to be more expensive than
> inscribers are willing to pay, either because its too expensive or because
> there?s no market demand for inscriptions. The former relies on Bitcoin
> becoming more useful to more people, the latter is the natural course of
> collectibles.
>
> > Finally, I would like to quote satoshi himself who wrote about spam here
> is the link: https://bitcointalk.org/index.php?topic=195.msg1617#msg1617
>
> Appeals to Satoshi are not compelling arguments.
>
> Cheers,
> Rijndael
>
> On Sun, Jul 30, 2023 at 2:04 PM, L?o Haf via bitcoin-dev <[
> bitcoin-dev@lists.linuxfoundation.org](mailto:On Sun, Jul 30, 2023 at
> 2:04 PM, L?o Haf via bitcoin-dev <<a href=)> wrote:
>
> > ?According to you, the rules of standardization are useless but in this
> case why were they introduced? The opreturn limit can be circumvented by
> miners, yet it is rare to see any, the same for maxancestorcount,
> minrelayfee or even the dust limit.
> >
> > This cat and mouse game can be won by bitcoin defenders. Why ? Because
> it is easier to detect these transactions and make them a standardization
> rule than to create new types of spam transactions.
> >
> > As for the default policy, it can be a weakness but also a strength
> because if the patch is integrated into Bitcoin Core by being activated by
> default, the patch will become more and more effective as the nodes update.
> >
> > Also, when it came to using a pre-segwit node, it is not a solution
> because this type of node cannot initiate new ones, which is obviously a
> big problem.
> >
> > Finally, I would like to quote satoshi himself who wrote about spam here
> is the link: https://bitcointalk.org/index.php?topic=195.msg1617#msg1617
> >
> >> Le 27 juil. 2023 ? 07:10, vjudeu@gazeta.pl a ?crit :
> >
> >>
> >
> >> ?
> >
> >>> not taking action against these inscription could be interpreted by
> spammers as tacit acceptance of their practice.
> >
> >>
> >
> >> Note that some people, even on this mailing list, do not consider
> Ordinals as spam:
> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2023-February/021464.html
> >
> >>
> >
> >> See? It was discussed when it started. Some people believe that
> blocking Ordinals is censorship, and could lead to blocking regular
> transactions in the future, just based on other criteria. That means, even
> if developers would create some official version with that option, then
> some people would not follow them, or even block Ordinals-filtering nodes,
> exactly as described in the linked thread:
> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2023-February/021487.html
> >
> >>
> >
> >>> as spammers might perceive that the Bitcoin network tolerates this
> kind of behavior
> >
> >>
> >
> >> But it is true, you have the whole pages, where you can find images,
> files, or other data, that was pushed on-chain long before Ordinals. The
> whole whitepaper was uploaded just on 1-of-3 multisig outputs, see
> transaction
> 54e48e5f5c656b26c3bca14a8c95aa583d07ebe84dde3b7dd4a78f4e4186e713. You have
> the whole altcoins that are connected to Bitcoin by using part of the
> Bitcoin's UTXO set as their database.
> >
> >>
> >
> >> That means, as long as you won't solve IBD problem and UTXO set growing
> problem, you will go nowhere, because if you block Ordinals specifically,
> people won't learn "this is bad, don't do that", they could read it as "use
> the old way instead", as long as you won't block all possible ways. And
> doing that, requires for example creating new nodes, without synchronizing
> non-consensus data, like it could be done in "assume UTXO" model.
> >
> >>
> >
> >> Also note that as long as people use Taproot to upload a lot of data,
> you can still turn off the witness, and become a pre-Segwit node. But if
> you block those ways, then people will push data into legacy parts, and
> then you will need more code to strip it correctly. The block 774628 maybe
> contains almost 4 MB of data from the perspective of Segwit node, but the
> legacy part is actually very small, so by turning witness off, you can
> strip it to maybe just a few kilobytes.
> >
> >>
> >
> >>> I want to emphasize that my proposal does not involve implementing a
> soft fork in any way. On the contrary, what I am asking is simply to
> consider adding a standardization option. This option would allow the
> community to freely decide whether it should be activated or not.
> >
> >>
> >
> >> 1. Without a soft-fork, those data will be pushed by mining pools
> anyway, as it happened in the block 774628.
> >
> >> 2. Adding some settings won't help, as most people use the default
> configuration. For example, people can configure their nodes to allow free
> transactions, without recompiling anything. The same with disabling dust
> amounts. But good luck finding a node in the wild that does anything
> unusual.
> >
> >> 3. This patch produced by Luke Dashjr does not address all cases. You
> could use "OP_TRUE OP_NOTIF" instead of "OP_FALSE OP_IF" used by Ordinals,
> and easily bypass those restrictions. This will be just a cat and mouse
> game, where spammers will even use P2PK, if they will be forced to. The
> Pandora's box is already opened, that fix could be good for February or
> March, but not now.
> >
> >>
> >
> >>
> >
> >>
> >
> >>> On 2023-07-26 11:47:09 user leohaf@orangepill.ovh wrote:
> >
> >>> I understand your point of view. However, inscription represent by far
> the largest spam attack due to their ability to embed themselves in the
> witness with a fee reduction.
> >
> >>
> >
> >> Unlike other methods, such as using the op_return field which could
> also be used to spam the chain, the associated fees and the standardization
> rule limiting op_return to 80 bytes have so far prevented similar abuses.
> >
> >>
> >
> >> Although attempting to stop inscription could lead to more serious
> issues, not taking action against these inscription could be interpreted by
> spammers as tacit acceptance of their practice. This could encourage more
> similar spam attacks in the future, as spammers might perceive that the
> Bitcoin network tolerates this kind of behavior.
> >
> >>
> >
> >> I want to emphasize that my proposal does not involve implementing a
> soft fork in any way. On the contrary, what I am asking is simply to
> consider adding a standardization option. This option would allow the
> community to freely decide whether it should be activated or not.
> >
> >>
> >
> >>
> >
> >>>> Le 26 juil. 2023 ? 07:30, vjudeu@gazeta.pl a ?crit :
> >
> >>>> and I would like to understand why this problem has not been
> addressed more seriously
> >
> >>> Because if nobody has any good solution, then status quo is preserved.
> If tomorrow ECDSA would be broken, the default state of the network would
> be "just do nothing", and every solution would be backward-compatible with
> that approach. Burn old coins, and people will call it "Tether",
> redistribute them, and people will call it "BSV". Leave everything
> untouched, and the network will split into N parts, and then you pick the
> strongest chain to decide, what should be done.
> >
> >>>> However, when it comes to inscriptions, there are no available
> options except for a patch produced by Luke Dashjr.
> >
> >>> Because the real solution should address some different problem, that
> was always there, and nobody knows, how to deal with it: the problem of
> forever-growing initial blockchain download time, and forever-growing UTXO
> set. Some changes with "assume UTXO" are trying to address just that, but
> this code is not yet completed.
> >
> >>>> So, I wonder why there are no options to reject inscriptions in the
> mempool of a node.
> >
> >>> Because it will lead you to never ending chase. You will block one
> inscriptions, and different ones will be created. Now, they are present
> even on chains, where there is no Taproot, or even Segwit. That means, if
> you try to kill them, then they will be replaced by N regular
> indistinguishable transactions, and then you will go back to those more
> serious problems under the hood: IBD time, and UTXO size.
> >
> >>>> Inscriptions are primarily used to sell NFTs or Tokens, concepts that
> the Bitcoin community has consistently rejected.
> >
> >>> The community also rejected things like sidechains, and they are still
> present, just in a more centralized form. There are some unstoppable
> concepts, for example soft-forks. You cannot stop a soft-fork. What
> inscription creators did, is just non-enforced soft-fork. They believe
> their rules are followed to the letter, but this is not the case, as you
> can create a valid Bitcoin transaction, that will be some invalid Ordinals
> transaction (because their additional rules are not enforced by miners and
> nodes).
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20230730/dfc353d3/attachment.html
> >
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
> ------------------------------
>
> End of bitcoin-dev Digest, Vol 98, Issue 20
> *******************************************
>

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

<div dir=3D"auto"><div dir=3D"auto">I don&#39;t think it&#39;s anyone&#39;s=
 place to judge which types of transactions should be allowed or not on the=
 network, in fact, when it comes to privacy and censorship resistance, it w=
ould be better if we were not even able to distinguish different types of t=
ransactions from one another in the first place.<br></div><div dir=3D"auto"=
><br></div><div dir=3D"auto">We have limited resources on the blockchain an=
d so they should go to the highest bidder. This is already how the network =
functions and how it ensures it&#39;s security.=C2=A0<br></div><div dir=3D"=
auto"><br></div>Rather than thinking about this as &quot;spam&quot;, I thin=
k it&#39;s useful to objectively think about it in terms of value to the ma=
rketplace (fees they&#39;re willing to pay) against cost to the network (st=
orage consumed). It comes down to supply and demand.<div dir=3D"auto"><div =
dir=3D"auto"><br></div><div dir=3D"auto">If the rate of growth of the block=
chain is too high, Ordinals aren&#39;t the cause, it&#39;s rather that the =
theoretical limit of the amount of storage that can be added per block isn&=
#39;t sufficiently limited. (Whether they are used to produce Ordinals or s=
omething else)</div><div dir=3D"auto"><br></div><div dir=3D"auto"><br></div=
></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail=
_attr">On Sun, Jul 30, 2023, 5:51 PM , &lt;<a href=3D"mailto:bitcoin-dev-re=
quest@lists.linuxfoundation.org">bitcoin-dev-request@lists.linuxfoundation.=
org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send bitcoin-dev=
 mailing list submissions to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:bitcoin-dev@lists.linuxfounda=
tion.org" target=3D"_blank" rel=3D"noreferrer">bitcoin-dev@lists.linuxfound=
ation.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://lists.linuxfoundation.org/ma=
ilman/listinfo/bitcoin-dev" rel=3D"noreferrer noreferrer" target=3D"_blank"=
>https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev</a><br>
or, via email, send a message with subject or body &#39;help&#39; to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:bitcoin-dev-request@lists.lin=
uxfoundation.org" target=3D"_blank" rel=3D"noreferrer">bitcoin-dev-request@=
lists.linuxfoundation.org</a><br>
<br>
You can reach the person managing the list at<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:bitcoin-dev-owner@lists.linux=
foundation.org" target=3D"_blank" rel=3D"noreferrer">bitcoin-dev-owner@list=
s.linuxfoundation.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than &quot;Re: Contents of bitcoin-dev digest...&quot;<br>
<br>
<br>
Today&#39;s Topics:<br>
<br>
=C2=A0 =C2=A01. Re: Concern about &quot;Inscriptions&quot;. (rot13maxi)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Sun, 30 Jul 2023 18:34:12 +0000<br>
From: rot13maxi &lt;<a href=3D"mailto:rot13maxi@protonmail.com" target=3D"_=
blank" rel=3D"noreferrer">rot13maxi@protonmail.com</a>&gt;<br>
To: L?o Haf &lt;leohaf@orangepill.ovh&gt;, &quot;<a href=3D"mailto:vjudeu@g=
azeta.pl" target=3D"_blank" rel=3D"noreferrer">vjudeu@gazeta.pl</a>&quot;<b=
r>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;<a href=3D"mailto:vjudeu@gazeta.pl" target=
=3D"_blank" rel=3D"noreferrer">vjudeu@gazeta.pl</a>&gt;<br>
Cc: Bitcoin Protocol Discussion<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfo=
undation.org" target=3D"_blank" rel=3D"noreferrer">bitcoin-dev@lists.linuxf=
oundation.org</a>&gt;<br>
Subject: Re: [bitcoin-dev] Concern about &quot;Inscriptions&quot;.<br>
Message-ID:<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;RIqguuebFmAhEDqCY_0T8KRqHBXEfcvPw6-MbDIyWsA=
WpLenFFeOVx88-068QFZr7xowg-6Zg988HsRCKdswtZC6QUKPXnrTyTAc_l5jphg=3D@<a href=
=3D"http://protonmail.com" rel=3D"noreferrer noreferrer" target=3D"_blank">=
protonmail.com</a>&gt;<br>
<br>
Content-Type: text/plain; charset=3D&quot;utf-8&quot;<br>
<br>
Hello,<br>
<br>
&gt; This cat and mouse game can be won by bitcoin defenders. Why ? Because=
 it is easier to detect these transactions and make them a standardization =
rule than to create new types of spam transactions.<br>
<br>
One of the things discussed during the mempoolfullrbf discussion is that a =
small (~10%) of nodes willing to relay a class of transaction is enough for=
 that class of transaction to consistently reach miners. That means you wou=
ld need to get nearly the entire network to run updated relay policy to pre=
vent inscriptions from trivially reaching miners and being included in bloc=
ks. Inscription users have shown that they are willing and able to send non=
-standard transactions to miners out of band (<a href=3D"https://mempool.sp=
ace/tx/0301e0480b374b32851a9462db29dc19fe830a7f7d7a88b81612b9d42099c0ae" re=
l=3D"noreferrer noreferrer" target=3D"_blank">https://mempool.space/tx/0301=
e0480b374b32851a9462db29dc19fe830a7f7d7a88b81612b9d42099c0ae</a>), so even =
if you managed to get enough of the network running the new rule to prevent=
 propagation to miners, those users can just go out of band. Or, they can s=
imply change the script that is used to embed an inscription in the transac=
tion witness. For example, instead of 0 OP_IF?, maybe they do 0 OP_DUP OP_D=
ROP OP_IF. When the anti-inscription people detect this, they have to updat=
e the rule and wait for 90%<br>
=C2=A0+ of the network to upgrade. When the pro-inscription people see this=
, they only have to convince other inscription enthusiasts and businesses t=
o update.<br>
<br>
The anti-inscription patch has to be run by many more participants (most of=
 whom don?t care), while the pro-inscription update has to be run by a smal=
l number of people who care a lot. It?s a losing battle for the anti-inscri=
ption people.<br>
<br>
If you want to prevent inscriptions, the best answer we know of today is ec=
onomic: the cost of the blockspace needs to be more expensive than inscribe=
rs are willing to pay, either because its too expensive or because there?s =
no market demand for inscriptions. The former relies on Bitcoin becoming mo=
re useful to more people, the latter is the natural course of collectibles.=
<br>
<br>
&gt; Finally, I would like to quote satoshi himself who wrote about spam he=
re is the link: <a href=3D"https://bitcointalk.org/index.php?topic=3D195.ms=
g1617#msg1617" rel=3D"noreferrer noreferrer" target=3D"_blank">https://bitc=
ointalk.org/index.php?topic=3D195.msg1617#msg1617</a><br>
<br>
Appeals to Satoshi are not compelling arguments.<br>
<br>
Cheers,<br>
Rijndael<br>
<br>
On Sun, Jul 30, 2023 at 2:04 PM, L?o Haf via bitcoin-dev &lt;[<a href=3D"ma=
ilto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank" rel=3D"norefe=
rrer">bitcoin-dev@lists.linuxfoundation.org</a>](mailto:<a href=3D"mailto:O=
n" target=3D"_blank" rel=3D"noreferrer">On</a> Sun, Jul 30, 2023 at 2:04 PM=
, L?o Haf via bitcoin-dev &lt;&lt;a href=3D)&gt; wrote:<br>
<br>
&gt; ?According to you, the rules of standardization are useless but in thi=
s case why were they introduced? The opreturn limit can be circumvented by =
miners, yet it is rare to see any, the same for maxancestorcount, minrelayf=
ee or even the dust limit.<br>
&gt;<br>
&gt; This cat and mouse game can be won by bitcoin defenders. Why ? Because=
 it is easier to detect these transactions and make them a standardization =
rule than to create new types of spam transactions.<br>
&gt;<br>
&gt; As for the default policy, it can be a weakness but also a strength be=
cause if the patch is integrated into Bitcoin Core by being activated by de=
fault, the patch will become more and more effective as the nodes update.<b=
r>
&gt;<br>
&gt; Also, when it came to using a pre-segwit node, it is not a solution be=
cause this type of node cannot initiate new ones, which is obviously a big =
problem.<br>
&gt;<br>
&gt; Finally, I would like to quote satoshi himself who wrote about spam he=
re is the link: <a href=3D"https://bitcointalk.org/index.php?topic=3D195.ms=
g1617#msg1617" rel=3D"noreferrer noreferrer" target=3D"_blank">https://bitc=
ointalk.org/index.php?topic=3D195.msg1617#msg1617</a><br>
&gt;<br>
&gt;&gt; Le 27 juil. 2023 ? 07:10, <a href=3D"mailto:vjudeu@gazeta.pl" targ=
et=3D"_blank" rel=3D"noreferrer">vjudeu@gazeta.pl</a> a ?crit :<br>
&gt;<br>
&gt;&gt;<br>
&gt;<br>
&gt;&gt; ?<br>
&gt;<br>
&gt;&gt;&gt; not taking action against these inscription could be interpret=
ed by spammers as tacit acceptance of their practice.<br>
&gt;<br>
&gt;&gt;<br>
&gt;<br>
&gt;&gt; Note that some people, even on this mailing list, do not consider =
Ordinals as spam: <a href=3D"https://lists.linuxfoundation.org/pipermail/bi=
tcoin-dev/2023-February/021464.html" rel=3D"noreferrer noreferrer" target=
=3D"_blank">https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2023-Fe=
bruary/021464.html</a><br>
&gt;<br>
&gt;&gt;<br>
&gt;<br>
&gt;&gt; See? It was discussed when it started. Some people believe that bl=
ocking Ordinals is censorship, and could lead to blocking regular transacti=
ons in the future, just based on other criteria. That means, even if develo=
pers would create some official version with that option, then some people =
would not follow them, or even block Ordinals-filtering nodes, exactly as d=
escribed in the linked thread: <a href=3D"https://lists.linuxfoundation.org=
/pipermail/bitcoin-dev/2023-February/021487.html" rel=3D"noreferrer norefer=
rer" target=3D"_blank">https://lists.linuxfoundation.org/pipermail/bitcoin-=
dev/2023-February/021487.html</a><br>
&gt;<br>
&gt;&gt;<br>
&gt;<br>
&gt;&gt;&gt; as spammers might perceive that the Bitcoin network tolerates =
this kind of behavior<br>
&gt;<br>
&gt;&gt;<br>
&gt;<br>
&gt;&gt; But it is true, you have the whole pages, where you can find image=
s, files, or other data, that was pushed on-chain long before Ordinals. The=
 whole whitepaper was uploaded just on 1-of-3 multisig outputs, see transac=
tion 54e48e5f5c656b26c3bca14a8c95aa583d07ebe84dde3b7dd4a78f4e4186e713. You =
have the whole altcoins that are connected to Bitcoin by using part of the =
Bitcoin&#39;s UTXO set as their database.<br>
&gt;<br>
&gt;&gt;<br>
&gt;<br>
&gt;&gt; That means, as long as you won&#39;t solve IBD problem and UTXO se=
t growing problem, you will go nowhere, because if you block Ordinals speci=
fically, people won&#39;t learn &quot;this is bad, don&#39;t do that&quot;,=
 they could read it as &quot;use the old way instead&quot;, as long as you =
won&#39;t block all possible ways. And doing that, requires for example cre=
ating new nodes, without synchronizing non-consensus data, like it could be=
 done in &quot;assume UTXO&quot; model.<br>
&gt;<br>
&gt;&gt;<br>
&gt;<br>
&gt;&gt; Also note that as long as people use Taproot to upload a lot of da=
ta, you can still turn off the witness, and become a pre-Segwit node. But i=
f you block those ways, then people will push data into legacy parts, and t=
hen you will need more code to strip it correctly. The block 774628 maybe c=
ontains almost 4 MB of data from the perspective of Segwit node, but the le=
gacy part is actually very small, so by turning witness off, you can strip =
it to maybe just a few kilobytes.<br>
&gt;<br>
&gt;&gt;<br>
&gt;<br>
&gt;&gt;&gt; I want to emphasize that my proposal does not involve implemen=
ting a soft fork in any way. On the contrary, what I am asking is simply to=
 consider adding a standardization option. This option would allow the comm=
unity to freely decide whether it should be activated or not.<br>
&gt;<br>
&gt;&gt;<br>
&gt;<br>
&gt;&gt; 1. Without a soft-fork, those data will be pushed by mining pools =
anyway, as it happened in the block 774628.<br>
&gt;<br>
&gt;&gt; 2. Adding some settings won&#39;t help, as most people use the def=
ault configuration. For example, people can configure their nodes to allow =
free transactions, without recompiling anything. The same with disabling du=
st amounts. But good luck finding a node in the wild that does anything unu=
sual.<br>
&gt;<br>
&gt;&gt; 3. This patch produced by Luke Dashjr does not address all cases. =
You could use &quot;OP_TRUE OP_NOTIF&quot; instead of &quot;OP_FALSE OP_IF&=
quot; used by Ordinals, and easily bypass those restrictions. This will be =
just a cat and mouse game, where spammers will even use P2PK, if they will =
be forced to. The Pandora&#39;s box is already opened, that fix could be go=
od for February or March, but not now.<br>
&gt;<br>
&gt;&gt;<br>
&gt;<br>
&gt;&gt;<br>
&gt;<br>
&gt;&gt;<br>
&gt;<br>
&gt;&gt;&gt; On 2023-07-26 11:47:09 user leohaf@orangepill.ovh wrote:<br>
&gt;<br>
&gt;&gt;&gt; I understand your point of view. However, inscription represen=
t by far the largest spam attack due to their ability to embed themselves i=
n the witness with a fee reduction.<br>
&gt;<br>
&gt;&gt;<br>
&gt;<br>
&gt;&gt; Unlike other methods, such as using the op_return field which coul=
d also be used to spam the chain, the associated fees and the standardizati=
on rule limiting op_return to 80 bytes have so far prevented similar abuses=
.<br>
&gt;<br>
&gt;&gt;<br>
&gt;<br>
&gt;&gt; Although attempting to stop inscription could lead to more serious=
 issues, not taking action against these inscription could be interpreted b=
y spammers as tacit acceptance of their practice. This could encourage more=
 similar spam attacks in the future, as spammers might perceive that the Bi=
tcoin network tolerates this kind of behavior.<br>
&gt;<br>
&gt;&gt;<br>
&gt;<br>
&gt;&gt; I want to emphasize that my proposal does not involve implementing=
 a soft fork in any way. On the contrary, what I am asking is simply to con=
sider adding a standardization option. This option would allow the communit=
y to freely decide whether it should be activated or not.<br>
&gt;<br>
&gt;&gt;<br>
&gt;<br>
&gt;&gt;<br>
&gt;<br>
&gt;&gt;&gt;&gt; Le 26 juil. 2023 ? 07:30, <a href=3D"mailto:vjudeu@gazeta.=
pl" target=3D"_blank" rel=3D"noreferrer">vjudeu@gazeta.pl</a> a ?crit :<br>
&gt;<br>
&gt;&gt;&gt;&gt; and I would like to understand why this problem has not be=
en addressed more seriously<br>
&gt;<br>
&gt;&gt;&gt; Because if nobody has any good solution, then status quo is pr=
eserved. If tomorrow ECDSA would be broken, the default state of the networ=
k would be &quot;just do nothing&quot;, and every solution would be backwar=
d-compatible with that approach. Burn old coins, and people will call it &q=
uot;Tether&quot;, redistribute them, and people will call it &quot;BSV&quot=
;. Leave everything untouched, and the network will split into N parts, and=
 then you pick the strongest chain to decide, what should be done.<br>
&gt;<br>
&gt;&gt;&gt;&gt; However, when it comes to inscriptions, there are no avail=
able options except for a patch produced by Luke Dashjr.<br>
&gt;<br>
&gt;&gt;&gt; Because the real solution should address some different proble=
m, that was always there, and nobody knows, how to deal with it: the proble=
m of forever-growing initial blockchain download time, and forever-growing =
UTXO set. Some changes with &quot;assume UTXO&quot; are trying to address j=
ust that, but this code is not yet completed.<br>
&gt;<br>
&gt;&gt;&gt;&gt; So, I wonder why there are no options to reject inscriptio=
ns in the mempool of a node.<br>
&gt;<br>
&gt;&gt;&gt; Because it will lead you to never ending chase. You will block=
 one inscriptions, and different ones will be created. Now, they are presen=
t even on chains, where there is no Taproot, or even Segwit. That means, if=
 you try to kill them, then they will be replaced by N regular indistinguis=
hable transactions, and then you will go back to those more serious problem=
s under the hood: IBD time, and UTXO size.<br>
&gt;<br>
&gt;&gt;&gt;&gt; Inscriptions are primarily used to sell NFTs or Tokens, co=
ncepts that the Bitcoin community has consistently rejected.<br>
&gt;<br>
&gt;&gt;&gt; The community also rejected things like sidechains, and they a=
re still present, just in a more centralized form. There are some unstoppab=
le concepts, for example soft-forks. You cannot stop a soft-fork. What insc=
ription creators did, is just non-enforced soft-fork. They believe their ru=
les are followed to the letter, but this is not the case, as you can create=
 a valid Bitcoin transaction, that will be some invalid Ordinals transactio=
n (because their additional rules are not enforced by miners and nodes).<br=
>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: &lt;<a href=3D"http://lists.linuxfoundation.org/pipermail/bitcoin-dev/=
attachments/20230730/dfc353d3/attachment.html" rel=3D"noreferrer noreferrer=
" target=3D"_blank">http://lists.linuxfoundation.org/pipermail/bitcoin-dev/=
attachments/20230730/dfc353d3/attachment.html</a>&gt;<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<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>
<br>
<br>
------------------------------<br>
<br>
End of bitcoin-dev Digest, Vol 98, Issue 20<br>
*******************************************<br>
</blockquote></div>

--0000000000001c36c40601c0a382--