State Trie Migration

[ggwpez]

Need to track where we are and what is missing cc @cheme @PierreBesson.
Three check marks: migration deployed, RPC reports done, migration removed from the runtime.

• Rococo [x], [x], [ ]
  • Asset-Hub [x], [ ], [ ]
  • Bridge-Hub [ ], [ ], [ ], [ ]
  • Contracts [ ], [ ], [ ], [ ]
  • Coretime [ ], [ ], [ ], [ ]
  • People [ ], [ ], [ ], [ ]
• Westend [x], [x], [ ]
  • Asset-Hub [ ], [ ], [ ]
  • Bridge-Hub [ ], [ ], [ ], [ ]
  • Collectives [ ], [ ], [ ]
  • Coretime [ ], [ ], [ ], [ ]
  • Glutton [ ], [ ], [ ], [ ]
  • People [ ], [ ], [ ], [ ]

[ggwpez]

@cheme i checked all the runtimes and i think i got all the missing ones listed here.
Could you please add the migration to the missing ones? Seems like most new chains have V1 since genesis, so its not that many.

[cheme]

Thanks,

Could you please add the migration to the missing ones?

Will do tomorrow (most likely will be the same change as the one you adapt in cecb8f4 , but I will reread the pallet logic first , just in case.

Seems like most new chains have V1 since genesis, so its not that many.

yes new chain should have started v1 (I am a bit surprise by asset_hub (we migrate at least two statemine/statemint envt), but it can be done any number of time anyway).

Did quickly check and see same thing.
Note that the three first check marks make sense to me, but not the fourth one: the state_version is switch in the runtime at the same time as the runtime with the migration is deployed (the migration only works if the state_version is 1 in the runtime).

[ggwpez]

Did quickly check and see same thing.
Note that the three first check marks make sense to me, but not the fourth one: the state_version is switch in the runtime at the same time as the runtime with the migration is deployed (the migration only works if the state_version is 1 in the runtime).

Okay, will remove 👍