There were bridge nodes being run on testnet at one point to prevent forks https://github.com/jl2012/bitcoin/commit/9717d856e72baa939d4b273f0a56e6009978e11b
On Thu, Mar 23, 2017 at 7:20 PM, Pieter Wuille via bitcoin-dev <[email protected]> wrote: > On Thu, Mar 23, 2017 at 3:37 PM, Juan Garavaglia via bitcoin-dev > <[email protected]> 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. > > -- > Pieter > _______________________________________________ > bitcoin-dev mailing list > [email protected] > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev _______________________________________________ bitcoin-dev mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
