Polkadot <> Kusama Bridge

Ecosystem
46

We have patched this now, thanks for noticing :slight_smile:
Screenshot_2024-04-19_17-51-01

2 Likes
47

The Polkadot BH runtime upgrade to fix the bridge is under voting in OpenGov.

Once itā€™s executed the bridge should be functioning at 100% again.

There is also a Kusama BH runtime upgrade under voting for patching the same issue on Kusama BH so we donā€™t experience the same error with the other direction too.

48

the kusama assets is now updated.

2 Likes
49

The Polkadot BH runtime upgrade to fix the Kusama->Polkadot transfers direction is under voting in OpenGov.

1 Like
50

The P<>K bridge is back to full functionality! Fully synced on both sides and processing bi-directional traffic :tada:

3 Likes
51

Awesome! Bi-directional transfers should have been enabled with the 1.2 upgrade right? Could I get assistance with building the extrinsic for sending the bridged DOT from Kusama Asset Hub to Polkadot Asset Hub? I will update the Wiki docs right after the extrinsics are executed successfully.

52

Sure! Actually, Iā€™ll use this opportunity to point people to try out GitHub - paritytech/asset-transfer-api: Typescript API aiming to provide clear, and simple to use tools for transferring assets across common good parachains..

There are examples of transferring bridged assets there, including this particular one you are inquiring about. DOT from KAH to PAH transfer API here.

Let us know if it works as expected! :smile:

The API gets more usecases integrated every day, so please request any usecase you have and is not yet covered.

1 Like
53

Thank you. The Wiki docs are now updated with bi-directional transfer info for both DOT and KSM.

4 Likes
54

The progress on the bridge PAH<>KAH is impressive. Once the fees are reduced, I anticipate it will see widespread use. However, I have a few questions:

  1. Once you have, for example, DOT in KAH, what use cases does it currently have?
  2. Is there, or can anyone create, a pool in KAH with DOT and KSM as assets (foreign-native)?
  3. Is there a team working on a UI to utilize the Asset Hub pools? (This question might not directly relate to this post, but it ties in with the previous questions.)
55

Yes :point_down:

1 Like
56
  1. I donā€™t expect DOT in Kusama have a use case beyond what parachains make out of it, e.g. in Kreivo we would allow people to make DOT payments which includes on/off ramping. In the future it would be interesting to introduce some form of remote staking via XCM, @pandres95 work on asset freezing can be a precursor of such a feature.
  2. It works, just created the pool KSM<>DOT (lpToken: 11)
  3. Thereā€™s also dotswap.org (missing Kusama AH)
2 Likes
57

Just want to share that SubWallet has integrated the Polkadot <> Kusama bridge into our browser extension UI! Mobile and web dashboard coming soon :star_struck:

6 Likes
58

What is the most convenient way to bridge assets between Kusama and Polkadot with a user-friendly interface?
After going through the conversations above I find Subwallet as a good choice :eyes:

59

As a continuation of Adrianā€™s original post above

  1. Bring down that damn high bridge fee, more details here .

I am happy to announce that the upcoming 1.3.0 Polkadot Fellows release introduces a new feature designed to reduce user delivery fees for message transfers over the Polkadot<>Kusama bridge.

For further details, please see this blog post:

5 Likes
60

May I ask for ETAs for bridging:

  • USDT + USDC to Kusama AH?
  • any foreignAsset PAH - KAH
  • permissionless lanes between arbitrary parachains
61

All assets between PAH<>KAH

All Polkadot and Kusama assets will flow freely between PAH<>KAH with Asset Hubs: allow Polkadot, Kusama and Ethereum assets across P<>K bridge by acatangiu Ā· Pull Request #421 Ā· polkadot-fellows/runtimes Ā· GitHub - nearing completion, security audit done.

This includes Polakdot USDC and USDT registered as foreign assets on Kusama Asset Hub.

On top of that, Ethereum assets on Polkadot Asset Hub can be bridged over to Kusama Asset Hub, thus giving Kusama access to trustlessly bridged Ethereum assets (coming over Snowbridge).

This will not make it into the impending Runtimes 1.3.0 release, so weā€™ll have to bring it with a 1.3.1 release afterwards. Guesstimate for that would be end of Sep, or sometime in Oct.

Permissionless lanes between arbitrary parachains

Also nearing completion: [bridges-v2] Permissionless lanes by bkontur Ā· Pull Request #4949 Ā· paritytech/polkadot-sdk Ā· GitHub, pending security audit.

This will be released with the next stable release of Polkadot-SDK estimated for end of October, and should make it onto Polkadot and Kusama runtimes by EOY.

5 Likes
62

image

the fees mentioned is wrong here, I was testing out and it deducted 0.4 KSM insteadā€¦

63

Yep we know. Itā€™s documented in the README of the project.

It was also mentioned in the previous comments of this same forum post.

Next week we are getting together with Cisco to discuss the best way to integrate the XCM fees API into the main library. So, I really think that by next week this will be fixed (and properly fixed, not harcoding values as it was previously suggested)

64

well itā€™s better to show the warning in the UI instead :slight_smile:
You canā€™t expect me to go through bunch of docs or comments.