From 91fe7a86c47f04a2637283c667f348e317b5d1c3 Mon Sep 17 00:00:00 2001 From: Kevin Davis Date: Fri, 5 Jun 2020 19:27:12 -0400 Subject: [PATCH] fix: use halt-time --- contrib/kava-3/migration.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/contrib/kava-3/migration.md b/contrib/kava-3/migration.md index 742b562b..635e4142 100644 --- a/contrib/kava-3/migration.md +++ b/contrib/kava-3/migration.md @@ -26,7 +26,7 @@ In the event that the upgrade does not succeed, validators and operators must do Set your node to produce the final block of kava-2 at __13:00__ UTC June 10th, 2020. To restart your node with that stop time, ``` -kvd start --halt-height 1591794000 +kvd start --halt-time 1591794000 ``` 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. @@ -78,4 +78,4 @@ kvd start --halt-height 1591794000 ### Coordination -If the `kava-3` chain does not launch by June 10, 2020 at 16:00 UTC, the launch should be considered a failure. Validators should restore the state from `kava-2` and coordinate a relaunch. In the event of launch failure, coordination will occur in the [Kava discord](https://discord.com/invite/kQzh3Uv). \ No newline at end of file +If the `kava-3` chain does not launch by June 10, 2020 at 16:00 UTC, the launch should be considered a failure. Validators should restore the state from `kava-2` and coordinate a relaunch. In the event of launch failure, coordination will occur in the [Kava discord](https://discord.com/invite/kQzh3Uv).