> This document is provided to assist Chinese speaking validators upgrade, but might not be updated as fast, and might not be the most current version. When in doubt, consult the English version
> 本文档用于帮助说中文的验证节点升级，但可能不是最新的版本。如有疑问，请查阅英文版
## Software Version and Key Dates 软件版本和关键日期
- We will be upgrading from chain-id "kava-7" to chain-id "kava-8".
- The kava-7 chain will be shutdown with a `SoftwareUpgradeProposal` that activates at block height 1878509, which is approximately 13:00 UTC on August, 30 2021.
As a validator, performing the upgrade procedure on your consensus nodes carries a heightened risk of double-signing and being slashed. The most important piece of this procedure is verifying your software version and genesis file hash before starting your validator and signing.
The riskiest thing a validator can do is discover that they made a mistake and repeat the upgrade procedure again during the network startup. If you discover a mistake in the process, the best thing to do is wait for the network to start before correcting it. If the network is halted and you have started with a different genesis file than the expected one, seek advice from a Kava developer before resetting your validator.
Prior to exporting kava-7 state, validators are encouraged to take a full data snapshot at the export height before proceeding. Snap-shotting depends heavily on infrastructure, but generally this can be done by backing up the .kvd and .kvcli directories.
It is critically important to back-up the .kvd/data/priv_validator_state.json file after stopping your kvd process. This file is updated every block as your validator participates in consensus rounds. It is a critical file needed to prevent double-signing, in case the upgrade fails and the previous chain needs to be restarted.
In the event that the upgrade does not succeed, validators and operators must downgrade back to v0.14.2 of the Kava software and restore to their latest snapshot before restarting their nodes.
Kava Labs will submit a `SoftwareUpgradeProposal` that specifies the exact block _height_ at which the chain should shut down. This height will correspond to approximately 13:00 UTC on August 30th. Once the proposal passes, the chain will shutdown automatically at the specified height and does not require manual intervention by validators.
**The kava chain is expected to halt at 13:00 UTC, and restart with new software at 15:00 UTC August 30th. Do not stop your node and begin the upgrade before 13:00UTC on August 30th, or you may go offline and be unable to recover until after the upgrade!**
**kava 链预计将在 13:00 UTC 停止，并在 8 月 30 日 15:00 UTC 重新启动新版本。 8 月 30 日 13:00 UTC 之前不要提前停止您的节点并开始升级，否则您可能会下线，直到升级后才能恢复！**
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.
kvd validate-genesis genesis.json # should say it's valid 应该说它是合法的
jq -S -c -M '' genesis.json | shasum -a 256
# PLACEHOLDER
# Restart node with migrated genesis state 重新启动具有迁移的创世状态的节点
cp genesis.json ~/.kvd/config/genesis.json
kvd unsafe-reset-all
# Restart node - 重启节点
# ! Be sure to remove --halt-time flag if it is set in systemd/docker 如果在 systemd/docker 中设置了 --halt-time 标志，请删除它
kvd start
```
### Coordination 协调
If the kava-8 chain does not launch by August 30, 2021 at 19:00 UTC, the launch should be considered a failure and validators should refer to the [rollback](./rollback.md) instructions to restart the previous kava-7 chain. In the event of launch failure, coordination will occur in the [Kava discord](https://discord.com/invite/kQzh3Uv).
