From: Peter Todd <pete@petertodd•org>
To: Michael Ford <fanquake@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Full-RBF Peering Bitcoin Core v24.1 Released
Date: Sun, 21 May 2023 21:21:33 +0000 [thread overview]
Message-ID: <ZGqLXaa4aiyGdVaH@petertodd.org> (raw)
In-Reply-To: <CAFyhPjVNQztgy-+Jrnhcd9qS=Uky3_m4LnO1NA+2=WCc0PzoRQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1085 bytes --]
On Fri, May 19, 2023 at 11:56:14AM +0100, Michael Ford via bitcoin-dev wrote:
> Bitcoin Core version 24.1 is now available from:
>
> <https://bitcoincore.org/bin/bitcoin-core-24.1/>
Available from: https://github.com/petertodd/bitcoin/tree/full-rbf-v24.1
eg:
git clone -b full-rbf-v24.1 https://github.com/petertodd/bitcoin.git
What is this? It's Bitcoin Core v24.1, with Antoine Riard's full-rbf peering
code, and some additional minor updates to it. This does two things for
full-rbf nodes:
1) Advertises a FULL_RBF service bit when mempoolfullrbf=1 is set.
2) Connects to four additional FULL_RBF peers.
Doing this ensures that a core group of nodes are reliably propagating full-rbf
replacements. We don't need everyone to run this. But it'd be helpful if more
people did.
As for why you should run full-rbf, see my blog post:
https://petertodd.org/2023/why-you-should-run-mempoolfullrbf
We even have hats! :D
https://twitter.com/peterktodd/status/1659996011086110720/photo/1
--
https://petertodd.org 'peter'[:-1]@petertodd.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-05-21 21:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 10:56 [bitcoin-dev] Bitcoin Core 24.1 released Michael Ford
2023-05-19 11:20 ` Sjors Provoost
2023-05-21 21:21 ` Peter Todd [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZGqLXaa4aiyGdVaH@petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=fanquake@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox