[bitcoin-dev] Issolated Bitcoin Nodes
eric at voskuil.org
Fri Mar 24 01:58:37 UTC 2017
-----BEGIN PGP SIGNED MESSAGE-----
On 03/23/2017 05:20 PM, Pieter Wuille via bitcoin-dev wrote:
> On Thu, Mar 23, 2017 at 3:37 PM, Juan Garavaglia via bitcoin-dev
> <bitcoin-dev at lists.linuxfoundation.org> wrote:
>> Long story short, when nodes 0.13+ receive blocks from 0.13+
>> nodes all is ok, and those blocks propagate to older nodes with
>> no issues. But when a block tries to be propagated from bitcoind
>> 0.12.+ to newer ones those blocks are NOT being propagated to the
>> peers with newer versions while these newer blocks are being
>> propagated to peers with older versions with no issues.
>> My conclusion is that we have a backward compatibility issue
>> between 0.13.X+ and older versions.
> Hello Juan,
> this is expected behaviour. Nodes with segwit active only download
> blocks from other segwit peers, as old peers cannot provide the
> witness data they need to verify the blocks.
Juan's statement pertains to incompatibility, not mysterious causation.
Clearly it's a material consideration. Is it an oversight that this is
not documented as an incompatibility in any of the segwit BIPs?
I don't recall any discussion on the importance of segwit bridge
nodes. Is there a plan for bridging mainnet?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the bitcoin-dev