You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@alexanderbez, we'll want instructions for validators to obtain the timestamp from the target export block. I'd like to add info necessary for a recovery scenario to the instructions wiki. @zmanian please let me know if this looks correct or not. Here are my requests:
In the event that a validator determines that the cosmoshub-3 chain is unlikely to start, or if export block time + 6 hours has elapsed without block generation, validators must resume signing on cosmoshub-2.
Governance procedures on the cosmoshub-2 chain will then be used to determine a future course of action for the network. // Create this as a new subsection
The text was updated successfully, but these errors were encountered:
@alexanderbez, we'll want instructions for validators to obtain the timestamp from the target export block. I'd like to add info necessary for a recovery scenario to the instructions wiki. @zmanian please let me know if this looks correct or not. Here are my requests:
During the upgrade process, each validator must preserve a snapshot of the node state of the target export block height to preserve recovery of their validator and sentry nodes to the cosmoshub-2 chain. // Add this to https://github.com/cosmos/gaia/wiki/Cosmos-Hub-2-Upgrade#upgrade-procedure
Recovery Scenario
In the event that a validator determines that the cosmoshub-3 chain is unlikely to start, or if export block time + 6 hours has elapsed without block generation, validators must resume signing on cosmoshub-2.
Governance procedures on the cosmoshub-2 chain will then be used to determine a future course of action for the network. // Create this as a new subsection
The text was updated successfully, but these errors were encountered: