chore: undelegate from all validators during migration #4
+251
−776
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
chatton
commented
Nov 26, 2025
| cache-from: type=gha | ||
| cache-to: type=gha,mode=max,ignore-error=true | ||
|
|
||
| docker-build-evolve-image: |
Collaborator
Author
There was a problem hiding this comment.
I just removed the evolve specific workflows that don't matter for this fork
chatton
changed the title
julienrbrt
reviewed
Nov 26, 2025
julienrbrt
approved these changes
Nov 27, 2025
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 updates the migration manager to correctly undelegate all tokens from the final validator.
The tokens are undelegated in the final step of the migration, and a single validator with a power if 1 is returned in the validator updates.
In order for IBC to function properly after the upgrade, you must backfill
MsgClientUpdates at all heights in which there was a power transition, otherwise relayers will not work. The E2E test was updated to do this.This means that AFTER the migration has occurred, you must start at the
trusted_heightgo to themigration_height+ 30.This must be done for all counter party chains, in this test we just have one.
Hermes can do this with the command
hermes update client --host-chain <counterparty-chain-id> --client <client-id> --height x