A tool to estimate time of protocol voting and protocol upgrade #12107
Labels
C-good-first-issue
Category: issues that are self-contained and easy for newcomers to work on.
T-dev-tools
Protocol upgrade in NEAR works as follows:
As an example:
201
is set to2024-01-02 12:00 UTC
#99
starts at2024-01-01 10:00 UTC
, the current protocol version is200
.#100
starts at2024-01-01 22:00 UTC
, the current protocol version is200
.#101
starts at2024-01-02 10:00 UTC
, the current protocol version is200
.2024-01-02 12:00 UTC
nodes start voting for protocol version201
, let's assume that 80% of stake voted for it.#102
starts at2024-01-02 22:00 UTC
, the current protocol version is200
.#103
starts at2024-01-03 10:00 UTC
, the current protocol version is201
.#104
starts at2024-01-03 22:00 UTC
, the current protocol version is201
.The protocol upgrade to version 201 happened at
2024-01-03 10:00 UTC
.(In the real world the numbers aren't that pretty because epochs aren't exactly 12 hours long)
In general we prefer protocol upgrades to happen during working hours of NEAR engineers, which is around 8-22 UTC, so that they can go and fix any problems that could arise because of the upgrade.
Because of that we try to set the voting dates to values which will cause the protocol upgrade to happen at the desired time.
It would be great to have a tool which:
Right now the process of estimating voting and upgrade dates is manual and a bit error prone.
Tasks
The text was updated successfully, but these errors were encountered: