public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
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 v25.1 Released
Date: Thu, 26 Oct 2023 22:20:21 +0000	[thread overview]
Message-ID: <ZTrmJUDWaKCw5zCm@petertodd.org> (raw)
In-Reply-To: <CAFyhPjWTOhkckhH-7DJ96m_67HL26-b8zYadr84_dN13n8aBuA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]

Available from: https://github.com/petertodd/bitcoin/tree/full-rbf-v25.1

eg:

    git clone -b full-rbf-v25.1 https://github.com/petertodd/bitcoin.git

What is this? It's Bitcoin Core v25.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

At the moment, ≥31% of hash power, ≥4 pools, are mining full-RBF:

https://petertodd.org/2023/fullrbf-testing


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 --]

      reply	other threads:[~2023-10-26 22:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-19 16:13 [bitcoin-dev] Bitcoin Core 25.1 released Michael Ford
2023-10-26 22:20 ` 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=ZTrmJUDWaKCw5zCm@petertodd.org \
    --to=pete@petertodd.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=fanquake@gmail.com \
    /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