You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As we move the governance system from the relay chain to AssetHub, we must ensure that we can still upgrade the relay chain after the AHM migration.
The actual relay chain upgrade is performed using authorize_upgrade, which requires root access. Therefore, we need to set up relay chain origin converters to process xcm::Transact(authorize_upgrade(new_code_hash)) from AssetHub. From the D-Day perspective, we should also allow Collectives.
/// The means that we convert the XCM message origin location into a local dispatch origin.
type LocalOriginConverter = (
// A `Signed` origin of the sovereign account that the original location controls.
SovereignSignedViaLocation<SovereignAccountOf, RuntimeOrigin>,
// A child parachain, natively expressed, has the `Parachain` origin.
ChildParachainAsNative<parachains_origin::Origin, RuntimeOrigin>,
// The AccountId32 location type can be expressed natively as a `Signed` origin.
SignedAccountId32AsNative<ThisNetwork, RuntimeOrigin>,
+ // TODO: add here
+ AssetHubOrCollectivesAsSuperuser<...>,
);
TODO
add an e2e, integration, or emulated test to ensure that AssetHub can issue authorize_upgrade on the relay chain as root
setup for Westend/AssetHubWestend asap
create tracking issue for polkadot-fellows
The text was updated successfully, but these errors were encountered:
// TODO: add here
AssetHubOrCollectivesAsSuperuser<...>,
We already have ChildSystemParachainAsSuperuser (not used anywhere) and similar SiblingSystemParachainAsSuperuser, but probably we want to be pretty specific here.
So I suggest we add filtering capabilities e.g.: AllowedParaIds: Contains<ParaId>;
Note: We can deprecated those and replace by generic SystemParachainAsSuperuser which could provide parents: 0/1, so we will have just one converter at all.
Question, is trusting to the location enough or we need to add some Plurality?
Relates to: #5588 (comment)
Description
As we move the governance system from the relay chain to AssetHub, we must ensure that we can still upgrade the relay chain after the AHM migration.
The actual relay chain upgrade is performed using
authorize_upgrade
, which requiresroot
access. Therefore, we need to set up relay chain origin converters to processxcm::Transact(authorize_upgrade(new_code_hash))
from AssetHub. From the D-Day perspective, we should also allow Collectives.E.g. for Kusama:
https://github.com/polkadot-fellows/runtimes/blob/main/relay/kusama/src/xcm_config.rs#L194
https://github.com/polkadot-fellows/runtimes/blob/main/relay/kusama/src/xcm_config.rs#L94-L102
TODO
authorize_upgrade
on the relay chain asroot
polkadot-fellows
The text was updated successfully, but these errors were encountered: