Good to past time and now with the closeness of a possible hardfork in the Bitcoin network to only a few weeks of being a reality, the chances of avoiding the hard fork that has caused a stir in the market of cryptoneses have put the users against Clock since this Friday when it was not reached a protocol consensus to apply to the network.
On August 1, all the nodes of the Bitcoin or BIP # 148 improvement proposal will begin to reject any block that does not indicate their availability for SegWit (separate control) activation. In fact, this day the main Bitcoin chain could be divided if most users, in one way or another, do not activate SegWit through signaling indicated by the processing power (hashrate) of the nodes of the network; The last chance for current Bitcoin nodes to remain in the same chain would also be lost because SegWit and BIP # 148 were designed to be compatible with earlier versions of the protocol.
If a minority of SegWit users active through BIP # 148, the block string would be split, creating two cryptoactive. A division between the BIP # 148 nodes and the nodes that did not execute BIP # 148 would last at least until most of the hash power was joined to the enhanced chain by BIP # 148 or until the BIP # 148 chain is left Used by users who by then must have chosen another protocol update proposal.
Users now have three options to avoid this split: locking SegWit before August 1 through Bitcoin Core's trigger mechanism: specifically that 95% of the hash power signals support the update within a time of difficulty two weeks. Specifically, such a period of difficulty consists of 2,016 of these sequential blocks, which means that a minimum of 1,916 blocks should point to support. This would make if more than 100 blocks - at least 101 of them - do not indicate the support of SegWit In a difficult period ending before August 1, this BIP # 148 deadline is lost.
The last difficult period to finish before August 1 began on Friday. And therefore, the first day and a half in this period of difficulty, only about half of the blocks noted support for SegWit. This means that the threshold of 101 blocks without signaling support has been reached.
Undoubtedly, the difficulty of achieving BIP # 148 activation was high. For now, a large majority of miners indicate that they will activate SegWit via BIP # 91 instead. This will be the next deadline for BIP # 148.
Two important trends are outlined to prevent a mild UASF fork. The first one is called SegWit2x, which is intended to activate SegWit through BIP code # 91. The other is known as the Bitcoin ABC implementation, and is a contingency plan that will be implemented if BIP # 148 is activated on August 1 or, In other words, if BIP # 91 is not activated on that date.!