-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[P-K Bridge] BridgeHub Kusama & BridgeHub Polkadot parachains story (bridge active and live) #2455
Closed
5 of 10 tasks
Tracked by
#2691
Milestone
Comments
Initial setup for Kusama is ready and all PRs are merged, |
4 tasks
5 tasks
acatangiu
changed the title
BridgeHub Kusama<>Polkadot parachains story
[P-K Bridge] BridgeHub Kusama & BridgeHub Polkadot parachains story
Apr 18, 2023
2 tasks
This issue has been mentioned on Polkadot Forum. There might be relevant details there: https://forum.polkadot.network/t/polkadot-kusama-bridge/2971/2 |
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
EmmanuellNorbertTulbure
added this to the Kusama <> Polkadot Parachain Bridge Release milestone
Sep 1, 2023
5 tasks
I think we may close it, since the bridge is launched :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: