path: root/4b/b29dfaed8e530f95b6547dfa443eb144e43c7b

Return-Path: <aymeric@peersm.com>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 77AFAC0032
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Thu, 27 Jul 2023 13:06:44 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp2.osuosl.org (Postfix) with ESMTP id 52B8B4018F
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Thu, 27 Jul 2023 13:06:44 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 52B8B4018F
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001,
 RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001]
 autolearn=ham autolearn_force=no
Received: from smtp2.osuosl.org ([127.0.0.1])
 by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id RurnQt_LNGxX
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Thu, 27 Jul 2023 13:06:42 +0000 (UTC)
X-Greylist: delayed 8731 seconds by postgrey-1.37 at util1.osuosl.org;
 Thu, 27 Jul 2023 13:06:42 UTC
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 6091D400D0
Received: from 2.mo548.mail-out.ovh.net (2.mo548.mail-out.ovh.net
 [178.33.255.19])
 by smtp2.osuosl.org (Postfix) with ESMTPS id 6091D400D0
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Thu, 27 Jul 2023 13:06:42 +0000 (UTC)
Received: from mxplan6.mail.ovh.net (unknown [10.109.143.25])
 by mo548.mail-out.ovh.net (Postfix) with ESMTPS id 419AF21B72;
 Thu, 27 Jul 2023 10:41:08 +0000 (UTC)
Received: from peersm.com (37.59.142.109) by DAG6EX2.mxp6.local (172.16.2.52)
 with Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.27; Thu, 27 Jul
 2023 12:41:07 +0200
Authentication-Results: garm.ovh; auth=pass
 (GARM-109S003dc5f1f5d-c9ba-45c1-8333-c2da47b11898,
 62DEFCF61F8FED0F11D287297961668B007FB0AA) smtp.auth=aymeric@peersm.com
X-OVh-ClientIp: 92.184.107.155
Content-Type: multipart/alternative;
 boundary="Apple-Mail-A63D5894-EB08-4DAF-8545-C6A872C9E7B8"
Content-Transfer-Encoding: 7bit
From: "aymeric@peersm.com" <aymeric@peersm.com>
MIME-Version: 1.0 (1.0)
Date: Thu, 27 Jul 2023 12:41:06 +0200
Message-ID: <55D64031-B210-4971-B353-E31A68268A58@peersm.com>
References: <A2F4432A-FFFA-4CAF-97A2-59EF4FFBD674@orangepill.ovh>
In-Reply-To: <A2F4432A-FFFA-4CAF-97A2-59EF4FFBD674@orangepill.ovh>
To: <leohaf@orangepill.ovh>, Bitcoin Protocol Discussion
 <bitcoin-dev@lists.linuxfoundation.org>
X-Mailer: iPhone Mail (17H35)
X-Originating-IP: [37.59.142.109]
X-ClientProxiedBy: DAG4EX1.mxp6.local (172.16.2.31) To DAG6EX2.mxp6.local
 (172.16.2.52)
X-Ovh-Tracer-GUID: ca672bd9-699f-4a7d-96ab-2ad575fc9645
X-Ovh-Tracer-Id: 5315373463679493018
X-VR-SPAMSTATE: OK
X-VR-SPAMSCORE: 0
X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedviedrieeggddthecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfqggfjpdevjffgvefmvefgnecuuegrihhlohhuthemucehtddtnecunecujfgurheptgfghfggufffkfhfjgfvofhisegrjehmrehhtdejnecuhfhrohhmpedfrgihmhgvrhhitgesphgvvghrshhmrdgtohhmfdcuoegrhihmvghrihgtsehpvggvrhhsmhdrtghomheqnecuggftrfgrthhtvghrnhepteeigfeftdehudegudevgfethfdtuddtleeiveeggeegheeugeefjeejhfefhfdunecuffhomhgrihhnpehlihhnuhigfhhouhhnuggrthhiohhnrdhorhhgnecukfhppeduvdejrddtrddtrddupdefjedrheelrddugedvrddutdelpdelvddrudekgedruddtjedrudehheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepihhnvghtpeduvdejrddtrddtrddupdhmrghilhhfrhhomhepoegrhihmvghrihgtsehpvggvrhhsmhdrtghomheqpdhnsggprhgtphhtthhopedupdhrtghpthhtoheplhgvohhhrghfsehorhgrnhhgvghpihhllhdrohhvhhdpsghithgtohhinhdquggvvheslhhishhtshdrlhhinhhugihfohhunhgurghtihhonhdrohhrghdpoffvtefjohhsthepmhhoheegkedpmhhouggvpehsmhhtphhouhht
X-Mailman-Approved-At: Sun, 30 Jul 2023 18:04:24 +0000
Subject: Re: [bitcoin-dev] [SPAM]  Concern about "Inscriptions".
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: Thu, 27 Jul 2023 13:06:44 -0000

--Apple-Mail-A63D5894-EB08-4DAF-8545-C6A872C9E7B8
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

See #28130 on bitcoin repo

Of course the intent is not to store "inscriptions" but a reference

Whatever you do bitcoin cannot avoid deviant practices

Therefore that one is the right way to go

Envoy=C3=A9 de mon iPhone

> Le 25 juil. 2023 =C3=A0 23:19, L=C3=A9o via bitcoin-dev <bitcoin-dev@lists=
.linuxfoun@lists.linuxfoundation.org> a =C3=A9crit :
>=20
> =EF=BB=BF
> Hello,
>=20
> I am writing to you today because I am concerned about a significant bug t=
hat seems to be overlooked in recent versions of the software. The bug in qu=
estion concerns the "inscriptions" developed by @rodarmor, and it worries me=
 because, in just a few months, they have already reached a size of 11.8GB o=
n the blockchain, causing issues with the UTXO set, which appears to be grow=
ing by about 25MB per day.
>=20
> I understand that there may be discussions about the nature of these inscr=
iptions, but personally, I find it hard not to consider them as spam. Their r=
ecurring nature and their impact on the size of the UTXO set and the blockch=
ain itself seem concerning, and I would like to understand why this problem h=
as not been addressed more seriously.
>=20
> I would also like to point out that there are options in Bitcoin Core to c=
hoose the mempool policy, such as datacarrier or permitbaremultisig. However=
, when it comes to inscriptions, there are no available options except for a=
 patch produced by Luke Dashjr. Unfortunately, this patch is unusable for mo=
st people as it requires compiling Bitcoin Core.
>=20
> So, I wonder why there are no options to reject inscriptions in the mempoo=
l of a node. Such a feature could give users the ability to customize their a=
pproach in managing these particular cases and help mitigate the negative im=
pact of inscriptions on the network.
>=20
> In addition to the technical issues, I also find that this situation raise=
s ethical questions. Inscriptions are primarily used to sell NFTs or Tokens,=
 concepts that the Bitcoin community has consistently rejected.
>=20
> Therefore, I kindly request you, as Bitcoin developers, to take this conce=
rn into consideration and seriously consider implementing a feature that wou=
ld allow users to reject inscriptions in the mempool. Such a measure would c=
ontribute to protecting the integrity of the network.
>=20
> Thank you sincerely for your attention to this matter.
>=20
> L=C3=A9o.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

--Apple-Mail-A63D5894-EB08-4DAF-8545-C6A872C9E7B8
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto">See #28130 on bitcoin repo<div><br></div><d=
iv>Of course the intent is not to store "inscriptions" but a reference</div>=
<div><br></div><div>Whatever you do bitcoin cannot avoid deviant practices</=
div><div><br></div><div>Therefore that one is the right way to go<br><br><di=
v dir=3D"ltr">Envoy=C3=A9 de mon iPhone</div><div dir=3D"ltr"><br><blockquot=
e type=3D"cite">Le 25 juil. 2023 =C3=A0 23:19, L=C3=A9o via bitcoin-dev &lt;=
bitcoin-dev@lists.linuxfoun@lists.linuxfoundation.org&gt; a =C3=A9crit&nbsp;=
:<br><br></blockquote></div><blockquote type=3D"cite"><div dir=3D"ltr">=EF=BB=
=BF
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8"><di=
v style=3D"overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: a=
fter-white-space;"><div style=3D"margin: 0px; font-style: normal; font-varia=
nt-caps: normal; font-stretch: normal; font-size: 11px; line-height: normal;=
 font-family: &quot;Helvetica Neue&quot;; font-size-adjust: none; font-kerni=
ng: auto; font-variant-alternates: normal; font-variant-ligatures: normal; f=
ont-variant-numeric: normal; font-variant-east-asian: normal; font-variant-p=
osition: normal; font-feature-settings: normal; font-optical-sizing: auto; f=
ont-variation-settings: normal;">Hello,</div><div style=3D"margin: 0px; font=
-style: normal; font-variant-caps: normal; font-stretch: normal; font-size: 1=
1px; line-height: normal; font-family: &quot;Helvetica Neue&quot;; font-size=
-adjust: none; font-kerning: auto; font-variant-alternates: normal; font-var=
iant-ligatures: normal; font-variant-numeric: normal; font-variant-east-asia=
n: normal; font-variant-position: normal; font-feature-settings: normal; fon=
t-optical-sizing: auto; font-variation-settings: normal; background-color: r=
gb(255, 255, 255); min-height: 12px;"><br></div><div style=3D"margin: 0px; f=
ont-style: normal; font-variant-caps: normal; font-stretch: normal; font-siz=
e: 11px; line-height: normal; font-family: &quot;Helvetica Neue&quot;; font-=
size-adjust: none; font-kerning: auto; font-variant-alternates: normal; font=
-variant-ligatures: normal; font-variant-numeric: normal; font-variant-east-=
asian: normal; font-variant-position: normal; font-feature-settings: normal;=
 font-optical-sizing: auto; font-variation-settings: normal;">I am writing t=
o you today because I am concerned about a significant bug that seems to be o=
verlooked in recent versions of the software. The bug in question concerns t=
he "inscriptions" developed by @rodarmor, and it worries me because, in just=
 a few months, they have already reached a size of 11.8GB on the blockchain,=
 causing issues with the UTXO set, which appears to be growing by about 25MB=
 per day.</div><div style=3D"margin: 0px; font-style: normal; font-variant-c=
aps: normal; font-stretch: normal; font-size: 11px; line-height: normal; fon=
t-family: &quot;Helvetica Neue&quot;; font-size-adjust: none; font-kerning: a=
uto; font-variant-alternates: normal; font-variant-ligatures: normal; font-v=
ariant-numeric: normal; font-variant-east-asian: normal; font-variant-positi=
on: normal; font-feature-settings: normal; font-optical-sizing: auto; font-v=
ariation-settings: normal; background-color: rgb(255, 255, 255); min-height:=
 12px;"><br></div><div style=3D"margin: 0px; font-style: normal; font-varian=
t-caps: normal; font-stretch: normal; font-size: 11px; line-height: normal; f=
ont-family: &quot;Helvetica Neue&quot;; font-size-adjust: none; font-kerning=
: auto; font-variant-alternates: normal; font-variant-ligatures: normal; fon=
t-variant-numeric: normal; font-variant-east-asian: normal; font-variant-pos=
ition: normal; font-feature-settings: normal; font-optical-sizing: auto; fon=
t-variation-settings: normal;">I understand that there may be discussions ab=
out the nature of these inscriptions, but personally, I find it hard not to c=
onsider them as spam. Their recurring nature and their impact on the size of=
 the UTXO set and the blockchain itself seem concerning, and I would like to=
 understand why this problem has not been addressed more seriously.</div><di=
v style=3D"margin: 0px; font-style: normal; font-variant-caps: normal; font-=
stretch: normal; font-size: 11px; line-height: normal; font-family: &quot;He=
lvetica Neue&quot;; font-size-adjust: none; font-kerning: auto; font-variant=
-alternates: normal; font-variant-ligatures: normal; font-variant-numeric: n=
ormal; font-variant-east-asian: normal; font-variant-position: normal; font-=
feature-settings: normal; font-optical-sizing: auto; font-variation-settings=
: normal; background-color: rgb(255, 255, 255); min-height: 12px;"><br></div=
><div style=3D"margin: 0px; font-style: normal; font-variant-caps: normal; f=
ont-stretch: normal; font-size: 11px; line-height: normal; font-family: &quo=
t;Helvetica Neue&quot;; font-size-adjust: none; font-kerning: auto; font-var=
iant-alternates: normal; font-variant-ligatures: normal; font-variant-numeri=
c: normal; font-variant-east-asian: normal; font-variant-position: normal; f=
ont-feature-settings: normal; font-optical-sizing: auto; font-variation-sett=
ings: normal;">I would also like to point out that there are options in Bitc=
oin Core to choose the mempool policy, such as datacarrier or permitbaremult=
isig. However, when it comes to inscriptions, there are no available options=
 except for a patch produced by Luke Dashjr. Unfortunately, this patch is un=
usable for most people as it requires compiling Bitcoin Core.</div><div styl=
e=3D"margin: 0px; font-style: normal; font-variant-caps: normal; font-stretc=
h: normal; font-size: 11px; line-height: normal; font-family: &quot;Helvetic=
a Neue&quot;; font-size-adjust: none; font-kerning: auto; font-variant-alter=
nates: normal; font-variant-ligatures: normal; font-variant-numeric: normal;=
 font-variant-east-asian: normal; font-variant-position: normal; font-featur=
e-settings: normal; font-optical-sizing: auto; font-variation-settings: norm=
al; background-color: rgb(255, 255, 255); min-height: 12px;"><br></div><div s=
tyle=3D"margin: 0px; font-style: normal; font-variant-caps: normal; font-str=
etch: normal; font-size: 11px; line-height: normal; font-family: &quot;Helve=
tica Neue&quot;; font-size-adjust: none; font-kerning: auto; font-variant-al=
ternates: normal; font-variant-ligatures: normal; font-variant-numeric: norm=
al; font-variant-east-asian: normal; font-variant-position: normal; font-fea=
ture-settings: normal; font-optical-sizing: auto; font-variation-settings: n=
ormal;">So, I wonder why there are no options to reject inscriptions in the m=
empool of a node. Such a feature could give users the ability to customize t=
heir approach in managing these particular cases and help mitigate the negat=
ive impact of inscriptions on the network.</div><div style=3D"margin: 0px; f=
ont-style: normal; font-variant-caps: normal; font-stretch: normal; font-siz=
e: 11px; line-height: normal; font-family: &quot;Helvetica Neue&quot;; font-=
size-adjust: none; font-kerning: auto; font-variant-alternates: normal; font=
-variant-ligatures: normal; font-variant-numeric: normal; font-variant-east-=
asian: normal; font-variant-position: normal; font-feature-settings: normal;=
 font-optical-sizing: auto; font-variation-settings: normal; background-colo=
r: rgb(255, 255, 255); min-height: 12px;"><br></div><div style=3D"margin: 0p=
x; font-style: normal; font-variant-caps: normal; font-stretch: normal; font=
-size: 11px; line-height: normal; font-family: &quot;Helvetica Neue&quot;; f=
ont-size-adjust: none; font-kerning: auto; font-variant-alternates: normal; f=
ont-variant-ligatures: normal; font-variant-numeric: normal; font-variant-ea=
st-asian: normal; font-variant-position: normal; font-feature-settings: norm=
al; font-optical-sizing: auto; font-variation-settings: normal;">In addition=
 to the technical issues, I also find that this situation raises ethical que=
stions. Inscriptions are primarily used to sell NFTs or Tokens, concepts tha=
t the Bitcoin community has consistently rejected.</div><div style=3D"margin=
: 0px; font-style: normal; font-variant-caps: normal; font-stretch: normal; f=
ont-size: 11px; line-height: normal; font-family: &quot;Helvetica Neue&quot;=
; font-size-adjust: none; font-kerning: auto; font-variant-alternates: norma=
l; font-variant-ligatures: normal; font-variant-numeric: normal; font-varian=
t-east-asian: normal; font-variant-position: normal; font-feature-settings: n=
ormal; font-optical-sizing: auto; font-variation-settings: normal; backgroun=
d-color: rgb(255, 255, 255); min-height: 12px;"><br></div><div style=3D"marg=
in: 0px; font-style: normal; font-variant-caps: normal; font-stretch: normal=
; font-size: 11px; line-height: normal; font-family: &quot;Helvetica Neue&qu=
ot;; font-size-adjust: none; font-kerning: auto; font-variant-alternates: no=
rmal; font-variant-ligatures: normal; font-variant-numeric: normal; font-var=
iant-east-asian: normal; font-variant-position: normal; font-feature-setting=
s: normal; font-optical-sizing: auto; font-variation-settings: normal;">Ther=
efore, I kindly request you, as Bitcoin developers, to take this concern int=
o consideration and seriously consider implementing a feature that would all=
ow users to reject inscriptions in the mempool. Such a measure would contrib=
ute to protecting the integrity of the network.</div><div style=3D"margin: 0=
px; font-style: normal; font-variant-caps: normal; font-stretch: normal; fon=
t-size: 11px; line-height: normal; font-family: &quot;Helvetica Neue&quot;; f=
ont-size-adjust: none; font-kerning: auto; font-variant-alternates: normal; f=
ont-variant-ligatures: normal; font-variant-numeric: normal; font-variant-ea=
st-asian: normal; font-variant-position: normal; font-feature-settings: norm=
al; font-optical-sizing: auto; font-variation-settings: normal; background-c=
olor: rgb(255, 255, 255); min-height: 12px;"><br></div><div style=3D"margin:=
 0px; font-style: normal; font-variant-caps: normal; font-stretch: normal; f=
ont-size: 11px; line-height: normal; font-family: &quot;Helvetica Neue&quot;=
; font-size-adjust: none; font-kerning: auto; font-variant-alternates: norma=
l; font-variant-ligatures: normal; font-variant-numeric: normal; font-varian=
t-east-asian: normal; font-variant-position: normal; font-feature-settings: n=
ormal; font-optical-sizing: auto; font-variation-settings: normal;">Thank yo=
u sincerely for your attention to this matter.</div><div style=3D"margin: 0p=
x; font-style: normal; font-variant-caps: normal; font-stretch: normal; font=
-size: 11px; line-height: normal; font-family: &quot;Helvetica Neue&quot;; f=
ont-size-adjust: none; font-kerning: auto; font-variant-alternates: normal; f=
ont-variant-ligatures: normal; font-variant-numeric: normal; font-variant-ea=
st-asian: normal; font-variant-position: normal; font-feature-settings: norm=
al; font-optical-sizing: auto; font-variation-settings: normal; background-c=
olor: rgb(255, 255, 255); min-height: 12px;"><br></div><div style=3D"margin:=
 0px; font-style: normal; font-variant-caps: normal; font-stretch: normal; f=
ont-size: 11px; line-height: normal; font-family: &quot;Helvetica Neue&quot;=
; font-size-adjust: none; font-kerning: auto; font-variant-alternates: norma=
l; font-variant-ligatures: normal; font-variant-numeric: normal; font-varian=
t-east-asian: normal; font-variant-position: normal; font-feature-settings: n=
ormal; font-optical-sizing: auto; font-variation-settings: normal;">L=C3=A9o=
.</div></div><span>_______________________________________________</span><br=
><span>bitcoin-dev mailing list</span><br><span>bitcoin-dev@lists.linuxfound=
ation.org</span><br><span>https://lists.linuxfoundation.org/mailman/listinfo=
/bitcoin-dev</span><br></div></blockquote></div></body></html>=

--Apple-Mail-A63D5894-EB08-4DAF-8545-C6A872C9E7B8--