[2017-10-05] Segwit2x Node Masking and Opt-in Replay Protection Merged

[Iloveelvis]

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/

[1714862688]

1714862688

[1714862688]

1714862688

[1714862688]

1714862688

[ChromaticStar]

How can anyone support 2x when this is the kind of thing that they do?

Garzik has no ethical standards. Is it worth bailing on BTC until this hardfork plays out?

[hatshepsut93]

Garzik has no ethical standards. Is it worth bailing on BTC until this hardfork plays out?

It seems like SegWit2x are ready to do anything to force their fork upon Bitcoin community, so I wouldn't be surprised to see even more blatant and malicious stuff like switching online wallets and all funds into 2x chain. This is because the stakes are very high for them - if 2x chain will fail to get adopted by Bitcoin users, all companies and miners who actively supported if will suffer major loses.

Garzik has no ethical standards. Is it worth bailing on BTC until this hardfork plays out?

Very hard to say, with Bitcoin selling at the wrong time can be a huge opportunity loss. For example, there was a huge dip just before SegWit voting period, but it quickly recovered and it hasn't moved at all during Bcash fork - if 2x attack will be small, Bitcoin's price might barely move.

[cr1776]

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/

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.