This hard-fork is expected to include features which are currently being discussed within technical communities, including an increase in the non-witness data to be around 2 MB, with the total size no more than 4 MB, and will only be adopted with broad support across the entire Bitcoin community.
SegWit is expected to be released in April 2016.
The code for the hard-fork will therefore be available by July 2016.
If there is strong community support, the hard-fork activation will likely happen around July 2017.
SegWit is expected to be released in April 2016.
The code for the hard-fork will therefore be available by July 2016.
If there is strong community support, the hard-fork activation will likely happen around July 2017.
So if someone started a purely classic/xt pool and got more than 5% hashing power...
Exactly. If someone ran a purely classic/xt pool and got more than 5% hashing power they should be able to single-handedly prevent any future hard fork of the bitcoin consensus protocol.
Why do you think there has been no changes to TCP/IP in the last 20 years? Why do you think IPV6 still has less than 1% implementation?
Changes to consensus protocol are not easy, nor should they be.
Nor am I.....
Muahahahahahaaaaa!!!!!!