A good summary of the state of things, and being covert in the open.:
http://www.coindesk.com/coindesk-explainer-bitcoin-bip-91-implements-segwit-avoiding-split/
It's like there is only segwit activation and idiots just making it difficult.
http://www.coindesk.com/coindesk-explainer-bitcoin-bip-91-implements-segwit-avoiding-split/
Disclosure: CoinDesk is a subsidiary of Digital Currency Group, which helped organize the Segwit2x agreement. - and mentions nothing about the 2X being the reason the 2MB Hard fork being the reason for segwit2X!SegWit2x was introduced during CoinDesk's Consensus 2017 conference in May. Based on a fork of the Bitcoin Core software client called BTC1, SegWit2x seeks to both implement SegWit and raise the block size limit.
BIP 141: Introduced in November 2016, BIP 141 is the original plan for activating SegWit. [with no raise to the block size limit.]
BIP 91 uses the same BIP 9 soft fork deployment method as BIP 141, but with a few key differences:
So, once that 80% threshold is reached, BIP 91 locks in, and another 336 blocks later, it activates.
- Miners signal with "bit 4," as opposed to "bit 1"
- Activation only requires 80% as opposed to 95% of hash power support
- The activation window is 336 blocks, as opposed to 2,016.
At that point, BIP 141 is enforced using the same technique as BIP 148:
But if BIP 91 is almost identical to BIP 141, why didn't miners signal support for the latter? ...
So, to get around that, BIP 91 employs a clever trick. Rather than change the existing SegWit activation logic, it uses a secondary bit to signal mandatory enforcement of the original bit.
In many ways, BIP 91 can be read as an effort to front-run the BIP 148 proposal, thus removing the potential of creating two rival bitcoin blockchains, each with competing assets.
It's like there is only segwit activation and idiots just making it difficult.