fix(drive)!: invalid protocol version is using to deserialize state - #1679
Merged
Conversation
QuantumExplorer
requested changes
Jan 22, 2024
QuantumExplorer
requested changes
Jan 25, 2024
QuantumExplorer
requested changes
Jan 25, 2024
QuantumExplorer
approved these changes
Jan 26, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue being fixed or feature implemented
Currently we use latest protocol version to deserialise state. It works until current protocol version == latest protocol version, which obviously won't be always the case.
What was done?
How Has This Been Tested?
None
Breaking Changes
We store protocol version on init chain so previously created state won't be valid
Checklist:
For repository code-owners and collaborators only