Allow Polkadot Collectives to govern the Kusama (relay)

[bkontur]

Summary

Allow xcm::Transact from PolkadotCollectives on the KusamaRelay.

Explanation / tasks

• Open a bridge lane between PolkadotCollectives and KusamaRelay on the BridgeHubPolkadot/BridgeHubKusama:
  • Either wait for the permissionless lanes BridgesV2 feature (in-progress) issue #2451.
  • Or check Slava's PoC for a static lane before BridgesV2 (see hints below).
• Add XcmRouter to the PolkadotCollectives for the Location::(2, GlobalConsensus(Kusama)) destination.
  • paid or unpaid (SovereignPaidRemoteExporter, UnpaidRemoteExporter or pallet_xcm_bridge_hub_router)
• Configure type UniversalAliases for xcm_executor::Config for Kusama.
• Adjust/change/extend type OriginConverter = LocalOriginConverter; on Kusama to trust PolkadotCollectives:
  • Create ConvertOrigin for GlobalConsensus functionality.
• more ???

Testing

• add xcm emulated integration tests
  • to send xcm::Transact from PolkadotCollectives to the Kusama relay (e.g. set some HostConfiguration parameter or open HRMP channel, ...)
  • to send xcm::Transact from PolkadotCollectives to the Kusama's parachain - to see that it is correctly propagated on the Kusama and we control root origin

Open questions

• Do we need a RFC for fellows?