path: root/f7/c78e16a030335fff2cd00a33b81770e3bc6b3d

Return-Path: <pete@petertodd.org>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 9642CC0032
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  5 Sep 2023 17:49:50 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp2.osuosl.org (Postfix) with ESMTP id 49C5B40153
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  5 Sep 2023 17:49:50 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 49C5B40153
Authentication-Results: smtp2.osuosl.org; dkim=pass (2048-bit key,
 unprotected) header.d=messagingengine.com header.i=@messagingengine.com
 header.a=rsa-sha256 header.s=fm1 header.b=AH4XTApn
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level: 
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-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 8pB0daYbtAA7
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  5 Sep 2023 17:49:48 +0000 (UTC)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com
 [64.147.123.25])
 by smtp2.osuosl.org (Postfix) with ESMTPS id 91BA140134
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue,  5 Sep 2023 17:49:48 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 91BA140134
Received: from compute2.internal (compute2.nyi.internal [10.202.2.46])
 by mailout.west.internal (Postfix) with ESMTP id AC88A32002E8;
 Tue,  5 Sep 2023 13:49:45 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162])
 by compute2.internal (MEProxy); Tue, 05 Sep 2023 13:49:46 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
 messagingengine.com; h=cc:cc:content-type:content-type:date:date
 :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to
 :message-id:mime-version:references:reply-to:sender:subject
 :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender
 :x-sasl-enc; s=fm1; t=1693936185; x=1694022585; bh=LKJ2PjCOjk/GA
 wwMfLR0djiXvigxq+xkXskC0WD9vjw=; b=AH4XTApn4xkWiYfQ4L0iHWPcj8GLZ
 1U8cRy8d2PvjD2qncY0NdFQmGS3ag9J6SU1mQtnoXKdAM2HpscRuN/u2h6ksfYhj
 Vzp/Sie/FrXsznJtDNKDhfaf64kjVTrro5h/6aHhScY+LLtLv8dy9aOmOVTDbe+o
 qdgC92+OhbkBG/apqIuno1sHdFyhWBu1rtjwohAhdICfPVHLL4eHususBNcugadd
 fyRcrfz5rXiEFGf4SfKChp9gufZo7aNAigMYdVkPeBsEjNm2sAXjvPIA6KrilYBy
 ObiVRTov617froQGMBdJ7uaKpDQiRSrCeIsjTp0zOPt0dQm+BEX08D9sQ==
X-ME-Sender: <xms:OGr3ZPO8nwyxq16uG6N2ml9tBCPC1S_7nnkU1brvgPxg661jGJ3m-w>
 <xme:OGr3ZJ_hvxXwPj3riyGrjHmihjN0mW0Y0iGvZazBuJyVvpMI2cqF7Mg7wZooTEn-P
 LHCreRcPQ2ALXa2AD4>
X-ME-Received: <xmr:OGr3ZORCXH_qxmf8kHZbpfCGrRvy67F1AwlHldH-Z-_1bavd9d89Tc5yuQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrudehuddgleegucetufdoteggodetrfdotf
 fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen
 uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvvefukfhfgggtuggjsehgtd
 erredttddunecuhfhrohhmpefrvghtvghrucfvohguugcuoehpvghtvgesphgvthgvrhht
 ohguugdrohhrgheqnecuggftrfgrthhtvghrnhephfefudejvedvieekheelgedtgeelvd
 ehheegffdvfffffeelfefgffegieekieelnecuffhomhgrihhnpegsihhttghoihhnthgr
 lhhkrdhorhhgpdhpvghtvghrthhouggurdhorhhgnecuvehluhhsthgvrhfuihiivgeptd
 enucfrrghrrghmpehmrghilhhfrhhomhepphgvthgvsehpvghtvghrthhouggurdhorhhg
X-ME-Proxy: <xmx:OGr3ZDu_dMW3LTIMmMOSnY35EEbinnvCxQ-JJLbrTUwdM2eBAoR_Jw>
 <xmx:OGr3ZHcyLKc0rAlfyt2aaT0mxgCr--MuVNYYQsnQaP8Qw33mgaBaBA>
 <xmx:OGr3ZP0Cwxs2rogQ5VFTcKt7fhlu10-stBxWfWW6VD0UEfiCPzq5Ig>
 <xmx:OWr3ZO585LBF5PURCZkScHliVrB_2AhgYOWtK3eXywq76pU7vMYFiA>
Feedback-ID: i525146e8:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue,
 5 Sep 2023 13:49:44 -0400 (EDT)
Received: by localhost (Postfix, from userid 1000)
 id 970235F82B; Tue,  5 Sep 2023 17:49:43 +0000 (UTC)
Date: Tue, 5 Sep 2023 17:49:43 +0000
From: Peter Todd <pete@petertodd.org>
To: vjudeu@gazeta.pl,
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Message-ID: <ZPdqNxf2BsESnpIa@petertodd.org>
References: <98009035-ac19029087479e992d1f7eccdc9eb0ab@pmq6v.m5r2.onet>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature"; boundary="jhtI8hEbNQtDMqYB"
Content-Disposition: inline
In-Reply-To: <98009035-ac19029087479e992d1f7eccdc9eb0ab@pmq6v.m5r2.onet>
Cc: GamedevAlice <gamedevalice256@gmail.com>
Subject: Re: [bitcoin-dev] 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: Tue, 05 Sep 2023 17:49:50 -0000


--jhtI8hEbNQtDMqYB
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Sep 03, 2023 at 06:01:02PM +0200, vjudeu via bitcoin-dev wrote:
> > Given the current concerns with blockchain size increases due to inscri=
ptions, and now that the lightning network is starting to gain more tractio=
n, perhaps people are now more willing to consider a smaller blocksize in f=
avor of pushing more activity to lightning?
> =A0
> People will not agree to shrink the maximum block size. However, if you w=
ant to kill inscriptions, there is another approach, that could be used to =
force them into second layers: it is called cut-through, and was described =
in this topic: https://bitcointalk.org/index.php?topic=3D281848.0
> =A0
> Then, if you have "Alice -> Bob -> ... -> Zack" transaction chain, and fo=
r example some inscriptions were created in "Alice -> Bob" transaction, the=
n cut-through could remove those inscriptions, while leaving the payment un=
affected, because the proper amount of coins will be received by Zack, as i=
t should be.

You are incorrect: cut-through transactions will not meaningfully affect
inscriptions. While it is true that with fancy cryptography we can prove the
Alice -> ... -> Zack chain, that does not change the fact that Alice -> Bob=
 ->
Zack was mined in the blockchain, and those transactions exist. Anyone runn=
ing
a full archival node will still have those transactions, and can provide th=
em
(and all their inscription data) to anyone who needs it.

This is not unlike how in Bitcoin right now many people run pruned nodes th=
at
do not have any archival inscription data. Them running those nodes does not
prevent others from running full archival nodes that do make that data
available.

--=20
https://petertodd.org 'peter'[:-1]@petertodd.org

--jhtI8hEbNQtDMqYB
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE0RcYcKRzsEwFZ3N5Lly11TVRLzcFAmT3ajUACgkQLly11TVR
LzejAA//R1gyM9SO2ZSP1v25Bp4xwJFOM2ihWkgUVM4Py3XQI10oq0VxaAORefBq
APO7rAmgjiRt+E+3+O4sGTz6DmXvfGDT+RlHfaFae1OII3ABJ8p5SXxoTEWydrqg
WqT8pZa6ek5ZxCOVSjWwcfpa37hr11wsmgso8vw4qCjth6swcjEDQEahWca8iVbJ
FNDSD5iH/aMpUNxrRtqEI0eoTcrQjhwu7Igc0pOZztuSzp4u21uY9P8QmTxDsZV9
L8y371iB2agHsb/TU+vYzcZyn0v5GEPjTGWAeIJyhm+XW7r/rXNmEbjLpVShYkHH
1huZ6QX0HtEEOxRL+8Rc7uPCr9HgiSwU1kXZyq7hWK8uZhnifh2sSYdihGnr/rS3
M7+mT+IwEi/gT2Ulz23kuqLRrJBA7wOE6vJ0qopa78twShXh6vlkN2EwkXUuZ7My
FC//4SwWeV0kHmlazyfHKujK6dYxRNzM7qIk31UqW5Bp6l8Q8yFwQZSv5hZLPg93
tz2tPL7b7AlH5WC4e3mo64V4Q0yNS2AESIlGY8XfN3k8uKZn9o1KM9ZDXueIHMkd
daFgejf/b+0jgGaBtmk/3pA2s8XWkdFixG3GrxLNMuyvfUNIOSViO+PC7UWm+qHL
3keLMSA9QwRwTg98DX2SfQiXPMzaLgii7teva3L3h5SML3Ngfx4=
=xgmi
-----END PGP SIGNATURE-----

--jhtI8hEbNQtDMqYB--