its just the hardfork for MN payments that has a delayed activation for either waiting for a certain pools compliance % or waiting for a certain time period, if one of those two conditions is met the
hardfork will be activated. This methode is also known as the spork update methode. The activation will be issued by Evan and then the hardfork will be active, forcing the mining pools to be on the right
darkcoin version or to have their mining efforts (on the wrong darkcoin version) rejected by the network.
We are using the spork methode for some time now, i dont understand why yr so bothered with it all of a sudden.. it gives the pools and the users some time to prepare and its more gracious then
forcing a hardfork down everyone's throat on short notice. The update methode is perhaps in a small number of hands (centralisation) but thats with all coins, even Bitcoin.
The lead developer is both in charge and has the responsibility over the coin he is developing, some times the lead developer operates alone.. sometimes he forms a team .. but it will still be a few experienced
people developing the code, or in this case flipping the switch.
hardfork will be activated. This methode is also known as the spork update methode. The activation will be issued by Evan and then the hardfork will be active, forcing the mining pools to be on the right
darkcoin version or to have their mining efforts (on the wrong darkcoin version) rejected by the network.
We are using the spork methode for some time now, i dont understand why yr so bothered with it all of a sudden.. it gives the pools and the users some time to prepare and its more gracious then
forcing a hardfork down everyone's throat on short notice. The update methode is perhaps in a small number of hands (centralisation) but thats with all coins, even Bitcoin.
The lead developer is both in charge and has the responsibility over the coin he is developing, some times the lead developer operates alone.. sometimes he forms a team .. but it will still be a few experienced
people developing the code, or in this case flipping the switch.
My assumption was always that it is part of all the users to update to the new version, and that's it.
Everything else (grace period, automatically going hardfork, etc.) is in the code itself.
So I think I just get confused by all those gifs and all those phrasings like "it's in evans hands" and "the activation will be issued by evan" etc...
He doesn't trigger anything at all.
It's just that he creates a new version and it's the people who have to update and then the spork code in the new version waits for a period / formula before going hardfork.
Evan triggers nothing, he just creates new versions and people have to follow.
So again, I think everything is clear if explained like that, it's just that how people depict it or make it sound like is confusing sometimes, especially to newcomers.
I need a coffee.
Case closed.
