-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 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 > <[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.
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? e -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBCAAGBQJY1H1AAAoJEDzYwH8LXOFOAk4H/RrJyexvyFKXfY7qC0bGCVwN 2iZ0wR0n/H0Z0qfP5nzDID0RARC3F/KFAAeLTaCIZa5uI0h3MrPbNm7hSi/m0nHJ mTzfJf0E8g+ETzyDpWjgR25ta6n3VdKp2tnNrY3z/ojnGYBFthpRDWV09K5trX5k qMyoPDfTP8jVIwihqx3MZLBnfiQKlEjNxCxmnuL7bh37msp6WK+elKudSrDBPiIi ljQ+u5NyeKWY+qzEzKPShIKnm3wC4K/RiiZIUvz60x6PCHr8OZGTEiKhPLWznVuj Q9gVtHxFzDpMZbxo4vP4nH+isQgqNa9gQ2E5783OC0/lpxHCoZEsgsD5lTAcp08= =GyRS -----END PGP SIGNATURE----- _______________________________________________ bitcoin-dev mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
