Bitcoin (BTC)

$ 7292.96

Bitcoin Cash (BCH)

$ 0.449377

Ethereum (ETH)

$ 454.426

Ripple (XRP)

$ 763.635

HOT NEWS
Bitcoin Costs Stabilize Above $6K – But Will They Keep? Jim Chanos Is Out of His Depth Trashing Crypto Assets There&#039s A New Bitcoin Core in Town – And It&#039s Out to Troll Bitcoin Money Enjoy Decentralized Art at Satoshi’s Place Bitcoin and Manga Collide in Shonen Crypto Switzerland Rejects Pro-Crypto Sovereign Money Initiative Coinbase Announces Intended Support for Ethereum Classic
Homepage / News November 17, 2017 218 views

No Fork, No Fire: Segwit2x Nodes Stall Running Abandoned Bitcoin Code

No Fork, No Fire: Segwit2x Nodes Stall Running Abandoned Bitcoin Code

The Segwit2x bitcoin fork may have been formally known as off, but as many as 150 nodes still operating its code have stopped accepting transaction blocks.

Information from Bitnodes shows that 95 nodes are presently operating 2x application and are stuck at block quantity 494,782. CoinDance, another network information web site, says that 154 nodes are running the “btc1” application as of press time.

The situation is a curious one particular, offered that the 2x fork work – advanced by a group of startups, miners and neighborhood supporters as a way to expand the transaction capacity of the bitcoin network – was successfully disbanded on Nov. 8 following an e mail circulated on the project’s mailing list. But regardless of the abandonment, dozens of nodes continue to be operated that use the most-recent btc1 software release.

Today’s stoppage appears to be driven by an problem in the code that prevented miners from in fact creating a bigger-than-1 MB block that would push nodes running Segwit2x into its own chain. Amid growing discussion in the project’s Slack channel, developer Jeff Garzik released a patch aimed at easing the creation of a bigger transaction block (though in the absence of strong mining help, it’s unlikely that the network will advance).

And even though the Segwit2x fork itself will not move forward, today’s improvement revived some of the acrimony between these who supported the work and these who have voiced vehement opposition to it.

One particular distinct point of contention is the precise block quantity at which the fork was supposed to activate.

Past materials indicate that this block would have been&nbsp494,784, top critics to say that developer Garzik had an “off-by-1” error and that, if carried out, the nodes planning to fork could have been caught in limbo. Garzik, in turn, has argued that the code is operating as intended in the absence of substantial hashing power.

It also remains to be seen whether or not some – if any – of the nodes in question see their application changed. Data from Bitnodes suggests that a number of them reside on hosting services from businesses like Amazon and Alibaba.

So unless that larger-than-1 MB block arrives, the nodes that are operating the application will have to preserve waiting.

Disclosure:&nbspCoinDesk is a subsidiary of Digital Currency Group, which helped organize the Segwit2x agreement.

Frozen clock image through Shutterstock

The leader in blockchain news, CoinDesk is an independent media outlet that strives for the highest journalistic standards and abides by a strict set of editorial policies. Have breaking news or a story tip to send to our journalists? Speak to us at news@coindesk.com.

Published at Fri, 17 Nov 2017 17:45:12 +0000

Tags