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
Because of asynchronous and disconnected governances for Polkadot vs Kusama, we want to allow bridge operations step-by-step in few iterations - to minimalize risk and avoid getting stuck or losing messages/assets. The end goal is to allow message transfer via bridge, only after both sides can operate and are ready to process incoming messages.
When 18. and 19. is done, at this point both sides (AssetHubKusama, AssetHubPolkadot) can receive and transfer assets DOTs/KSMs over bridge
Note: HRMP channels between AssetHubs and BridgeHubs are already opened. Note: Some governance calls can be added directly to runtime as Migrations/OnRuntimeUpgrade.
_Note: Creation of ForeignAssets for wrappedDOT/wrappedKSM will be done simultaneously: #2401
Check if it is possible to authorizeUpgrade / enactAuthrozedUpgrade + pallet_bridge_grandpa::Call::initialize as one Governance call, because initialize have to be called after enact
The text was updated successfully, but these errors were encountered:
acatangiu
changed the title
BridgeHub Kusama<>Polkadot parachains story
[P-K Bridge] BridgeHub Kusama & BridgeHub Polkadot parachains story
Apr 18, 2023
acatangiu
changed the title
[P-K Bridge] BridgeHub Kusama & BridgeHub Polkadot parachains story
[P-K Bridge] BridgeHub Kusama & BridgeHub Polkadot parachains story (bridge active and live)
Jul 21, 2023
Components
Local testing
Check here
Going live / cutover and timeline for bridge
Because of asynchronous and disconnected governances for Polkadot vs Kusama, we want to allow bridge operations step-by-step in few iterations - to minimalize risk and avoid getting stuck or losing messages/assets. The end goal is to allow message transfer via bridge, only after both sides can operate and are ready to process incoming messages.
pallet_bridge_grandpa::Call::initialize
- enables relaying Polkadot relaychain finality (which enables receiving extrinsics for otherpallet_bridge_parachains
+pallet_bridge_message
)frame_system::Call::set_storage(DeliveryRewardInBalance)
frame_system::Call::set_storage(RequiredStakeForStakeAndSlash)
pallet_bridge_grandpa::Call::initialize
- enables relaying Kusama relaychain finality (which enables receiving extrinsics for otherpallet_bridge_parachains
+pallet_bridge_message
)frame_system::Call::set_storage(DeliveryRewardInBalance)
frame_system::Call::set_storage(RequiredStakeForStakeAndSlash)
Going live / cutover and timeline for asset transfer via bridge use-case
--
Note: HRMP channels between AssetHubs and BridgeHubs are already opened.
Note: Some governance calls can be added directly to runtime as Migrations/OnRuntimeUpgrade.
_Note: Creation of ForeignAssets for wrappedDOT/wrappedKSM will be done simultaneously: #2401
Issues/TODOs:
authorizeUpgrade
/enactAuthrozedUpgrade
+pallet_bridge_grandpa::Call::initialize
as one Governance call, becauseinitialize
have to be called afterenact
The text was updated successfully, but these errors were encountered: