3 ms·
Unlike the UASF timebomb, SegWit2x won't activate unless there's 80%+ support, so it's not going to trigger a fork. (Well, technically it will, but if activated
by jpatokal 9y ago
Unlike the UASF timebomb, SegWit2x won't activate unless there's 80%+ support, so it's not going to trigger a fork. (Well, technically it will, but if activated the non-SegWit2x rump will quickly be reduced to irrelevance.)
- wyager 9y agoThere's currently 86.5% support.
- dekz 9y agoThat's 86.5% miners signalling to signal support. Segwit2x is still yet to have a working and tested implementation. Would you support something which has not been fundamentally tested?
- awestroke 9y ago> Segwit2x is still yet to have a working ... https://github.com/btc1/bitcoin https://github.com/btc1/bitcoin > ... and tested implementation. It will go online on the testnet tomorrow
- spiralx 9y ago> It will go online on the testnet tomorrow It seems rather premature to call it working before it gets properly tested. And three weeks is a woefully short time to test something like this, fix any issues that are found, and then re-test.
- ilikechilis 9y agoThe testnet is already online since a few weeks now. But according to the segwit2x timeline this step should come tomorrow if they are still on track: July 14 - Agreement Participants Install and Test Milestone