State trie migrations ah#604
Conversation
nkpar
commented
Feb 25, 2025
- Does not require a CHANGELOG entry
Eliminated the conditional `state-trie-version-1` feature and all associated code, including configurations, parameterization, and tests. The `state-trie-migration` pallet is now always included without feature gating.
Reorganized and reordered runtime configuration types to enhance readability and consistency. Adjusted type alias placements, added missing types, and restructured constants for better maintainability and alignment across pallets.
This reverts commit cb23f58.
Replaces `EnsureSignedBy<RootMigController, AccountId>` with `EnsureRoot<AccountId>` for `ControlOrigin`. This simplifies migration control logic by ensuring only the root origin has full authority over the pallet.
Updated `ControlOrigin` to support either Root or Fellowship origins. Modified `SignedFilter` to use `EnsureSigned`.
cargo fmt
Bump spec_version for AH Kusama
ggwpez
left a comment
There was a problem hiding this comment.
I think we need clarity on the bot accounts to use for the migration; otherwise looks good
Co-authored-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>
…hub-polkadot in migration workflow
|
The migration bot code is in paritytech/polkadot-scripts/blob/master/src/services/state_trie_migration.ts |
bkchr
left a comment
There was a problem hiding this comment.
One question regarding the changes in the CI code, otherwise looks good.
| "is_relay": false, | ||
| "blocktime": 12000 | ||
| "blocktime": 12000, | ||
| "runtime_args": "--overwrite-state-version 1" |
There was a problem hiding this comment.
Why do we need this? The on chain version is still 0?
There was a problem hiding this comment.
@bkchr As I updated state version in this PR - otherwise check will fail
There was a problem hiding this comment.
The externalities initialize with the state version of the snapshot (0) and then at the end of the block it is 1 and fails to match the state root. Now instead we initialise with 1.
There was a problem hiding this comment.
Are we building a block because of the possible multi block migrations?
Co-authored-by: Kian Paimani <5588131+kianenigma@users.noreply.github.com>
Co-authored-by: Kian Paimani <5588131+kianenigma@users.noreply.github.com>
Co-authored-by: Kian Paimani <5588131+kianenigma@users.noreply.github.com>
Co-authored-by: Kian Paimani <5588131+kianenigma@users.noreply.github.com>
Co-authored-by: Bastian Köcher <git@kchr.de>
Co-authored-by: Bastian Köcher <git@kchr.de>
Co-authored-by: Bastian Köcher <git@kchr.de>
|
/merge |
|
Enabled Available commands
For more information see the documentation |