Delivery-date: Sun, 14 Apr 2024 08:58:22 -0700
Sender: bitcoindev@googlegroups.com
Received-SPF: pass (google.com: domain of pete@petertodd.org designates 103.168.172.149 as permitted sender) client-ip=103.168.172.149;
Feedback-ID: i525146e8:Fastmail
Date: Sun, 14 Apr 2024 15:51:34 +0000
From: Peter Todd <pete@petertodd.org>
To: Bitcoin Error Log <bitcoinerrorlog@gmail.com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Draft BIP for User-Defined Transaction Flags Policy
 & Strategy
Message-ID: <Zhv7hp9aydx3KAQA@petertodd.org>
References: <cc812488-9da0-4595-be3b-bcfd7ab41106n@googlegroups.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="+nWLEuNS/Dm2Vxv0"
Content-Disposition: inline
In-Reply-To: <cc812488-9da0-4595-be3b-bcfd7ab41106n@googlegroups.com>
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com


--+nWLEuNS/Dm2Vxv0
Content-Type: text/plain; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Apr 14, 2024 at 08:09:51AM -0700, Bitcoin Error Log wrote:
> Adoption and Transition Strategy & Requirements
>=20
> It is implicit, until now, that within this strategy is a requirement for=
=20
> Core and other implementations to abandon strategies within Option 2, by=
=20
> specifically removing and rejecting policy tools like mempoolfullrbf, or=
=20
> other attempts to overrule, filter, or otherwise filter and hamper the=20
> propagation of valid, non-destructive transactions.

For the record, I will continue to distribute both my Libre Relay=C2=B9 and=
 Full-RBF
Peering=C2=B2 forks of Bitcoin Core, and they will continue to propagate fu=
ll-rbf
replacements. I'd estimate roughly 30 nodes in total on the P2P network are
running one of those two forks. Bitcoin Knots also enables full-RBF by defa=
ult,
and has something like 150 nodes.

90%+ of hash rate is running full-RBF because it's common for blocks to ear=
n
thousands of dollars worth of fees from full-RBF replacements.  The idea th=
at
miners would give that up, en-mass, just because you asked nicely for the s=
ake
of your broken, insecure, and unused ways of transacting bitcoin is laughab=
le.
Miners regularly modify the Bitcoin Core codebase for their own needs;
commenting out the one line of code that prevents full-RBF replacements is
trivial.

You'd do well to stop wasting your time with this nonsense and work on
Lightning or something. As for Bitcoin Core, enabling full-RBF by default i=
s
well overdue: https://github.com/bitcoin/bitcoin/pull/28132

1) https://github.com/petertodd/bitcoin/tree/libre-relay-v27.0rc1
2) https://github.com/petertodd/bitcoin/tree/full-rbf-v27.0rc1

--=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 on the web visit https://groups.google.com/d/msgid/=
bitcoindev/Zhv7hp9aydx3KAQA%40petertodd.org.

--+nWLEuNS/Dm2Vxv0
Content-Type: application/pgp-signature; name="signature.asc"

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

iQIzBAEBCgAdFiEE0RcYcKRzsEwFZ3N5Lly11TVRLzcFAmYb+4QACgkQLly11TVR
LzepeA//c0IwFPD5f9+3PTbCAFirMsYpNMDoLTjI9pslZcpe06XaxW9mK6VKq0D6
W1tjkim8LKU0FFsB0CKUoG/Rh/peQP9ogOVbkxz8TWYhdZIeBaiwIwhw1kJUgYvB
H85AxIZTQmw2K9tgDMGnqeK8JvxVFFAGMA5j/MW25jZoQtbNoxEIjJl5ui888ts2
eeup6Mkn1zX+5CptyXKp06I5sJ4/EPanH9ZYNmWrbq5Y2Mf9+N9s18BALlYYooZj
X30htIP6PInYwb9EnpSTjBBgwBCAkXRZm1oddJ9GucnJweJJswJFUvHWZNvGut2i
A+WkpshBJ60/1wHWjUHKmz/4oc/EIn0hqOWHwzYD250s6FqNP1sD34If/iPr2WL9
N/mqFZ710+ACfWQQSeksfPfeW05SaYeCkYTqljLRGYEWt4Oe7dgePcw762ou6Elo
YsqKqG/VK3mTt6rhs/PX5HOZiBZypxfEQ+Vos14yMeQLvFAASy46SbvgVjQmNCmL
AQW1wir60L8I+6gKhOYc5o++Lr1knv/miy5pKPc/zXBGH51YY3Y3xkQpKkFv70sr
yrNmCtx2Eeb0n4wAZYm5WSwyC5AzzF0PK75f3AufhHAu/v4XxJsAE02Ly5NljSGE
b47SIiAHUmaX77Um+joT4YjbF8yixQvhlf8VIxI51lTb6JGY+qg=
=+BTi
-----END PGP SIGNATURE-----

--+nWLEuNS/Dm2Vxv0--