smeb_y/0g-chain
1
0
Fork 0
mirror of https://github.com/0glabs/0g-chain.git synced 2024-12-26 08:15:19 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

update kava-5.1 migration guide

Browse Source
This commit is contained in:
karzak 2021-03-26 08:57:28 -06:00
parent 54c0793ced
commit b80c18506e
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
migrate/v0_14/migrate.md
View File

@ -4,8 +4,8 @@
* We will be upgrading from chain-id "kava-6" to chain-id "kava-5.1". This is to keep the features in our roadmap aligned with the features on mainnet going forward. * We will be upgrading from chain-id "kava-6" to chain-id "kava-5.1". This is to keep the features in our roadmap aligned with the features on mainnet going forward.
* The version of Kava for kava-5.1 is v0.14.0 * The version of Kava for kava-5.1 is v0.14.0
* Kava-6 validators should prepare to shutdown their nodes March 24th, 2021 at 13:00 UTC by setting `--halt-time` to `1616590800` * Kava-6 validators should prepare to shutdown their nodes March 31st, 2021 at 13:00 UTC by setting `--halt-time` to `1617195600`
* Kava-5.1 genesis time is set to March 24th, 2021 at 15:00 UTC * Kava-5.1 genesis time is set to March 31st, 2021 at 15:00 UTC
* The version of cosmos-sdk for kava-5.1 is v0.39.2 * The version of cosmos-sdk for kava-5.1 is v0.39.2
* The version of tendermint for kava-5.1 v0.33.9 * The version of tendermint for kava-5.1 v0.33.9
* The minimum version of golang for kava-5.1 is 1.13+, 1.15+ has been tested and is recommended. * The minimum version of golang for kava-5.1 is 1.13+, 1.15+ has been tested and is recommended.
@ -28,17 +28,17 @@ In the event that the upgrade does not succeed, validators and operators must do
### Before the upgrade ### Before the upgrade
Set your node to produce the final block of kava-6 at __13:00__ UTC March 24th, 2021. To restart your node with that stop time, Set your node to produce the final block of kava-6 at __13:00__ UTC March 31st, 2021. To restart your node with that stop time,
```sh ```sh
kvd start --halt-time 1616590800 kvd start --halt-time 1617195600
``` ```
You can safely set the halt-time flag at any time. You can safely set the halt-time flag at any time.
### On the day of the upgrade ### On the day of the upgrade
__The kava chain is expected to halt at 13:00 UTC, and restart with new software at 15:00 UTC March 24th. Do not stop your node and begin the upgrade before 13:00UTC on March 24th, or you may go offline and be unable to recover until after the upgrade!__ __The kava chain is expected to halt at 13:00 UTC, and restart with new software at 15:00 UTC March 31st. Do not stop your node and begin the upgrade before 13:00UTC on March 31st, or you may go offline and be unable to recover until after the upgrade!__
Kava developers will update this PR with the final block number when it is reached. __Make sure the kvd process is stopped before proceeding and that you have backed up your validator__. Failure to backup your validator could make it impossible to restart your node if the upgrade fails. Kava developers will update this PR with the final block number when it is reached. __Make sure the kvd process is stopped before proceeding and that you have backed up your validator__. Failure to backup your validator could make it impossible to restart your node if the upgrade fails.
@ -88,4 +88,4 @@ __Note:__ This can take a while!
### Coordination ### Coordination
If the kava-5.1 chain does not launch by March 24, 2021 at 17:00 UTC, the launch should be considered a failure and validators should refer to the [rollback]("./rollback.md") instructions to restart the previous kava-6 chain. In the event of launch failure, coordination will occur in the [Kava discord](https://discord.com/invite/kQzh3Uv). If the kava-5.1 chain does not launch by March 31, 2021 at 17:00 UTC, the launch should be considered a failure and validators should refer to the [rollback]("./rollback.md") instructions to restart the previous kava-6 chain. In the event of launch failure, coordination will occur in the [Kava discord](https://discord.com/invite/kQzh3Uv).