From mboxrd@z Thu Jan  1 00:00:00 1970
Delivery-date: Mon, 05 May 2025 16:36:29 -0700
Received: from mail-oi1-f184.google.com ([209.85.167.184])
	by mail.fairlystable.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
	(Exim 4.94.2)
	(envelope-from <bitcoindev+bncBDRYHVHZTUGRB44W4XAAMGQENRYLG2A@googlegroups.com>)
	id 1uC5MK-00025X-PW
	for bitcoindev@gnusha.org; Mon, 05 May 2025 16:36:29 -0700
Received: by mail-oi1-f184.google.com with SMTP id 5614622812f47-3fa52ae463asf3878242b6e.1
        for <bitcoindev@gnusha.org>; Mon, 05 May 2025 16:36:28 -0700 (PDT)
ARC-Seal: i=2; a=rsa-sha256; t=1746488183; cv=pass;
        d=google.com; s=arc-20240605;
        b=PJCgEAVu9oFSdj8+PcUua61+1fCoHIKVRTpHQtxYLVaH2nREUTe4b6Ktlfg10i/BpI
         Kxo7BXsJY5mXxRFfLqK24gjpXk2VWExSwag7g684kxcjsVnGISs8PBuay3Jf9juJIFQ2
         DlfDNPI+7QMiF9ZA10TU0ERS8jE9LGCB2JrlD+iM8GFNfIQOnAMzVQP0FwiQvHUFTyWM
         c0ud+t7mes5cgDpg+vRbvzgB1hruD8JzWbtA3UHrhIoq6xx0fK/kw7BmiVfdyEcnmLEH
         TFAU2whPbDPqhhxIf/HrlKmksP15yi7rgLMbWXPvQneX1M3eV7i4+VkS7Y5m73+1ylXn
         PFuQ==
ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605;
        h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
         :list-id:mailing-list:precedence:in-reply-to:content-disposition
         :mime-version:references:message-id:subject:cc:to:from:date
         :feedback-id:sender:dkim-signature;
        bh=kJ51wj+02RStSYTF38NGAs9eRYDXAe1SRFmiZ2q8X20=;
        fh=XyPhlk2DLNrvgpOPm3PMYMq4anVEvaIgMKPnBVwm3D4=;
        b=QHh67CAka2UBay0+OkWAktUEsnwVS5Tojp2OFEfmkNd2ZIhk2zZU9VXIZLKEb+lGMA
         +DoBRpPKoq4AyhUujckCLvBX+ZRNqcIIXcGyXgF/g4Magq1dcL8aktmTuDvNlrt80/r9
         wtVTBjjDSO1yNetHb+0Kpqn2DZEmew1bZ6tjTqbEBMxd75Qn3o8NqR8PSjXyOs7Vynvf
         qln4z9o61kmvweHyJJaT1FQvmJKRX43Anu6laqqIvIiq7r2ldjLgJOenoInNSyIgipAY
         nReGYJRqtfZpwkEq3rNrhcHmz8uZM9N82QX0Ub6xm4sCMvsJdAot6FWV+FSh5eFCM5/N
         7asg==;
        darn=gnusha.org
ARC-Authentication-Results: i=2; gmr-mx.google.com;
       dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=hRr8llk9;
       spf=pass (google.com: domain of pete@petertodd.org designates 103.168.172.154 as permitted sender) smtp.mailfrom=pete@petertodd.org
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlegroups.com; s=20230601; t=1746488183; x=1747092983; darn=gnusha.org;
        h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
         :list-id:mailing-list:precedence:x-original-authentication-results
         :x-original-sender:in-reply-to:content-disposition:mime-version
         :references:message-id:subject:cc:to:from:date:feedback-id:sender
         :from:to:cc:subject:date:message-id:reply-to;
        bh=kJ51wj+02RStSYTF38NGAs9eRYDXAe1SRFmiZ2q8X20=;
        b=QX1ZAfEreDAl3BS1SRiNBa9L+AGj27YuT/1W/QUCBDem3X2kKd77bClDOULiHbY/2W
         WoCXr7dhIrqJB4hLeUeI55x/jgoShnt6yiGllwXxSwqK0hp3tpU8UssPEfb14cOkDGdG
         qeEnCW1qki4lDVl859+HjT3p57TzuM9JpMh0eW/URB/sL/7Q1PrMxIbjqbp1sYdabc+H
         SrEpJXPzusj7cBatUxD2GlYnMx7E/fF/I9/ks0nawzlIkFh/R3pw+QG/DuEEVoOpgOEX
         tvJZC2LH+Itwkk++QBduO5i6r9YyqNDCsq1Cav0TA6tC+Vj/DKJRH30LDLIlcpNKzkn2
         n0Gw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20230601; t=1746488183; x=1747092983;
        h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
         :list-id:mailing-list:precedence:x-original-authentication-results
         :x-original-sender:in-reply-to:content-disposition:mime-version
         :references:message-id:subject:cc:to:from:date:feedback-id
         :x-beenthere:x-gm-message-state:sender:from:to:cc:subject:date
         :message-id:reply-to;
        bh=kJ51wj+02RStSYTF38NGAs9eRYDXAe1SRFmiZ2q8X20=;
        b=HK26+P4FYaCtCex1fLWus/B0surJcEcDSi0wYcWAln8aM+mFd5Wu7gv2/rc9k5ct94
         IxUMTdywv+5/2ZkThQuSx2f7S3eu3uO/Im6RFuxZD1qm7IO85tSZZunDR6zYwomQYXin
         eKA9Ad6PucoHfc4luoZtp6KSPWPokP6k5hnCRSQWxsa2b+LLY4IrXNeYEfaKAAqRyx1+
         euSOClLkl2L+NGzNKyjdxTsIjOdkjeC2no0JEfZKXK0ef6ym7Qte/xzup6HIr8XLXjEa
         LgTfceYSsJy8TXHZppohEO8+p/kf18e3MmF20sMyY4Y6ZKBlUu8icBnCl8vkJKJEKQiM
         sMgQ==
Sender: bitcoindev@googlegroups.com
X-Forwarded-Encrypted: i=2; AJvYcCUxBsUymJ5NKiQLfyODuK74NQTLziRNGEa5xobyvXspOYIdyeoQAJO0kpcfMTTM5QmgvV5lN/fc1yFI@gnusha.org
X-Gm-Message-State: AOJu0YxFOi+Or6Oi8col/XtSfWzQjeT061FQUC4LwiyVaufwWlNQ27pO
	a2mceEv9Oa7jvxkkPMzfx77xrs/OHwSZxjBm1rvRXK2KZi58bsAg
X-Google-Smtp-Source: AGHT+IF/9gZmop0JdkZx1OJe7wLso+OBv9Hj3oEA3GE0juDbkJmMrAHdCqZhNOXsMLSFAWRHXozNog==
X-Received: by 2002:a05:6808:238a:b0:3fa:52ae:43dd with SMTP id 5614622812f47-4035a584756mr6502151b6e.19.1746488182685;
        Mon, 05 May 2025 16:36:22 -0700 (PDT)
X-BeenThere: bitcoindev@googlegroups.com; h=AVT/gBHS5mXjvqjrpjk76GoJ4F+4T+p1tMGs5qTxLAVuNzVOWw==
Received: by 2002:a4a:d145:0:b0:606:8605:dc0b with SMTP id 006d021491bc7-607df24e1a9ls1124250eaf.0.-pod-prod-07-us;
 Mon, 05 May 2025 16:36:18 -0700 (PDT)
X-Forwarded-Encrypted: i=2; AJvYcCVZeZLizHcDapdT5eNEObjbmtIvZKlGjHGDO9YVF5+uu/8fIMDFyzvZQfpJfqG1iFqbxNfYNha35gNv@googlegroups.com
X-Received: by 2002:a05:6808:1a12:b0:401:e6b9:8e2f with SMTP id 5614622812f47-4035a585303mr6463794b6e.22.1746488178828;
        Mon, 05 May 2025 16:36:18 -0700 (PDT)
Received: by 2002:a05:6808:14d5:b0:3fa:da36:efcd with SMTP id 5614622812f47-403425cae8dmsb6e;
        Mon, 5 May 2025 14:30:19 -0700 (PDT)
X-Forwarded-Encrypted: i=2; AJvYcCUald1LWtRa7g8rqh78V+scvreAE4vZTyQc7TLkfIgK59apeyUlDGJfuB2urqNvGTrPuXiSP5ldiv2O@googlegroups.com
X-Received: by 2002:a17:902:d508:b0:224:1001:6787 with SMTP id d9443c01a7336-22e1e8d3417mr130039375ad.4.1746480618078;
        Mon, 05 May 2025 14:30:18 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1746480618; cv=none;
        d=google.com; s=arc-20240605;
        b=U/o1CbW09XFXQbrB9XRWf8pYL7h8+R5K4G2LdEFtOMInA/dH0Cg3GijiBTugWflO3s
         ILCCIfpkTDOy3Qr+7UKSWAy/is58inV8EF1oi1OSLtK5edwsk6D9Qj2PfuD85yvdD9vS
         Av8/lknyTljPSB26LMJgANI0JjQjUUrizBo+3SLcnEkpj3wDxuJYAa/aAXXV8oJziMsH
         Gr8lE4KJaeQTiXM+QDhIXD9yGSnpPGIirLGIwLiJBWczU+fDZ21x9dSD6sm2rXEoGRas
         McMwRzKrYJYXIWq82nFJwnSsnO6Hk6HcgzCurVkN8KnzIDWYQs94rdYg+GCGwV5t805I
         SSuQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605;
        h=in-reply-to:content-disposition:mime-version:references:message-id
         :subject:cc:to:from:date:feedback-id:dkim-signature;
        bh=rTWWxP3eeu7nAX/7OC4Ob3wr5s3JGvyTirBJ3eMWXWI=;
        fh=ruQZ3+kDM9GiEW034PUw0HbiqqRlPNlZBdZH4gO05LM=;
        b=Pq+we9QQ+KXoR6n0JAC6fe8SnPukNF9F7dkPTJ+NIIzmNficShvEIgMZawuI38Mdxt
         GZJ4RpfCZRbOr/FBonVOSleBypBHFePtBWOyA9aFv4P39gH4ItdwlO/OLeXHw4zz7qgR
         dWpnf80gjpeVGKFIqZ8qyQlGCpc6/l7UdbxvrVALx+510QGYrYwx4qba6mFA2t7uze0C
         sCNcdcwlTBpRagihhFgNx04nse00LdmNFRWSrlkrtYIz2g25isFOHK8fG7Awl+KQdP10
         zbwMOCyTjfFtL8mGJROlQQHKDx07HaZbt++oORgtAvUgbBmtBfOw+8Y9R8ibDp5ztoki
         QKqA==;
        dara=google.com
ARC-Authentication-Results: i=1; gmr-mx.google.com;
       dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=hRr8llk9;
       spf=pass (google.com: domain of pete@petertodd.org designates 103.168.172.154 as permitted sender) smtp.mailfrom=pete@petertodd.org
Received: from fhigh-a3-smtp.messagingengine.com (fhigh-a3-smtp.messagingengine.com. [103.168.172.154])
        by gmr-mx.google.com with ESMTPS id d9443c01a7336-22e150de6f9si2776035ad.2.2025.05.05.14.30.17
        for <bitcoindev@googlegroups.com>
        (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
        Mon, 05 May 2025 14:30:17 -0700 (PDT)
Received-SPF: pass (google.com: domain of pete@petertodd.org designates 103.168.172.154 as permitted sender) client-ip=103.168.172.154;
Received: from phl-compute-03.internal (phl-compute-03.phl.internal [10.202.2.43])
	by mailfhigh.phl.internal (Postfix) with ESMTP id 271C7114018A;
	Mon,  5 May 2025 17:30:17 -0400 (EDT)
Received: from phl-mailfrontend-02 ([10.202.2.163])
  by phl-compute-03.internal (MEProxy); Mon, 05 May 2025 17:30:17 -0400
X-ME-Sender: <xms:6C0ZaD9gsa0yLTh6CD3W3tXZuJRzMZFOTM7BlhKtJRdxJOTE9H63tg>
    <xme:6C0ZaPuwCPXalIA9-qnHKaM-Rn7qUIac6LRDnjg-2wJqywIc_mOjqJ0eM-MQ1iYiI
    MKkgjUOUgkgN6fySSs>
X-ME-Received: <xmr:6C0ZaBA1eexvJXnfZeevKkP33iTnca6j1EAUJ6eNWRJ8AuViguZInJH2iLZAOw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefvddrtddtgddvkedvudekucetufdoteggodetrf
    dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggv
    pdfurfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpih
    gvnhhtshculddquddttddmnecujfgurhepfffhvfevuffkfhggtggujgesghdtreertddt
    jeenucfhrhhomheprfgvthgvrhcuvfhougguuceophgvthgvsehpvghtvghrthhouggurd
    horhhgqeenucggtffrrghtthgvrhhnpefgledvgeevjeffgffhueegffeltedvudeluddv
    gfdukefgffdufeeggfefkeekjeenucffohhmrghinhepghhithhhuhgsrdgtohhmpdhpvg
    htvghrthhouggurdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehm
    rghilhhfrhhomhepphgvthgvsehpvghtvghrthhouggurdhorhhgpdhnsggprhgtphhtth
    hopeefpdhmohguvgepshhmthhpohhuthdprhgtphhtthhopegrlhhitggvgigsthhonhhg
    sehgmhgrihhlrdgtohhmpdhrtghpthhtohepsghnrghgrggvvhesghhmrghilhdrtghomh
    dprhgtphhtthhopegsihhttghoihhnuggvvhesghhoohhglhgvghhrohhuphhsrdgtohhm
X-ME-Proxy: <xmx:6C0ZaPdj66Slp7HpjFl0hlU37LostMtSTGUjNjhpPcu-evOljM-Nkg>
    <xmx:6C0ZaIM-AUoSk_02aKE5jI7ZVdGaW1A_Wp2BNsVk2VPKsa2x2_gSGQ>
    <xmx:6C0ZaBnsW1y1kjYLvOmjVNi8mBxjnig0xWJwQoUbe9fPqEQl0QZneA>
    <xmx:6C0ZaCuO67Ctev0-g0eZC9gjgEkjreMl6lAQPLLIiorezhY8B-ClVA>
    <xmx:6S0ZaEw2ed7BS59ecF0AFiSG-4T24HDwCH9eVJe7F9h4Piaij5eC_UKR>
Feedback-ID: i525146e8:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon,
 5 May 2025 17:30:16 -0400 (EDT)
Received: by localhost (Postfix, from userid 1000)
	id 3733B9FBD9; Mon,  5 May 2025 21:30:14 +0000 (UTC)
Date: Mon, 5 May 2025 21:30:14 +0000
From: Peter Todd <pete@petertodd.org>
To: Nagaev Boris <bnagaev@gmail.com>
Cc: /dev /fd0 <alicexbtong@gmail.com>,
	Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Re: Relax OP_RETURN standardness restrictions
Message-ID: <aBkt5mtT-Zh2_hsl@petertodd.org>
References: <rhfyCHr4RfaEalbfGejVdolYCVWIyf84PT2062DQbs5-eU8BPYty5sGyvI3hKeRZQtVC7rn_ugjUWFnWCymz9e9Chbn7FjWJePllFhZRKYk=@protonmail.com>
 <9c50244f-0ca0-40a5-8b76-01ba0d67ec1bn@googlegroups.com>
 <47454755-7c6c-458b-9545-8c8657b640f1n@googlegroups.com>
 <aBUmn9HIYj06vbsX@petertodd.org>
 <CAFC_Vt41NOmM1Mscri+=SEPzPLb+Z83R2FzZkQuTVbBfGssMug@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="zHJZ/NJe4WrgFmpQ"
Content-Disposition: inline
In-Reply-To: <CAFC_Vt41NOmM1Mscri+=SEPzPLb+Z83R2FzZkQuTVbBfGssMug@mail.gmail.com>
X-Original-Sender: pete@petertodd.org
X-Original-Authentication-Results: gmr-mx.google.com;       dkim=pass
 header.i=@messagingengine.com header.s=fm3 header.b=hRr8llk9;       spf=pass
 (google.com: domain of pete@petertodd.org designates 103.168.172.154 as
 permitted sender) smtp.mailfrom=pete@petertodd.org
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com
List-ID: <bitcoindev.googlegroups.com>
X-Google-Group-Id: 786775582512
List-Post: <https://groups.google.com/group/bitcoindev/post>, <mailto:bitcoindev@googlegroups.com>
List-Help: <https://groups.google.com/support/>, <mailto:bitcoindev+help@googlegroups.com>
List-Archive: <https://groups.google.com/group/bitcoindev
List-Subscribe: <https://groups.google.com/group/bitcoindev/subscribe>, <mailto:bitcoindev+subscribe@googlegroups.com>
List-Unsubscribe: <mailto:googlegroups-manage+786775582512+unsubscribe@googlegroups.com>,
 <https://groups.google.com/group/bitcoindev/subscribe>
X-Spam-Score: -0.8 (/)


--zHJZ/NJe4WrgFmpQ
Content-Type: text/plain; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, May 04, 2025 at 05:04:23PM -0300, Nagaev Boris wrote:
> > The `mempoolfullrbf` option was a good example of how keeping an option
> > to reject otherwise standard transactions is just wasted effort. Having
> > the option didn't stop full-rbf replacements from getting mined; user's
> > refusing to relay a transaction type that a significant % of miners are
> > mining acomplishes nothing.
> >
> > In that *specific* case there were a tiny number of users, Wasabi's
> > Coordinator being an example, where for technical reasons full-rbf
> > replacements caused problems until that code was fixed; giving those
> > users an option to temporarily disable those replacements was sort of
> > useful. But there's no reason to think that will be true with OP_Return
> > outputs, and in any case, you can just delaying upgrading your node
> > while you fix your broken code.
> >
>=20
> If I understand correctly, the Wasabi bug is described in this issue:
> https://github.com/WalletWasabi/WalletWasabi/issues/10648
> It was opened in May 2023. If the option hadn't been available at that
> time, it would have been much harder for Wasabi coordinators to
> mitigate the issue =E2=80=94 they would have had to patch Bitcoin Core or=
 use
> an alternative node implementation, rather than just toggling a
> setting.

No, in this hypothetical case (see below) they could have just
downgraded to the earlier version. There's no rush to adopt new Bitcoin
Core versions.

> Also note that the bug in Wasabi was discovered after mempoolfullrbf
> was added in July 2022. The first Bitcoin Core release to include this
> change was v24.0.1, in December 2022. It took several months after
> that release for the Wasabi team to realize that mempoolfullrbf=3D1
> created problems for their use case. If the feature had been released
> without a flag (enabled by default with no way to disable it) it would
> have made things significantly harder for them.

Nope. Wasabi was actually running Bitcoin Knots, which had full-rbf
enabled by default long before Bitcoin Core did. In *their* case, IIRC
they just turned it off, fixed their code, and turned it back on.

> There may also be users today who rely on datacarrier
> behaviour/options without yet realizing they're scheduled for removal.
> If the options are simply relaxed in the next release, users could
> still set the values they need and have time to adjust their
> infrastructure. It would give them a chance to move away from relying
> on those settings before they're removed entirely in a future version.
> Otherwise, they may be forced to either switch to another node
> implementation or remain on version 29.

It is *very* hard to imagine removing datacarrier causing issues given
that oversized OP_Returns regularly show up in blocks. We don't need to
put unlimited effort into hypotheticals. The only way this would be an
actual issue if it you had mempool-specific code that was so broken that
it broke on an oversized OP_Return (or more than one), and yet somehow
you desperately needed to use a *new* version of Bitcoin Core.

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

--=20
You received this message because you are subscribed to the Google Groups "=
Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/=
aBkt5mtT-Zh2_hsl%40petertodd.org.

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

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

iQIzBAEBCgAdFiEE0RcYcKRzsEwFZ3N5Lly11TVRLzcFAmgZLdcACgkQLly11TVR
LzfYvA//bhPrhA0yUVTgLaNZ5DGF+bauD0Q03gUBUyv1zJos/a+z/lS7DwEokjs1
aI8JeYPwgMZgfk1JtuYMLM3IojNQZtyyxjgbu7dtHokuNVBMmriivtrmROsMquMq
5m8V+cqk1P//lzZKxqHwhgaHtLgOmsOaPUgyqymoxZoshuOaLgFPmydQ5bRMNihI
bR4xwMPgVm+daWKvzaneqlqAef8mChe3vCC0saMlYEy3AX7o7pyj8ZZMpoVfW4sk
Kbp5lRFnDwJ39fRfdcyLhbDVN2KQFNAo3Py9sxoqrXPp7n8a8X/VbMovK8wMhnJ7
NmlfHWsuURdZJPYfK/4zVgu2KaatCJBXRYV+fQsE5wqMOexc57Dmx8QNs6+7DN44
Fmk2JwLsr3j6YGnT5RDb6h+L4EbLqeDOPyUH6BR0XF86iy2Da55rpGTwNnEENNnY
gZsvWpFQWb/+QPslPL8ebERlLJmMwjT17CE3HZuOP7R+f06bQVQIYH+L2qRCDSXG
lUlze1HMrTfKL+gXlrry2qkXHPJeallOLZnku0KfO3kfohxNAz+z49XZuapXQjfE
yMDEf1xhGuNcv7+pXG6K6GcLsKpcgzKqYJEcrCXPTXCb0FiOwbJk9r47IaklnVO8
LPsVm9xXz8Tck4vx3ODj+Oj8pnLj7AfdXnICYZdG6YUrjwSzszA=
=u3/k
-----END PGP SIGNATURE-----

--zHJZ/NJe4WrgFmpQ--