wip: introduce vote-state-v5 #490
Draft
Conversation
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
akhi3030
force-pushed
the
akhi3030/vote-state-v5
branch
from
620f8d0 to
d9854da
Compare
akhi3030
force-pushed
the
akhi3030/vote-state-v5
branch
from
d9854da to
b2ab379
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Proposal for how to update vote state so that it supports both tower and alpenglow vote rewards.
Compared to
VoteStateV4:If it helps with migration, we do not have to introduce new structs and just add the new field needed for alpenglow at the bottom of
VoteStateV5.Assuming that after migration to alpenglow, we still need to finish paying tower rewards so both states are accessible at the same time.