writing-migrations

Moonbeam runtime migrations manage state transitions during upgrades to preserve storage integrity and avoid breakages. They handle pallet renaming, index changes, and format updates across Moonbase, Moonriver, and Moonbeam networks using on-runtime upgrade hooks.

You validate Substrate runtime migrations using unit tests and try-runtime checks to verify storage layout changes. This includes running pre/post-upgrade checks to ensure migrations apply correctly across Moonbase, Moonriver, and Moonbeam networks.

Try-runtime validation checks Moonbeam runtime migrations by simulating storage layout changes against existing chain states. It executes pre/post-upgrade hooks to ensure pallet renaming and index modifications preserve storage integrity.

Yes, runtime migrations support pallet renaming, index changes, and format updates across Moonbase, Moonriver, and Moonbeam. They apply storage layout modifications via on-runtime upgrade hooks during network upgrades.

Managing the migration lifecycle involves registering migrations before the upgrade, applying them during the runtime upgrade, and removing them after deployment. This ensures storage modifications execute only once without bloating future runtime logic.

Runtime upgrades break storage integrity when pallet indices or storage formats shift without state transitions. Migrations prevent this by executing on-runtime upgrade hooks that explicitly transform old storage layouts into the new expected format.