Upgrade substrate to v30 #660
Merged
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
surangap
force-pushed
the
feat/substrate-v30
branch
from
5873954
to
03145e6
Compare
|
Migration
|
surangap
force-pushed
the
feat/substrate-v30
branch
from
61409ca
to
636b7ab
Compare
surangap
force-pushed
the
feat/substrate-v30
branch
from
ccff78c
to
1b068aa
Compare
surangap
force-pushed
the
feat/substrate-v30
branch
2 times, most recently
from
6671bed
to
491848a
Compare
|
The bulk of the changes look good. I have one part I have to come back to and look at, then should be good to go |
JasonTulp
approved these changes
Aug 24, 2023
surangap
force-pushed
the
feat/substrate-v30
branch
from
aad4121
to
a81186a
Compare
* Add pallet-preimage * Update pallet-scheduler to use locally generated weight file. * Update pallet-preimage to use locally generated weights.
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.
Upgrades substrate version from
polkadot-v0.9.27topolkadot-v0.9.30Migrations
Stakingpallet is inV7_0_0. need to bring it up to date with v27. i.eV10_0_0Upto v27 - need to update the storage version to v10
Staking
VoterList.We have already populated values in porcini/root
and this is an expensive operation
VoterListas well.we have validators + nominators in porcini
root only have validators
EarliestUnappliedSlash.UnappliedSlashes is empty for porcini/root
TransactionPayment
V1Ancient. there has been a PR for V2. We are already in V2. But the storage version gives the default valueV1Ancient. maybe we should update the version for the sake of future migrationsAfter v27 - migration required
Staking
We already have it under the prefix "VoterList", and no change
can run the migration with the same name to update the storage version
HistoryDepth.Move from storage value to config type alias
migration required
migration comparison
paritytech/substrate@polkadot-v0.9.27...polkadot-v0.9.28
paritytech/substrate@polkadot-v0.9.28...polkadot-v0.9.29
paritytech/substrate@polkadot-v0.9.29...polkadot-v0.9.30