Feedback-ID: i525146e8:Fastmail
Date: Wed, 2 Nov 2022 05:26:27 -0400
From: Peter Todd <pete@petertodd.org>
To: bitcoin-dev@lists.linuxfoundation.org
Message-ID: <Y2I3w8O5X55sD/3C@petertodd.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature"; boundary="1ULUfi+m4lHJofa2"
Content-Disposition: inline
Subject: [bitcoin-dev] Announcement: Full-RBF Miner Bounty
Precedence: list


--1ULUfi+m4lHJofa2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

I'm now running a full-RBf bounty program for miners.

tl;dr: I'm broadcasting full-RBF replacements paying extremely high fees to
reward miners that turn on full-RBF. I'm starting small, just ~$100/block in
times of congestion. Miner and pool profit margins are pretty small, on the
order of $1k/block in many cases, so I know it doesn't take that much more
money to make a difference.

Why should you do this? Full-RBF/zeroconf has been discussed to death. But
tl;dr: You'll earn more money, and help transition Bitcoin to a more secure
mempool policy based on economic incentives rather than trust.


If you're a miner and want to participate, the easiest way to so is to use =
the
mempoolfullrbf=3D1 option in the upcoming Bitcoin Core v24 release (eg the
24.0rc3 tag), or use the mempoolreplacement=3Dfee option in Bitcoin Knots.

You can also just modify the code yourself by removing the opt-in RBF check.
For example against the v23.0 tag:

    $ git diff
    diff --git a/src/validation.cpp b/src/validation.cpp
    index 214112e2b..44c364623 100644
    --- a/src/validation.cpp
    +++ b/src/validation.cpp
    @@ -736,7 +736,7 @@ bool MemPoolAccept::PreChecks(ATMPArgs& args, Works=
pace& ws)
                     // check all unconfirmed ancestors; otherwise an opt-i=
n ancestor
                     // might be replaced, causing removal of this descenda=
nt.
                     if (!SignalsOptInRBF(*ptxConflicting)) {
    -                    return state.Invalid(TxValidationResult::TX_MEMPOO=
L_POLICY, "txn-mempool-conflict");
    +                    // return state.Invalid(TxValidationResult::TX_MEM=
POOL_POLICY, "txn-mempool-conflict");
                     }
    =20
                     ws.m_conflicts.insert(ptxConflicting->GetHash());

Once you've enabled full-RBF, you need a full-RBF peer. I'm running a few of
them:

    cup.nop.lol
    mug.nop.lol
    jar.nop.lol
    jug.nop.lol

These nodes run a preferential peering patch (https://github.com/bitcoin/bi=
tcoin/pull/25600)
to ensure that full-RBF nodes are interconnected to each other and replacem=
ents
can easily propagate. Also feel free to contact me if you'd like to peer wi=
th a
private node.


If you'd like to donate to this effort, send BTC to
bc1qagmufdn6rf80kj3faw4d0pnhxyr47sevp3nj9m


=2E..and yes, I'm well aware that miners could collect this bounty in other=
 ways,
eg by raising minimum fees. Doing that also breaks zeroconf, so I'm not too
concerned.

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

--1ULUfi+m4lHJofa2
Content-Type: application/pgp-signature; name="signature.asc"

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

iQIzBAEBCgAdFiEE0RcYcKRzsEwFZ3N5Lly11TVRLzcFAmNiN7sACgkQLly11TVR
LzdPIg/+NYI/u3S3HpbyCKG1UqT+0xpMJq4dwuh7l42z0zJaFWCp78GsY3tx2qB9
kE+puj+tUneMrSG4CCZMClt+k4xOVKhoJF7eo91z1wEgqLdlTMclRkrFHorQX2xg
pRpaLNIHjDiIHhkuxTzB5vSzNEeFaJ8EcMWy/MCs9zs3nTjnwL+zJbT25CX8jLp3
sokkCiccSA6wsex0OhdCRsH09UK2QdMIfUTLXeVOV1ce67HelFZx3CyvFcLdYHHl
0GjSSwNZAGFFXnH2ElkmkxRN7ih7SDaPp/QVRWyqQZxUUfTSPuDhp4INpVTQg8AZ
xtgjr87deyG13iKUf+RqLvPGQOJcr/3+tLKcLbcKOIjzboug/0HlOaR5Qbrjo1tt
vi4i5FOgl6zaK9+SqQ8ekMpmVmJHz93hK3x6q2sf0I4gkii7w54gx6U418aQxOT6
URGJStZwp5hYCG1l7eioyE7lOEQL4OEqH1XemSq6ppPy3o4AoP9TTdQ0cLZ/Ku6S
u1bAa5/Fkn4M6gF/gkKDSk+1kEzH+0X4OdMmD5IryOYEawrF7KKiYVQJv8mIacLI
m4gSb5bcGrfWZTqvV3Ilkf/waf02RmFqo1LPAHpHU05Kw9ss7oskbwuL+LqUstqU
jRyM3qKZmrzIdcQdsrmW1a4mVsi9qd6vAYM2EUELBKQprWdrpyw=
=D5dn
-----END PGP SIGNATURE-----

--1ULUfi+m4lHJofa2--