From: Peter Todd <pete@petertodd.org>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] Full-RBF Peering Bitcoin Core v26.0 Released
Date: Sat, 20 Jan 2024 21:33:39 +0000 [thread overview]
Message-ID: <Zaw8M5Dj46pdwMQm@petertodd.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 887 bytes --]
Available from: https://github.com/petertodd/bitcoin/tree/full-rbf-v26.0
eg:
git clone -b full-rbf-v26.0 https://github.com/petertodd/bitcoin.git
What is this? It's Bitcoin Core v26.0, 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
I'm already running v26.0 on a few nodes with v2transport=1 enabled. You should
too!
--
https://petertodd.org 'peter'[:-1]@petertodd.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2024-01-20 21:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Zaw8M5Dj46pdwMQm@petertodd.org \
--to=pete@petertodd.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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