Segwit2x: Updated Code to be Released Tomorrow, Will This Address the Issues?

View this thread on: d.buzz | hive.blog | peakd.com | ecency.com
·@sflaherty·
0.000 HBD
Segwit2x: Updated Code to be Released Tomorrow, Will This Address the Issues?
![18.3.7.png](https://steemitimages.com/DQmW1rUzUrhphF3d6UZPEYUDoB2hP8S5YKioXsz15HW1MVa/18.3.7.png)

## <center>Lead Segwit2x Dev Announces Better Code for Possible Better Results</center>
#
Segwit2x lead developer Jeff Garzik announced today that come tomorrow Friday, June 30th, an updated code will be set out to to testers which he claims to address many of the concerns and issues with the last testing release of Segwit2x. 

This proposed fix to the Segwit fix is still a bit controversial at the moment. Many miner camps have found love for Segwit2x but many Bitcoin Core developers are on the fence still about this being the godsend that they deem this to be. Segwit2x will undergo more testing but if consensus does form in the majority its expected an early activation before the August date for the user activated soft fork (UASF). Segwit2x is honored by the miners due to its increase to the 2mb block size they have fought for all along.

## <center> Testing With Fake Coins in Testnet5</center>
#
Its publicly known that a new testnet has been created for this testing phase on Segwit2x. The new testnet has been called **testnet5** and the concept for testing is through a faucet system that spits out fake coins so developers can iron out and make sure all is going according to plans with this code.

During the last 2 week phase of testing a bunch of bugs have been found and corrected already. A few buggy issues have been discovered and work arounds have been proposed by GitHub developers in on the action. So far the testing consensus is in high hopes that this soon to be released code will limit the bug issues presently seen.

![mining-farm.jpg](https://steemitimages.com/DQmPiuhbNCJEUxQcU6JMuoN89MbM7jFcaNYqpE5Ci3h9Qwm/mining-farm.jpg)

## <center>Skeptical Worries of Centralization Growing Inside of Bitcoin</center>
#
There are hair rising concerns at the moment with the testing going on with Segwit2x due to the small amount of companies in on the action with the code testing and bug fixing. The testing is done through an invite only based Slack and many questions are arising about the lack of replies being put out there by outsiders to find out what is going on with the status of the testing. 

Already there is a serious concern by users about the mining camps and how they seem to stall progress in many decentralized ways. Right now it appears this testing is very centrally closed off to the public which goes highly against the open source nature of what Bitcoin Core has always stood for. More concerns are running around due to the speed that the mining camps want to run this, calling for a July activation of this Segwit2x which many feel could cause many issues with a Bitcoin hard fork split and an outcome of 2 coins which no one wants.

Mining pools have with 80% hashrate of the whole Bitcoin stadium have said they are on board for Segwit2x, with plans for a July 31 no later activation. The trick is if users do not upgrade their software to this forced hard fork, we very may well find a division in our beloved coin and a lot of future headaches.

Bitcoin Core members are growing more and more skeptical of the tactics on this, Bitcoin users are also growing tired of the back and forth mess due to this unfolding drama. To me, main issue here is get this to stay decentralized and make sure the transaction fees and transaction backlog issues are fixed. I guess its a wait and see because as a user our hands are literally tied to hope and a dream that these two camps find an eye to eye solution for all.

Keep up on this stuff, most important as a user that you secure your Bitcoins in a safe wallet and we ride out the storm informed.

#### ~sflaherty
#
### Follow me @sflaherty
👍 , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,