Blockchain, cryptocurrency and smart contracts pioneer Nick Szabo has become the latest high-profile figure to declare his opposition to SegWit2x.
Nick ‘No2X’ Szabo Highlights Lack of Replay Protection
In typically understated fashion, Szabo added the increasingly widespread [No2X] label to his Twitter profile this week.
Looks like @NickSzabo4 has added the #NO2X tag to his twitter name :) Thanks Nick for showing people the way!
— Vortex | CTV / LNHANCE (@theonevortex) November 8, 2017
As one of Bitcoin’s original proponents, the move marks a further blow to SegWit2x in the eyes on the Bitcoin community, which already counts many of its most well-known names as detractors.
Szabo this week also quoted a post on the upcoming Bitcoin hard fork by Chaincode Labs’ Alex Morcos, which pays special attention to SegWit2x’s lack of replay protection.
“There is no downside to implementing optional 2-way replay protection. There is no argument against it,” the portion of Morcos’ blog post Szabo highlighted reads.
Any company that is still part of the the NYA needs to take the time to reflect on that and ask themselves why they are part of creating this completely unnecessary network disruption. The largest disruption in the history of Bitcoin.
SegWit2x Futures Drift Back To Square One
The issue of replay protection has frequently surfaced as a key downside of SegWit2x and Bitcoin Gold, leading supporters of the original Bitcoin chain to allege hostile attacks on the network by the forks’ developers.
“There is no excuse for not having it,” Morcos concluded in his post.
It’s hard to conclude as to why BTC1 doesn’t. Incompetence? Intentional desire to cause chaos? Or just gross negligence with the duty of care owed to the Bitcoin system?
SegWit2x futures prices meanwhile continue to decline, data from Coinmarketcap showing 10% daily losses and a press time value of $1,289. The fork had gone as high as $1,610, double its debut price of $810 late October.
What do you think about Nick Szabo’s stance on SegWit2x? Let us know in the comments below!
Images courtesy of Shutterstock, Twitter