-
Notifications
You must be signed in to change notification settings - Fork 764
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
[Asset Hubs] Polkadot and Kusama treasuries fund DOT/KSM pools on Asset Hubs #6959
Comments
Isn't Kusama treasury already owns some DOT (allocated by W3F)? So it can just add both KSM and DOT? |
I’m not aware of this. Where are the DOT owned by Kusama Treasury (which chain+account)? How does it access/control them? @joepetrowski you might know more? |
I can't find the source anymore but when Kusama launched, W3F promised that 1% of the initial supply of DOT will be reserved for Kusama. There is also a later post somewhere stated that those DOT will be transferred to Kusama treasury after P<>K bridge is alive. Maybe W3F people knows more about the details. |
Yeah that is right. I reached out to them to try to find out where they are. |
A must have thing! |
We're planning to propose listing KSM in the Omnipool asap but before we need to make sure the proposal will be constructed and executed correctly, so having the P<>K bridge support in Chopsticks would be helpful. |
Something I thought about, could the Polkadot & Kusama governance not just "gift" tokens for each side of the bridge? So, Polkadot governance is sending 100000DOT to Kusama and Kusama is sending KSM worth the same amount to Polkadot? Then each side can open the pools? |
Yes, they could. We need a temporary recipient though to be able to do these asynchronously - let's take Polkadot side as example:
The question is what is best If we use Polkadot Treasury SA on AH, do we have a way to instruct that account to put up the liquidity (Transact on AH)? Or do we do it through Root execute_as()? (the equivalent can be then done for Kusama, with both treasuries paying again 20k$ worth of DOT/KSM each) |
The "gift" is a good an simple thing to do but it would also be good if W3F gives a statement about the 1M DOT allocation to Kusama. The topic has been brought up several times including governance but W3F has remained silent about it. EDIT: A related topic is this WFC looking for ways to add one sided liquidity in asset conversion pallet, a suggested implementation is to have the pallet act as an escrow account that adds liquidity to the pool once there's a matching amount of the other token, this can simplify the way Kusama and Polkadot contribute liquidity to their KSM/DOT DOT/KSM pools. |
Yeah the Polkadot treasury account sounds about right. The proposal that transfers the funds, can also setup on its side a scheduled call that will then move the funds to the pool in X days. So, we only need one proposal on each side. |
DOT/KSM pools on Polkadot and Kusama Asset Hubs have very low liquidity.
We should use the Polkadot and Kusama treasuries to bootstrap this liquidity, but we have a chicken-n-egg problem: neither Treasury has access to liquidity of the other's token to be able to add DOT/KSM pair liquidity atomically.
Possible path forward:
Once we bootstrap these pairs, ecosystem arbitrage should naturally keep the pools alive and funded/balanced.
The text was updated successfully, but these errors were encountered: