Have configurable number of epochs for protocol upgrades #205
Comments
|
I would be happy to see 72/96-hours grace period, but reduce 80% figure to 51% to encourage more validators to upgrade in the given timeframe. Also can you clarify is it 80% of a total stake or number of validators, please. |
Yes. Please refer to https://nomicon.io/ChainSpec/Upgradability.html |
janewang
moved this from Incoming Requests (To Be Groomed)
to Backlog
in Node Experience Q3 2021
|
Here are suggested configurable epochs from validators:
|
janewang
moved this from Backlog (team committed to work on)
to In Development
in Node Q2 2022
near-bulldozer bot
pushed a commit
to near/nearcore
that referenced
this issue
Mar 4, 2022
…6309) See near/NEPs#205 This PR enables clients to extend the protocol upgrade window, but indirectly. This PR lets clients upgrade early but not announce the fact of the upgrade until a certain date in the future. Normal upgrades: * Clients will delay voting until a certain date. Emergency upgrades: * Voting for the new version starts immediately and a protocol upgrade becomes effective in 1-2 epochs.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently once 80% of the validators switch to a new protocol version, the upgrade happens in 2 epochs, which may not be sufficient for some validators to upgrade their nodes. At the same time, if there is an emergency upgrade to fix some critical vulnerability, we would like to upgrade to finish as fast as possible. Therefore, it may make sense to distinguish, for every protocol upgrade, whether it is urgent or standard and have different number of epochs between when the majority of validator switch to the new version and when the new protocol kicks in.
The text was updated successfully, but these errors were encountered: