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
In order to add KSM into the Omnipool, we need to ensure that users can easily transfer KSM between Kusama and Polkadot - therefore it should be added to our CROSS-CHAIN UI.
The bridge has been live for quite some time, however, there are not currently any UIs available to do this complex transaction.
The most hated man in all of Polkadot (Leemo) has provided this (very cringe) thread on X that demonstrates how this extrinsic should be constructed: https://x.com/LeemoXD/status/1866884191650189498 (this is Kusama AssetHub to Polkadot AssetHub - I would assume some additional bells & whistles need to be added in order to make it work for Kusama > Hydration)
We also need to determine which route/s we want to use here - the example from Leemo assumes the user has KSM on Kusama AssetHub, so we will need either include Kusama & Kusama AH into our UI, or we somehow do Kusama (Relay) directly to Hydration, skipping out the AssetHub Kusama & Polkadot parts.
In any event we should also include Polkadot AssetHub > Hydration transfers for KSM in our UI, in case the user already sent them to AH using a different UI.
In order to add KSM into the Omnipool, we need to ensure that users can easily transfer KSM between Kusama and Polkadot - therefore it should be added to our CROSS-CHAIN UI.
The bridge has been live for quite some time, however, there are not currently any UIs available to do this complex transaction.
The most hated man in all of Polkadot (Leemo) has provided this (very cringe) thread on X that demonstrates how this extrinsic should be constructed: https://x.com/LeemoXD/status/1866884191650189498 (this is Kusama AssetHub to Polkadot AssetHub - I would assume some additional bells & whistles need to be added in order to make it work for Kusama > Hydration)
An example call:
0x1f08030202090200a10f03000101000c691601793de060491dab143dfae19f5f6413d4ce4c363637e5ceacb2836a4e030400010000070010a5d4e80000000000
The text was updated successfully, but these errors were encountered: