No2X > B2X: Segwit2 Fails to Fork

in bitcoin •  7 years ago 

No2X_B2X.png

Plenty of bugs and no nodes on the day the SegWit2 hard fork was expected to take place. When the New York Agreement was signed at Consensys 2017 last May,
the hard fork was set to occur at block 494784, which was reached today.

Unfortunately, SegWit2 nodes, such as btc1, were unable to fork and create a new currency, often called B2X. BTC1, for example, did not progress past block 494782. This failed to fork primarily because the SegWit2 base block at 494784 had to have a base-block larger that one megabyte. The SegWit2 fork had an error, however, that forced it to reject blocks less than one megabyte at block 494783, one block too soon. The SegWit2 fork coulnd not then progress to block 494784.

To add to the pain, the SegWit2 fork also prevented forking miners from mining a large enough block without manually adjusting their block weight settings. Miners propably did not know they needed to make this reset, although a patch has been released. Still, no SegWit2 blocks have been mined as far a I can tell, but that may change as word of the fix spreads. Even if some miners pick it up, it seems that the fork has failed completely from the looks of things.

Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE STEEM!