From: Peter Todd <pete@petertodd•org>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] replace-by-fee-v0.14.0rc1 available
Date: Sun, 19 Feb 2017 16:30:01 -0500 [thread overview]
Message-ID: <20170219213001.GA10603@savin.petertodd.org> (raw)
In-Reply-To: <201702191213.01101.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 758 bytes --]
My full-RBF patched branch of Bitcoin Core v0.14.0rc1 is now available:
https://github.com/petertodd/bitcoin/tree/replace-by-fee-v0.14.0rc1
As with replace-by-fee-v0.13.2, this version uses the nRelevantServices
machinery to do preferential peering, so it's just a few lines of code changed
between it and Bitcoin Core v0.14.0rc1.
The relevant services machinery is less agressive at connecting to full-RBF
peers than the earlier custom code previous versions used. But it seems to work
well enough to keep RBF peers connected to each other, so I'm inclined to keep
using it as doing so makes maintaining this patched branch pretty trivial every
time a new upstream version is released.
--
https://petertodd.org 'peter'[:-1]@petertodd.org
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
prev parent reply other threads:[~2017-02-19 21:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-19 12:12 [bitcoin-dev] Bitcoin Knots 0.14.0 release candidate 1 available Luke Dashjr
2017-02-19 21:30 ` 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=20170219213001.GA10603@savin.petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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