Re-enable vested delegation migration + contract migration for fixing existing mistakes #4956
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 2 Skipped Deployments
|
jstuczyn
force-pushed
the
bugfix/vested-delegation-restoration
branch
from
e04829c to
1f089ca
Compare
octol
approved these changes
Oct 10, 2024
Contributor
Author
|
superseded by #4977 which removes the contract migration code as it's already been run |
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.
This PR does introduces two things to the mixnet contract:
MigrateMsg(which got very painstakingly determined by scraping our chain) it either adds additional tokens to existing delegations or, if somebody decided to undelegate everything, creates brand new delegation in that place.oh and there's plenty of unit tests for the both additions... not going to make the same mistake twice lol
This change is