Well the main thing about the Core plan is to do the Softfork part of this say six months in advance of the hardfork, that way you avoid any confusion at the time the hardfork activates, no period when exchanges are down ect. If the hardfork and softfork happen at the same time then you get none of the advantages of the way the Core team plan to do it, so its not really the same idea.Justus Ranvier said:I said that a majority of miners can ensure the success of a hard fork by simply agreeing to continue extending the large block chain even if the minority chain temporarily overtakes theirs. The mechanism via which they could accomplish that can accurately be described as a "soft fork" since it doesn't require any client participation.
That's where you jumped in and said that Core had planned to do that all along.
Out of interest, would you be happy to modify your idea such that the softfork element happens say six months earlier than the hardfork?
Justus Ranvier said:I also said that miners planning the fork and preparing users for it ahead of time should tell everyone not to consider the fork complete until the first >1MB generation output has matured (become spendable), which does not occur until it's 100 blocks old.
Why do we need this network downtime? There is already a solution to this as I explained. Is it 100 blocks old or a 100 block lead? The game theory here starts to get complicated. I would probably oppose such an idea.
Oh you mean like Bitcoin Classic? Yes my probabilities assume Bitcoin Classic. I agree with your sentiment in the description of Classic, but I would try not to be rude and call it the "stupidest possible implementation", a 51% activation threshold would have been worse. Gavin is an extremely intelligent and capable person, it is just that these issues are new and difficult and require careful discussion and considerationJustus Ranvier said:If the hard fork was done completely haphazardly, with no planning whatsoever and with the stupidest possible implementation then your probabilities are correct.