x-crisis-skip-assert-invariantsCLI flag to the
5,713,000. At the time of writing, and at current block times (around 5.5s/block), this block height corresponds approximately to
UTC. This date/time is approximate as blocks are not generated at a constant interval.
fxcore. This is because an in-place migration of state will take place, i.e., this upgrade does not export any state.
Minimum system requirements have an upgrade by 2 Cores and 4GB
.fxcore/data/priv_validator_state.jsonfile after stopping the fxcore 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.
.jsonfile so they will be able to recover their validators in case the upgrade fails. More on the validator recovery process.
A detailed upgrade failure handling tutorial will be added later
There is no particular need to restore a state snapshot prior to the upgrade height, unless specifically directed by core fxCore team.
#validators-verified channelto create and execute a contingency plan. Likely this will be an emergency release with fixes or the recommendation to consider the upgrade aborted and revert back to the previous release.