-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] Try out migration extraction #177
Closed
Closed
Conversation
This file contains 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
* Revert to older substrate 064ca16f12e05d805ac38d302fe9258863a74852, accounts are migrating correctly * Up the version * Cargo version updates * Clean out v99 testnet, move chainspecs into binary * Fix module test imports
…tructure parameters so that they could be modified through democracy. (#161) Co-authored-by: remzrn <@>
…ies. (#165) * Updates substrate commit, still broken, needs to resolve compile errors * Updates to new fork commit * Updates * Adds missing type from update * Fix indentation * Fixes indentation elsewhere
* add migration.md to track the process * remove migration md (moved to issue #164) * WIP add signaling hasher migration and (failing) test * fix migration test * add voting hasher change test and fix migration * add WIP state grafting script * actually execute migration for voting pallet * use live chain for grafting and reformt code * use apopiak-migrations substrate branch * update grafting script to skip staking * remove berlin.json loading line * add mainnet-dev hybrid chainspec for migration testing * update Cargo.lock * add custom migration that orders balances and account migration correctly * update cargo.lock
* Ups to apopiak's upstream merge branch * Fixes module tests * Changes branch to time-travel
Add staking migration
…king Prime member selection (ElectionsPhragmen) migration #11
* change substrate branch to corresponding branch for this one * Updates lock file Co-authored-by: Drew Stone <drewstone329@gmail.com>
Maybe merge this into |
of course, thanks, will tweak tomorrow |
wrong base branch |
See #179 for the actual PR |
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 tries to extract migration logic out of substrate into separate crates.
Very prototypical, does not work, yet.
see paritytech/polkadot-sdk#353 for inspiration