[pallet-balances] Add SimpleStorageUpdate to migrate balances without any additional inactive tracks#6313
Closed
dmitrylavrenov wants to merge 1 commit intoparitytech:masterfrom
Conversation
dmitrylavrenov
force-pushed
the
dl-hmnd-balances-migrations-simple-storage-update
branch
from
ac9609d to
382a753
Compare
dmitrylavrenov
deleted the
dl-hmnd-balances-migrations-simple-storage-update
branch
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
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.
During work on humanode-network/humanode#940 in our humanode codebase to update substrate related dependencies to
polkadot-v0.9.43we've faced some migration errors related topallet-balancesas the pallet's code hasStorageVersion = 1but our mainnet balanceson_chain_versionis still equal to 0.We've researched current existing migration options like
MigrateToTrackInactive,MigrateManyToTrackInactiveandResetInactive. So, there are no any options to do migration without including additional tracks of inactive funds. In our codebase we use own implementation to track inactive funds. As a result, it would great to have an option to do storage version update without doing additional inactive related stuff.