Date: Sun, 19 Feb 2017 16:30:01 -0500
From: Peter Todd <pete@petertodd.org>
To: bitcoin-dev@lists.linuxfoundation.org
Message-ID: <20170219213001.GA10603@savin.petertodd.org>
References: <201702191213.01101.luke@dashjr.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="VbJkn9YxBvnuCH5J"
Content-Disposition: inline
In-Reply-To: <201702191213.01101.luke@dashjr.org>
User-Agent: Mutt/1.5.23 (2014-03-12)
Subject: [bitcoin-dev] replace-by-fee-v0.14.0rc1 available
Precedence: list


--VbJkn9YxBvnuCH5J
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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 chan=
ged
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 k=
eep
using it as doing so makes maintaining this patched branch pretty trivial e=
very
time a new upstream version is released.

--=20
https://petertodd.org 'peter'[:-1]@petertodd.org

--VbJkn9YxBvnuCH5J
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCAAGBQJYqg5VAAoJECSBQD2l8JH788oH/35Y4FvseqdMc2zLznIplc+5
xfURlAMtSjVu2+b3mt1D/pXxdsop3nQYL4Zn36SGKw8etQdAqGDWUiIL146KA7aN
rJRer5yzW+yCk/w0ZZI1b8aNpIzjssJ7u6og+lBfX/4dvpB4slfap/JOgPodgEQq
OaFwfuNr8pB3Vmm2RGByqFDEdBWD0Ewga8W7wqP90XVYnLjPU5jPtB2h36wrH2OR
PjNBZQf5ZgFqQzq0n1sN9jAVP5hp1+5nbsv135Ml8ISB0V5gXWm16ozvLXCSqImT
HCswKvwmOwU2younQWcwyVrQYXg2Bjv5qYHtNyz1XfThrOEchwY4Yghm0RkZKW0=
=GRHl
-----END PGP SIGNATURE-----

--VbJkn9YxBvnuCH5J--