Feedback-ID: i525146e8:Fastmail
Date: Fri, 9 Dec 2022 16:16:20 -0500
From: Peter Todd <pete@petertodd.org>
To: 0xB10C <b10c@b10c.me>,
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Message-ID: <Y5OlpAi3wHPKxxkx@petertodd.org>
References: <Y2I3w8O5X55sD/3C@petertodd.org> <Y2qc7Ubc5xtJhxGw@petertodd.org>
 <Y3MlSE7AWkBgiCyr@erisian.com.au>
 <f146ca66-a611-f129-ae11-6907a7333d10@b10c.me>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature"; boundary="XP3EK/bse+5kVOQB"
Content-Disposition: inline
In-Reply-To: <f146ca66-a611-f129-ae11-6907a7333d10@b10c.me>
Cc: Anthony Towns <aj@erisian.com.au>
Subject: Re: [bitcoin-dev] Announcement: Full-RBF Miner Bounty
Precedence: list


--XP3EK/bse+5kVOQB
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Dec 09, 2022 at 05:04:05PM +0100, 0xB10C via bitcoin-dev wrote:
> Hi AJ and list,
>=20
> > This seems to be pretty good evidence that we currently don't have any
> > significant hashrate mining with fullrbf policies (<0.5% if there was a
> > high fee replacement available prior to every block having been mined),
> > despite the bounty having been collected.
>=20
> For further monitoring, I've set-up a mempoolfullrbf=3D1 node and are
> logging replacement events with [0]. I filter the full-RBF replacements
> and list the replaced and replacement transactions here:

Question: are you taking any special steps to peer that node with other
full-rbf nodes? I see you are in fact getting all the replacements I'd expe=
ct
you to get, so you must have good peering. I'm curious what it took (if
anything) to achieve that. Also, is that node accepting incoming connection=
s?

> Over the last few days, I has mostly seen OP_RETURN transactions
> (presumably mostly by OpenTimestamps; but I haven't checked closely) and
> a few other non-OP_RETURN transactions. None of the replacement
> transactions have been mined yet.

They are mostly OpenTimestamps transactions; I checked against the records =
=66rom
my calendars and didn't find any OP_Return tx that wasn't one of mine.

The two calendars making full-rbf replacements are:

https://alice.btc.calendar.opentimestamps.org/
https://bob.btc.calendar.opentimestamps.org/

The status pages currently link to https://mempool.nixbitcoin.org, which is
also running mempoolfullrbf=3D1 As you can see, I've started the full-rbf b=
ounty
again on Alice.

https://blockstream.info also enabled full-rbf a few days ago. But currently
propagation to their nodes is spotty, so replacements don't always show up.

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

--XP3EK/bse+5kVOQB
Content-Type: application/pgp-signature; name="signature.asc"

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

iQIzBAEBCgAdFiEE0RcYcKRzsEwFZ3N5Lly11TVRLzcFAmOTpZ4ACgkQLly11TVR
Lzdrog//ddKzk5jagYHtz4cPpzdp/rT+XIEJgiFTH5CNaG0QQyhVE9OZzg2MBDC7
eEM/ogwH016lSnx/GuXnUWdv50GCXh+LYoEGfP4lHfkoE9VaqGThA94YwJTj2YdT
cYuEiIhU9hWMr66D3pfip2iC9mzrftvWYeW9C/duAzOqxIUQNjqKqXUbkibDpmgX
q18OuJUB+JHCJ8xCZQd0o4gnrRGff4fJF+5dGXpbSrK+LV/srEMFcvyGkMKoiFMh
vPFlrevkN3Y7jatPnr+rQBkzGZZ85nSa11N3kMd5J6UJ7SVBt7jn8sm1rE7oz0TY
Yi0s3sY5+x2i6G9T+AYvJYVMuWd1ijxolxMS4dnX54ZvxXrRBVTX0bvLG2MKPmY9
YnYe+vRmGgQOtvXZjk816rLH01FWHAuq2YKBbbD4gGHvZ3bOMnChISAdZa94vGnM
vcaxufcR0lwRrNCxC66xARPpFdMSZe/HZ/Wbc5e1Rw1KYTJiTlIE2U3wUAOoulPs
Tndk4j4cVvE52JLDU9Tnrzag5jDlzz94R6ax/IUNIMJcKcG4+zqudxd7DS6eTheW
7QET/MSY7dIwottMJ867qXdQYsOKgqsAAfhkShZadXwVp4JU3q/8IV9OJeLFnxHj
n3sjKUf/KGlVtMORja8vVQuZT6oPi8SRR1PY+oh0kQ4x4+/+BuA=
=zrXj
-----END PGP SIGNATURE-----

--XP3EK/bse+5kVOQB--