[Whitelisted Caller] Upgrade all system chains to v2.0 and schedule Asset Hub Migration
## Upgrade all system chains to v2.0.0.
See the testing and reproduction document here on how the exact calls were constructed.
AHM
This runtime upgrade is in preparation for the Asset Hub Migration (see FAQ). The migration is not immediately activated after the upgrade but rather schedules itself.
### Invulnerable Change For Asset Hub
We have added four more invulnerables from the set of permissionless collators in the protocol to improve the censorship resistance of Asset Hub post-AHM. Now that governance, staking and more other functionality is moving to AH this is needed more than ever.
The numbers have been decided in collaboration with W3F researchers, and the specific collators who are put forward are those who have proven themselves and are "up next" according to the System Parachain collator bounty.
Hydration proxy switch
This referendum also changes the proxy for the pure proxy on Hydration used to DCA Treasury funds. This will be switched from the Relay Chain sovereign account to Asset Hub's sovereign account on Hydration. This is required to maintain control over the account post-AHM.
You can check this referendum to verify the pure proxy account: https://polkadot.subsquare.io/referenda/1501
"Liquidity Restriction" error fix
This upgrade also fixes a bug where accounts with funds on hold or locked for multiple reasons could not add new locks (including adding proxies etc) due to an issue with the way the free balance of an account was computed in certain scenarios.
Timeline
Block 28,476,212 (~3rd Nov, 8 AM UTC)
The referendum passes, sends the xcm to update the invulnerable set on AH, sends the XCM to switch over the Hydration proxy, and upgrades the runtimes. This should be handled like any normal runtime upgrade.
Block 28,490,502 (~4th Nov, 8 AM UTC)
The Asset Hub Migration starts.
Comments (0)