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

Bech32 PubKey: use protobuf in slashing keeper #7979

Merged
merged 4 commits into from
Nov 20, 2020

Conversation

robert-zaremba
Copy link
Collaborator

@robert-zaremba robert-zaremba commented Nov 19, 2020

Description

x/slashing keeper was not migrated to use protobuf serialization for pub keys.

This change breaks the state machine and thus requires a migration for update. That being said we don't need to write new migration, because this keeper data is not a part genesis object (it's generated through processing other genesis messages).

Related to: #7447


Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

  • Targeted PR against correct branch (see CONTRIBUTING.md)
  • Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
  • Code follows the module structure standards.
  • Wrote unit and integration tests
  • Updated relevant documentation (docs/) or specification (x/<module>/spec/)
  • Added relevant godoc comments.
  • Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
  • Re-reviewed Files changed in the Github PR explorer
  • Review Codecov Report in the comment section below once CI passes

@codecov
Copy link

codecov bot commented Nov 19, 2020

Codecov Report

Merging #7979 (07cfed4) into master (fcb6c33) will increase coverage by 0.00%.
The diff coverage is 75.00%.

@@           Coverage Diff           @@
##           master    #7979   +/-   ##
=======================================
  Coverage   61.56%   61.57%           
=======================================
  Files         601      601           
  Lines       34446    34443    -3     
=======================================
- Hits        21208    21207    -1     
+ Misses      11054    11053    -1     
+ Partials     2184     2183    -1     

Copy link
Contributor

@amaury1093 amaury1093 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm. Would be good to add a changelog entry under "State Machine Breaking"

x/slashing/keeper/keeper.go Show resolved Hide resolved
@amaury1093 amaury1093 added the T: State Machine Breaking State machine breaking changes (impacts consensus). label Nov 19, 2020
@robert-zaremba
Copy link
Collaborator Author

Updated the changelog

Copy link
Contributor

@alexanderbez alexanderbez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK. I presume we'll need to handle the stargate migration scripts for these changes?

@amaury1093
Copy link
Contributor

@alexanderbez I don't think so, as Robert wrote:

That being said we don't need to write new migration, because this keeper data is not a part genesis object

@alexanderbez
Copy link
Contributor

Got it 👍 (note, on a live upgrade I believe it would)

@robert-zaremba robert-zaremba removed the T: State Machine Breaking State machine breaking changes (impacts consensus). label Nov 19, 2020
@robert-zaremba robert-zaremba added the A:automerge Automatically merge PR once all prerequisites pass. label Nov 20, 2020
@robert-zaremba robert-zaremba merged commit a054da8 into master Nov 20, 2020
@robert-zaremba robert-zaremba deleted the robert/bech32-pubkey-slashing branch November 20, 2020 11:58
@amaury1093 amaury1093 mentioned this pull request Nov 25, 2020
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A:automerge Automatically merge PR once all prerequisites pass. C:x/slashing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants