chore(runtime): remove enacted block_time_6s migrations; heima spec 9270, node 0.9.27#4052
Open
Kailai-Wang wants to merge 1 commit into
Open
chore(runtime): remove enacted block_time_6s migrations; heima spec 9270, node 0.9.27#4052Kailai-Wang wants to merge 1 commit into
Kailai-Wang wants to merge 1 commit into
Conversation
…pec 9270, node 0.9.27 The 12s->6s block-time migrations (spec 9262) have been enacted and finalized on heima mainnet and verified on-chain: - OnePassRescale (single-block): guard `OnePassRescaleDone` set; parachain-staking Round, score-staking RoundConfig, and scheduler Agenda rebased correctly. - VestingRescaleMigration + identity LazyMigrationV1ToV2 (multi-block): both present in pallet_migrations Historic; MBM Cursor is None (idle, nothing in progress). Remove the now-enacted one-shot migrations (matching the earlier paseo cleanup in #4050): - drop `block_time_6s::OnePassRescale` from the executive `Migrations` tuple - drop `block_time_6s::VestingRescaleMigration` from `pallet_migrations` MBMs - delete the `migration::block_time_6s` module - keep the permanent `MigrateToLatestXcmVersion` and the lazy `LazyMigrationV1ToV2` Bump heima runtime spec_version 9262 -> 9270 and node version 0.9.26 -> 0.9.27.
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
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.
What
The 12s→6s block-time migrations shipped at spec_version 9262 have been enacted and finalized on heima mainnet, so this removes the now-spent one-shot migrations (mirroring the earlier paseo cleanup in #4050) and bumps versions.
Changes:
migration::block_time_6s::OnePassRescalefrom the executiveMigrationstuple.migration::block_time_6s::VestingRescaleMigrationfrompallet_migrations::Config::Migrations(leaving just the lazypallet_identityv1→v2 migration).migration::block_time_6smodule (onepass.rs,vesting.rs,mod.rs).MigrateToLatestXcmVersionand the still-lazyLazyMigrationV1ToV2.spec_version9262 → 9270, node version 0.9.26 → 0.9.27.Why it's safe — on-chain verification
Verified the 9262 migrations are fully enacted on heima mainnet before removing:
OnePassRescaleDoneis set on-chain; parachain-stakingRound, score-stakingRoundConfig.interval, and the schedulerAgendawere rebased. The one scheduled task is anonymous + non-periodic with an emptyScheduler::Lookup(the only kind this migration rebases correctly) and now sits at a sane future block.pallet_migrations::Historic;pallet_migrations::CursorisNone(no MBM in progress) → both completed.The leftover
OnePassRescaleDoneguard key remains in storage (harmless dead key; paseo's cleanup left its equivalent too — clearing it would need another migration, not worth it).Note
No data migration in this PR — it only removes already-run migration code and bumps the version. The spec bump (9270) is the next on-chain runtime upgrade.