Discussion:
Bitcoin Knots 0.14.0 release candidate 1 available
(too old to reply)
Luke Dashjr via bitcoin-dev
2017-02-19 12:12:55 UTC
Permalink
Raw Message
Release candidate 1 of a new major Bitcoin Knots release, version 0.14.0, has
been made available.

This is a release candidate for a new major version release, including new
features, various bugfixes and performance improvements.

Preliminary release notes for the release can be found here:

https://github.com/bitcoinknots/bitcoin/blob/v0.14.0.knots20170218.rc1/doc/release-notes.md

Binaries can be downloaded from:

http://bitcoinknots.org/files/0.14.x/0.14.0.knots20170218.rc1/

Please take care to verify the PGP signature of all downloads.

Source code can be found on GitHub under the signed tag

https://github.com/bitcoinknots/bitcoin/tree/v0.14.0.knots20170218.rc1

Release candidates are test versions for releases. When no critical problems
are found, this release candidate will be tagged as 0.14.0 final, otherwise
a new rc will be made available after these are solved.

Please report bugs using the issue tracker at GitHub:

https://github.com/bitcoinknots/bitcoin/issues
Peter Todd via bitcoin-dev
2017-02-19 21:30:01 UTC
Permalink
Raw Message
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
Loading...