Date: Wed, 02 Nov 2022 19:02:33 +0000
To: Peter Todd <pete@petertodd.org>
From: alicexbt <alicexbt@protonmail.com>
Message-ID: <fMZWicZXp5SM0ON8jgYuykBydOXcbgePbPfGKA0DQYtEDdiIr4bWljL_TqQHKtVKZRhvRXkEab47aaZw17OxGaSgOP2_w9_Owjb9WnTmsQ0=@protonmail.com>
In-Reply-To: <Y2I3w8O5X55sD/3C@petertodd.org>
References: <Y2I3w8O5X55sD/3C@petertodd.org>
Feedback-ID: 40602938:user:proton
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Announcement: Full-RBF Miner Bounty
Precedence: list

Hi Peter,

> 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 t=
he
> order of $1k/block in many cases, so I know it doesn't take that much mor=
e
> money to make a difference.

I appreciate this effort and perhaps this was all that was needed in additi=
on to Bitcoin Core's inclusion of full rbf support. Making it default right=
 away or enabling preferential peering with service flag in a bitcoin core =
release was unnecessary.

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

Sorry, I don't trust you based on some of the things you support on Twitter=
. Hopefully, others will donate and help this bounty.

/dev/fd0

Sent with Proton Mail secure email.

------- Original Message -------
On Wednesday, November 2nd, 2022 at 2:56 PM, Peter Todd via bitcoin-dev <bi=
tcoin-dev@lists.linuxfoundation.org> wrote:


> I'm now running a full-RBf bounty program for miners.
>=20
> 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 t=
he
> order of $1k/block in many cases, so I know it doesn't take that much mor=
e
> money to make a difference.
>=20
> Why should you do this? Full-RBF/zeroconf has been discussed to death. Bu=
t
> tl;dr: You'll earn more money, and help transition Bitcoin to a more secu=
re
> mempool policy based on economic incentives rather than trust.
>=20
>=20
> If you're a miner and want to participate, the easiest way to so is to us=
e the
> mempoolfullrbf=3D1 option in the upcoming Bitcoin Core v24 release (eg th=
e
> 24.0rc3 tag), or use the mempoolreplacement=3Dfee option in Bitcoin Knots=
.
>=20
> You can also just modify the code yourself by removing the opt-in RBF che=
ck.
> For example against the v23.0 tag:
>=20
> $ 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, Workspa=
ce& ws)
> // check all unconfirmed ancestors; otherwise an opt-in ancestor
> // might be replaced, causing removal of this descendant.
> if (!SignalsOptInRBF(*ptxConflicting)) {
> - return state.Invalid(TxValidationResult::TX_MEMPOOL_POLICY, "txn-mempoo=
l-conflict");
> + // return state.Invalid(TxValidationResult::TX_MEMPOOL_POLICY, "txn-mem=
pool-conflict");
> }
>=20
> ws.m_conflicts.insert(ptxConflicting->GetHash());
>=20
>=20
> Once you've enabled full-RBF, you need a full-RBF peer. I'm running a few=
 of
> them:
>=20
> cup.nop.lol
> mug.nop.lol
> jar.nop.lol
> jug.nop.lol
>=20
> These nodes run a preferential peering patch (https://github.com/bitcoin/=
bitcoin/pull/25600)
> to ensure that full-RBF nodes are interconnected to each other and replac=
ements
> can easily propagate. Also feel free to contact me if you'd like to peer =
with a
> private node.
>=20
>=20
> If you'd like to donate to this effort, send BTC to
> bc1qagmufdn6rf80kj3faw4d0pnhxyr47sevp3nj9m
>=20
>=20
> ...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 t=
oo
> concerned.
>=20
> --
> https://petertodd.org 'peter'[:-1]@petertodd.org
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev