Delivery-date: Tue, 23 Jul 2024 04:40:55 -0700
Sender: bitcoindev@googlegroups.com
Received-SPF: pass (google.com: domain of pete@petertodd.org designates 103.168.172.151 as permitted sender) client-ip=103.168.172.151;
Feedback-ID: i525146e8:Fastmail
Date: Tue, 23 Jul 2024 11:29:04 +0000
From: Peter Todd <pete@petertodd.org>
To: "David A. Harding" <dave@dtrt.org>
Cc: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] RBFR makes the CPFP carve-out obsolete with cluster
 mempool, without upgrading LN nodes; TRUC/V3 does not
Message-ID: <Zp+UAAtYDBqcgzEd@petertodd.org>
References: <Zpk7EYgmlgPP3Y9D@petertodd.org>
 <c6593662694f9d4a4fe999dd432f87ff@dtrt.org>
 <Zp5GW/yHzPB8wyjU@petertodd.org>
 <0eeb34c87b4cd7c9165983dc3a613550@dtrt.org>
 <Zp674YtMTaUX3imH@petertodd.org>
 <6c222c758e10e8061ccdcc180b1826a3@dtrt.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="l9GYZYVe6stwkzM2"
Content-Disposition: inline
In-Reply-To: <6c222c758e10e8061ccdcc180b1826a3@dtrt.org>
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com


--l9GYZYVe6stwkzM2
Content-Type: text/plain; charset="UTF-8"
Content-Disposition: inline

On Mon, Jul 22, 2024 at 12:08:28PM -1000, David A. Harding wrote:
> > Frankly, unless you can point to actual "significant discussion and
> > analysis"
> > of the idea, it's dishonest and toxic of you to portray it as such as
> > you
> > should know better.
> 
> I'm sorry you've been unable to keep up with protocol development and
> are confusing that for me being dishonest and toxic.  May I suggest you
> subscribe to the weekly Optech newsletter?  It's free.

Ironically, while toxicly and dishonestly accusing me of being "unable to keep
up with protocol developments", you proved I was in fact quite aware of imbued
TRUC around the same time it got it's mention in Optech, and was even involved
in the short discussion of it.

Anyway, I'll stand by my earlier comment: the fact is the imbued TRUC proposals
are currently dead, and never received significant discussion and analysis. I
did forget about the fact that a draft pull-req was made. But that pull-req was
a mere draft and the author has abandoned it without responding to critique,
and only a few weeks after authoring it, even said on Feb 28 that "I would also
prefer to not merge the imbued v3 patch.":

https://github.com/bitcoin/bitcoin/issues/29319#issuecomment-1969122250

...and one of the LN maintainers queried explicitly argued against it, saying,
among other things, "I'm not a fan of merging hacky, temporary code into
bitcoin core to be honest.":

https://github.com/bitcoin/bitcoin/issues/29319#issuecomment-1968709925

Notice how that's an issue where I commented something like a half dozen times,
including after the author of imbued TRUC gave up on it.

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

-- 
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 email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bitcoindev/Zp%2BUAAtYDBqcgzEd%40petertodd.org.

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

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

iQIzBAEBCgAdFiEE0RcYcKRzsEwFZ3N5Lly11TVRLzcFAmafk/MACgkQLly11TVR
LzdzKg/8DeCPuumEB2ukkepj33GZsLYCOEy6/kkdLpl6vhc7Mi/bRN43pzj0sGoQ
K+FQ1AhOBd9k/jr0bpgEZ5I60LdBxBxBXxqMpDeO8DEOSrtdIggFVoBL7mCNrmq/
u0d7jEWQ7n29bDbRm2fIqqXJGPfLtsInc90DfX7dFJukJje37bVU5Ovv4mjhLWp/
Wdziy8+GnQ+kQFZsEbPD6idrQCcAc3CqR7NSH3cz6o+rfuemTyzmDo+vw4oyWlGP
K2iPPfHNbEK9YXnkqANbAqufkFmoWay6SMasgWnyslMt/xCQrxgWHGNebN0O3uKo
oS7nyae2IfKCRH1ytylKUV3Vby9azc81cnPnjIDIY9OSnPIXcTIgHEtzZDZXHLWX
3OYgVrngkThQqLlCIWKfxl1OS14toYCz/SaSwGLrf35fGaWhuLrIJzJimXqFxULP
SxB4Ao0cHBOYxECkM5Z+6Bl3c5E7mif8/yDWgcBKxVN04bYGUw0vPqIRJ+hITylr
56KvZ+7d+GXDmQzqlmFwmnnDpcR7Fvf3DLd5iRsQXXmPucaHKl4K1VnJat30uFDf
lME0OUS2nJAcRJ/myT0iuZUo3wDffJno+m4JgD9rb9M2DIjvcdDfIcvB2X9XuCHL
4tKIdeX8nOMg5+6Fvxum/GxoF4fx0zgojZ4Ns9xF0n4bULEUouA=
=54He
-----END PGP SIGNATURE-----

--l9GYZYVe6stwkzM2--