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

Abort if binary too new #4

Merged
merged 4 commits into from
Aug 27, 2019

Conversation

ethanfrey
Copy link

If we are running a version of the software before it is triggered, we will have upgrade handlers registered in code, which have not been marked done in the database. If we detect this, abort immediately to prevent people from upgrading too early and breaking consensus

@ethanfrey ethanfrey requested a review from aaronc August 27, 2019 12:10
x/upgrade/keeper.go Outdated Show resolved Hide resolved
@ethanfrey ethanfrey force-pushed the frey/abort-if-too-new branch from c1c17f3 to c572cc3 Compare August 27, 2019 13:32
@ethanfrey
Copy link
Author

Rebased on merged PR #3
And addressed change requests.

Please re-review

@ethanfrey ethanfrey merged commit 281da88 into regen-network/upgrade-module-v0.4 Aug 27, 2019
@ethanfrey ethanfrey deleted the frey/abort-if-too-new branch August 27, 2019 14:28
@ethanfrey ethanfrey changed the title Abort if too newa Abort if binary too new Aug 27, 2019
sahith-narahari pushed a commit that referenced this pull request Dec 16, 2019
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

Successfully merging this pull request may close these issues.

2 participants