News for hackers. Stuff that matters.

A comment on Bitcoin – Potential Network Disruption on July 31st. Parent comment

Re:Bitcoin – Potential Network Disruption on July 31st by jpatokal on Thursday July 13, 2017 @01:11AM (#14758880)
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.)
[ Parent | on HN ]
Re:Bitcoin – Potential Network Disruption on July 31st by wyager on Thursday July 13, 2017 @02:10AM (#14759095)
There's currently 86.5% support.
[ Parent | on HN ]
Re:Bitcoin – Potential Network Disruption on July 31st by dekz on Thursday July 13, 2017 @02:52AM (#14759258)
That'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?

[ Parent | on HN ]
Re:Bitcoin – Potential Network Disruption on July 31st by awestroke on Thursday July 13, 2017 @03:04AM (#14759308)
> Segwit2x is still yet to have a working ...

https://github.com/btc1/bitcoin

> ... and tested implementation.

It will go online on the testnet tomorrow

[ Parent | on HN ]
Re:Bitcoin – Potential Network Disruption on July 31st by spiralx on Thursday July 13, 2017 @05:03AM (#14759808)
> 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.

[ Parent | on HN ]
Re:Bitcoin – Potential Network Disruption on July 31st by ilikechilis on Thursday July 13, 2017 @01:00PM (#14762943)
The 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

[ Parent | on HN ]