Litecoin’s Charlie Lee: GBMiners Has Stopped Signaling For SegWit2x Bitcoin Hard Fork
On October 27, Litecoin creator and former Coinbase executive Charlie Lee revealed that GBMiners, a major mining pool operator, has stopped signaling for the
SegWit2x hard fork expected to occur in mid-November.
Hashrate Support For SegWit2x is Declining
Earlier this month, F2Pool, another leading mining pool operator with 14 percent of the global bitcoin hashrate, stopped signaling for the SegWit2x hard fork. According to the NYA SegWit2x agreement established at the Consensus 2017 event, F2Pool signed the proposal along with other miners that represent 83.28 percent of global bitcoin hashing power.
With the withdrawal of support from F2Pool and GBMiners, the hashrate support for the SegWit2x hard fork in November has declined from 83.28 percent to around 66 percent. More to that, as Luke Parker of BraveNewCoin stated, many individual miners have started to move from SegWit2x supporting mining pools to Slush Pool, which grants individual miners to express support for either SegWit2x or the original Bitcoin blockchain.
“Further, over 3,000 miners moved from other pools to join the Slush Pool last week, which is the only major pool that lets individual miners decide for themselves which fork they’d like to support. The move saw Slush Pool rise to become the 5th largest pool with 8.5% of the total Bitcoin hashrate — and only 6% of its miners are signaling for Segwit2x, with 75% signaling for the legacy chain,” wrote Parker.
Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:
https://www.cryptocoinsnews.com/charlie-lee-gbminers-has-stopped-signaling-for-segwit2x-hard-fork/
Congratulations @hasnainjutt! You have completed some achievement on Steemit and have been rewarded with new badge(s) :
Award for the number of upvotes
Click on any badge to view your own Board of Honor on SteemitBoard.
For more information about SteemitBoard, click here
If you no longer want to receive notifications, reply to this comment with the word
STOP