DEV Community

nikania
nikania

Posted on

Updating parachain with migrations

#substrate #polkadot #runtimeupgrade #parachain

How to look and add migrations while upgrading parachain to new version via runtime upgrade.

We use example of simple parachain node template with tag polkadot-v0.9.32 and upgrade it to polkadot-v0.9.40.
To test this upgrade we need local testnet. How to create simple testnet short guide here.

Build polkadot-v0.9.32 parachain-template version

First, we add some pallets that changed between these two versions to parachain-template:
pallet-alliance and pallet_assets.
Then, we build and place parachain in /bin folder

cargo build --release
mkdir bin
cp ./target/release/parachain-template-node \
    ./bin/parachain-template-node-v0.9.32
Enter fullscreen mode Exit fullscreen mode

Prepare for runtime upgrade

(official guide here)
a) change versions polkadot-v0.9.32 to polkadot-v0.9.40 in Cargo.toml
b) fix compile errors🀯
a1)-b1) it's faster to use polkadot-v0.9.40 parachain-template version instead upgrading in this example😎
c) change spec_version

d) add migrations

this was the most unclear to me (do I need to apply them? where to find migrations? how to apply them?), but I'll show you how to add substrate migrations (not your own):

  • look through the releases in Polkadot repo and search for migrations description, here I found migrations in v0.9.34 release, v0.9.38 release, v0.9.40 release
  • download the source code and look for migrations in runtime/polkadot/src/lib.rs in struct frame_executive::Executive, migrations can be summed in type Migrations or just put there, here I found the following migrations: 
// in v0.9.34
pub type Migrations = (
    //9320
    // "Bound uses of call" <https://github.com/paritytech/polkadot/pull/5729>
    pallet_preimage::migration::v1::Migration<Runtime>,
    pallet_scheduler::migration::v3::MigrateToV4<Runtime>,
    pallet_democracy::migrations::v1::Migration<Runtime>,
    pallet_multisig::migrations::v1::MigrateToV1<Runtime>,
    // "Properly migrate weights to v2" <https://github.com/paritytech/polkadot/pull/6091>
    parachains_configuration::migration::v3::MigrateToV3<Runtime>,
    //9330
    pallet_election_provider_multi_phase::migrations::v1::MigrateToV1<Runtime>,
    pallet_fast_unstake::migrations::v1::MigrateToV1<Runtime>,
    //9340
    pallet_balances::migration::MigrateToTrackInactive<Runtime, xcm_config::CheckAccount>,
    crowdloan::migration::MigrateToTrackInactive<Runtime>,
);
Enter fullscreen mode Exit fullscreen mode 
// in v.0.9.38
pub type Migrations = (
    // "Use 2D weights in XCM v3" <https://github.com/paritytech/polkadot/pull/6134>
    pallet_xcm::migration::v1::MigrateToV1<Runtime>,
    parachains_ump::migration::v1::MigrateToV1<Runtime>,
    // Remove stale entries in the set id -> session index storage map (after
    // this release they will be properly pruned after the bonding duration has
    // elapsed)
    pallet_grandpa::migrations::CleanupSetIdSessionMap<Runtime>,
);
Enter fullscreen mode Exit fullscreen mode 
// in v0.9.40
pub type Migrations = (
    pallet_nomination_pools::migration::v4::MigrateToV4<
        Runtime,
        NominationPoolsMigrationV4OldPallet,
    >,
);
Enter fullscreen mode Exit fullscreen mode
  • also look for migrations in Cumulus repo, here I found v9360 v9330 v9380 v9400
  • migrations found in Cumulus: 
// v9400
pub type Migrations = (pallet_nfts::migration::v1::MigrateToV1<Runtime>,);
// v9380
pub type Migrations = (pallet_contracts::Migration<Runtime>,);
// v9360
type Migrations = (
    pallet_alliance::migration::Migration<Runtime>,
    pallet_balances::migration::MigrateToTrackInactive<Runtime, xcm_config::CheckingAccount>,
);
// v9330
pub type Executive = frame_executive::Executive<
    Runtime,
    Block,
    frame_system::ChainContext<Runtime>,
    Runtime,
    AllPalletsWithSystem,
    pallet_assets::migration::v1::MigrateToV1<Runtime>,
>;
Enter fullscreen mode Exit fullscreen mode
  • for all pallet that exist in your chain, add migrations, here I added (don't need to add balances: read instructions in pallet_balances::migration::MigrateToTrackInactive): 
pub type Migrations = (
    pallet_xcm::migration::v1::MigrateToV1<Runtime>,
    pallet_alliance::migration::Migration<Runtime>,
    pallet_assets::migration::v1::MigrateToV1<Runtime>,
// added myself just to look in logs
    TestOnRuntimeUpgrade,
);
Enter fullscreen mode Exit fullscreen mode 
pub struct TestOnRuntimeUpgrade;

impl OnRuntimeUpgrade for TestOnRuntimeUpgrade {
    fn on_runtime_upgrade() -> frame_support::weights::Weight {
        frame_support::log::info!("ಠ_ಠ 🀞🀞🀞🀞🀞🀞🀞🀞🀞🀞 migrations applied");
        Weight::from_ref_time(1)
    }
}
Enter fullscreen mode Exit fullscreen mode

e) build cargo b -r, save wasm

Perform upgrade and check everything is ok

  • run old-versioned parachain in local testnet (can use quick list) 
cargo run ./bin/parachain-template-node-v0.9.32
Enter fullscreen mode Exit fullscreen mode

Migrations of pallet_xcm, pallet_alliance and pallet_assets are needed only if there is something in the storage of these pallets. Therefore, in this example migrations are unnecessary. I did this example only to show how to find the migrations.

Any comments, corrections and suggestions are appreciated!πŸ’¬

Top comments (0)

Read next

triptivermaa01 profile image

Unleashing Innovation: Sachin Dev Duggal's Builder.ai with Natasha Pushes the Boundaries of Gen AI and RNN

Tripti Verma -

codebycorey profile image

What is a Design System and Why Is It Important for Software Engineering?

Corey O'Donnell -

rksalo88 profile image

Learning AWS Day by Day β€” Day 41 β€” Amazon Aurora β€” Part 2

Saloni Singh -

apchapcomputing profile image

Who is going to make Vision Pro apps with Unity?

apchapcomputing -