Published updated code suggestions for scaling bitcoin Segwit2x

Previously supported large number of miners and companies offer on the scaling of network bitcoin Segwit2x today moves to a new level. As confirmed by the co-founder of the Bloq and the lead developer Segwit2x Jeff garzik's, Friday, June 30, we will post an updated Protocol code, according to CoinDesk.

Recall signaling in support SegWit2x on the part of the miners began on June 19, and in fact, during the day reached the required support threshold of 80% .

The last two weeks codebase SegWit2x was in the mode of alpha testing.According to garzik's, the updated code is intended to fix previously identified bugs and to help in its further optimization.

In the opinion of a significant part of the bitcoin industry, SegWit2x should be seen as a compromise solution to the protracted discussions about the scalability. The proposal involves the activation of the Protocol Segregated Witness on the part of the miners, followed by increasing the block size to 2Mb.

At the same time we cannot deny the fact that at least a significant portion of the bitcoin community is against SegWit2x, calling him not only too hasty and imperfect from a technical point of view, but insisting that the proposal was the result of backroom agreements major players in the market. Alternatively, the solution UASF (activated by user softpark – BIP148), which also activates Segregated Witness, but not at the expense of the efforts of the miners, and through the support of the holders of nod.

At what level of controversy out of the discussion about scaling bitcoin, wholly says the incident on Thursday, June 29, verbal sparring on Twitter between the head of the Digital Currency Group is Barry Silbert (camp SegWit2x) and President of the International Blockchain Real Estate Association Ragnar Lifthrasir, who is an ardent supporter of UASF:

In his initial tweet Liftrasir refers to businesses, urging them to pay attention to that if Digital Currency Group is one of their investors, they should remember that SegWit2x may be potential unsafe decision that can have a negative impact on their own business and bitcoin in General.

The response of Silbert was the same and the gist of it is that his organization Digital Currency Group supports entrepreneurs who must remember that the UASF can be a unsafe solution can adversely affect both their business and bitcoin in General.

Meanwhile, with more stringent statement was made by the crypto analyst Tone Weiss. According to him, "Barry Silbert becomes a problem for the ecosystem of bitcoin", but in the future he, like the rest [apparently, supporters SegWit2x – ed.] will be ignored.

Let's remind, that Barry Silbert acted as the mastermind behind SegWit2x agreement which was signed in may in new York.

However, as CoinDesk notes, publicly available information about testing SegWit2x still very small. According to involved in this process, the involved companies have tested the Protocol work in testnet5, as well as in the so-called "tap", which gives the test coins.

Among those who participated in testing and contributing to the development of the Protocol, the magazine says companies like Abra, Bitfury, Blockchain, BTCC, OpenBazaar, and Purse Xapo. Visit SegWit2x on GitHub, you can, for example, to see what the technical Director Purse Christopher Jeffrey identified and fixed a few bugs, while others suggested different ideas.

At the same time, some companies are reluctant to share information about their participation in testing SegWit2x.

Anyway, the miners and the company apparently intend to actively promote this solution. Now, after the release of the beta version, the next step would be to install software (July 14) and July 21 to begin an active signaling process to support SegWit2x.

Activation of the Protocol will in any case mean the activation of Segregated Witness, however, remains a lot of questions about how decentralized is bitcoin in such a scenario. As yet no clear answers of a technical nature relative to the alleged hard forks network, which should increase the block size.

ForkLog continues to keep abreast of events. Subscribe to our newsletter