Return-Path: Received: from smtp1.osuosl.org (smtp1.osuosl.org [IPv6:2605:bc80:3010::138]) by lists.linuxfoundation.org (Postfix) with ESMTP id 66A86C002D for ; Wed, 2 Nov 2022 09:26:35 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id 2B0A58176C for ; Wed, 2 Nov 2022 09:26:35 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 2B0A58176C Authentication-Results: smtp1.osuosl.org; dkim=pass (2048-bit key, unprotected) header.d=messagingengine.com header.i=@messagingengine.com header.a=rsa-sha256 header.s=fm3 header.b=a/LffZqV X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.101 X-Spam-Level: X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, PDS_BTC_ID=0.499, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from smtp1.osuosl.org ([127.0.0.1]) by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I1IVq-RMqtNb for ; Wed, 2 Nov 2022 09:26:33 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 8FDF581769 Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by smtp1.osuosl.org (Postfix) with ESMTPS id 8FDF581769 for ; Wed, 2 Nov 2022 09:26:33 +0000 (UTC) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id E365E5C00C8 for ; Wed, 2 Nov 2022 05:26:29 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Wed, 02 Nov 2022 05:26:29 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:message-id:mime-version :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1667381189; x= 1667467589; bh=jEKfNUr7E/lk00cxNY4o8z9XxFe/TXMalvWtH9KSlus=; b=a /LffZqViL3E/WOB2aBPSFFZhxsPZpyN7X1qhWFj3FmiTIxkfyR2Bs72i9ZX9drhU IzU8IkyO9XGd0h9SUQxQh9GWBWVNjQL+pDJvP1STkKW6istzjT8FDjmRYS2ntxki uTqK6XmlTesHhZ2FwS5nkKFu7gCZxewSdqn5z2y8p9RWC+PLK0paeVAMbAl258K3 MoXalnFrJKJZ3nBuiIhTccx+L1O/HMh9F8ijUKZxg/nJf0YhysMtt3iHSWVGFsJL aqAVz159ULgxJN3NQMyBHMgwXxmkYrgANwEArfz86wSx9aDLlkkZ40oS9fqGtoqZ syuhmRZx1HLuoD1XX3U+g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvgedrudejgddtvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepfffhvffukfggtggusehgtderredttd dvnecuhfhrohhmpefrvghtvghrucfvohguugcuoehpvghtvgesphgvthgvrhhtohguugdr ohhrgheqnecuggftrfgrthhtvghrnhepieevieehudejteffgfekuedvledvudelveeiff evffegteehleetkefhgfeiteetnecuffhomhgrihhnpehnohhprdhlohhlpdhgihhthhhu sgdrtghomhdpphgvthgvrhhtohguugdrohhrghenucevlhhushhtvghrufhiiigvpedtne curfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvgesphgvthgvrhhtohguugdrohhrgh X-ME-Proxy: Feedback-ID: i525146e8:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Wed, 2 Nov 2022 05:26:29 -0400 (EDT) Received: by localhost (Postfix, from userid 1000) id 430AC5F82D; Wed, 2 Nov 2022 05:26:27 -0400 (EDT) Date: Wed, 2 Nov 2022 05:26:27 -0400 From: Peter Todd To: bitcoin-dev@lists.linuxfoundation.org Message-ID: 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 X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2022 09:26:35 -0000 --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--