Bitcoin SegWit-2X Almost Approved

in bitcoin •  8 years ago  (edited)

80% of Bitcoin hash power agrees with SegWit-2X

bitcoin-mining-d01.jpg

When SegWit-2X was first announced, users looked at it with reluctance. Almost nobody believed to find support at 80% of the network's hash power. The last pool from which approval is expected is BTCC, and the thoughts on SegWit-2X are somewhat positive.


In other news, it is true that discussions about scalability have lasted for too long. A solution has to be found and implemented as quickly as possible. SegWit-2X seems to be a way of solving that. According to Coin.dance website, 76.4% of miners agree with SegWit-2X. It's just a matter of time until this percentage reaches 80%. Once this target is reached, SegWit-2X will be activated.

SegWit-2X is on the right track:

  • BTCC is the last pool to expect to join SegWit-2X. Many miners were concerned that the pool has dropped for hours during the day yesterday. Apparently, owners have made some major changes to support the SegWit-2X deployment.
  • Once the BTCC agreement is reached, the 80% threshold will be reached, which is excellent news for all the fans of the update.
  • In addition, this solution to scalability is also economically beneficial. A large number of companies are already on the SegWit-2X side. Just keep the time until this update will be enabled on the network.

What is certain is that the following weeks will be particularly interesting for Bitcoin and for the entire community.




Thank you for your attention!

More crypto-news coming soon!

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!
Sort Order:  

Do you have a link to the uptake?

  ·  8 years ago (edited)

I gathered the information from multiple sources when I wrote the article. Unfortunately, I no longer have the links.

The code for segit 2x is not open source and no one from Bitcoin core has signed off on this. There is a reason 80% was picked. This seems like a trojan horse

I do not think so, it's meant to solve scaling issues.