Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add info to 'upgrade instructions' wiki: https://github.com/cosmos/gaia/wiki/Cosmos-Hub-2-Upgrade #116

Closed
gavinly opened this issue Aug 30, 2019 · 3 comments

Comments

@gavinly
Copy link
Contributor

gavinly commented Aug 30, 2019

@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

@alexanderbez
Copy link
Contributor

@gavinly I've added two entries on recovery and getting a block's UTC timestamp. Please review.

@gavinly
Copy link
Contributor Author

gavinly commented Aug 30, 2019

Looks good to me, thank you! @zmanian could you please review?

@alexanderbez
Copy link
Contributor

Will close for now. @zmanian feel free to make any adjustments 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants