On a more promising note, I have been testing code for another hardfork. This code is generating the desired effect and should prevent these unintentional forks from forming. My plan is to big bang and hardfork the network again. If testing continues to be favorable, this will occur this weekend. I have already made exchanges aware of this plan and its possible execution this weekend. Of course, more details to come.
Hi Steven,
Based on the network's adoption of v1.4.2.0 and based on those peers which still run v1.3.0.0, we know it took more than 2.5 weeks to see greater than 50% of the users install v1.4.2.0.
To ensure a successful launch of the proposed fork, it would be prudent to select a block height at least 2.5 weeks in the future and have the new client trigger the new network rules at the specified height.
This will permit us to release the new client as soon as the time is right yet also provide enough time to monitor the number of peers who have adopted it so we can spread the message more aggressively if needed.
Also, what specifically do you mean by "big bang and hardfork"? I understand hardfork but do not yet see commits describing the big bang reference.
https://github.com/EverGreenCoinDev/EverGreenCoin/commits/masterBest Regards,
-Chicago
Hi Chicago,
We had gone through this in June with the PoW block time hardfork. This is the reason we still find v1.3 wallets and not v1.1 wallets, a protocol upgrade to the network forced the upgrade to v1.3. Selecting a point in time the old protocol version stops, all seednodes are upgraded to the new protocol version, users upgrade to the new protocol version then or in the future, and the blockchain continues. This is what I mean by 'big bang'.
Protocol version cannot be changed while in use. We can't create a condition that says at 'this' block height, start using a new protocol version. A protocol version upgrade must be 'big bang', all or nothing.
When you think about it, and for reasons like you stated including people's reluctancey to upgrade, 'big bang' is the only proper way to implement a hardfork. The hardfork itself will happen at a later point in time on the new protocol version blockchain and, yes, with the condition test of at 'this' block introduce a new PoS block difficulty mininum. Thus not necessarily slowing down the network, but preventing it from going
so fast concensus is not formed before nodes start building on to, what they think is, the correct blockchain height.
We can't have old wallets introducing new blocks that do not meet the new validity rules after the hardfork and we can't have other old wallets verifying those blocks after the hardfork. Big bang (protocol upgrade) is the only way for us to stop that. Also, the source code not being made publically available until that time. I of course can private repo the change and review with any community member that wishes to see them.
Giving forewarning is not beneficial in any other way than letting people know to not to try and move any coins after the time of the big bang until they upgrade. But they will not be able to upgrade until the time of the big bang when new wallets, containing the protocol upgrade and the forthcoming hardfork code, are made available.
People that do not have the time to upgrade, no worries, don't upgrade until you have time.
But you will have to resync
if you run the old version past the time of the big bang. If you do not run the old version past the time of big bang, you can upgrade at your convenience. But you will not be able to stake or move coins until you do upgrade.
So, why the urgency? The issues are holding the project back and for that I sincerely apologize and wish to change. Not only does it eat away at any time for further development, we are at risk of losing services. It is no secret I have been giving great effort to make EGC user friendly to new comers. The tasks of having to verify blockchains and resyncing defeats those efforts. The sooner we can put them behind us, the better.