This week, the Segwit2x development team merged a controversial implementation into the project’s Github repository that masks BTC1 nodes from 0.15 version Core nodes. Additionally, the project added opt-in replay protection for Segwit2x transactions.
“To be honest, IMHO it was you who started the war by merging the change that disconnects their nodes from the Core’s network,” explained an individual that responded to Maxwell.
"We will see how it develops. 96% of the recently mined blocks have “/NYA/” tag inside the coinbase. If the split and the post-fork hashrate distribution ends up with such proportions, your bitcoin Core project is doomed. And the “replay protection” bloating the Core’s UTXO set would be just the final nail in your coffin — I guess that’s what scares you."
Read More Here >>> https://news.bitcoin.com/bitcoin-software-wars-segwit2x-node-masking-and-opt-in-replay-protection-merged/
“To be honest, IMHO it was you who started the war by merging the change that disconnects their nodes from the Core’s network,” explained an individual that responded to Maxwell.
"We will see how it develops. 96% of the recently mined blocks have “/NYA/” tag inside the coinbase. If the split and the post-fork hashrate distribution ends up with such proportions, your bitcoin Core project is doomed. And the “replay protection” bloating the Core’s UTXO set would be just the final nail in your coffin — I guess that’s what scares you."
Read More Here >>> https://news.bitcoin.com/bitcoin-software-wars-segwit2x-node-masking-and-opt-in-replay-protection-merged/
BTC1 by DEFINITION will disconnect from the Bitcoin network as soon as they hard fork. Segregating the network beforehand provides numerous benefits at that point, particularly with regard to network partitioning. Transactions can still be routed between the two networks until the hard fork occurs.
Then anything else that BTC1 does is purely for disruptive purposes. And this just demonstrates the recklessness and goals of BTC1 even more.
