Treasury Proposal: Streamline use of Statemine Assets in dApps on other parachains
There should be an easy way to utilize tokens that “live” on Statemine from other parachains. At the moment, this is not easily achievable. The go-to solution would be to teleport assets to other chains, thus replicating the state and losing the benefits of chain specialization.
A runtime-level parachain app can send an XCMP transfer message to Statemine, but currently has no way of reading Statemine's state, or have a secure execution confirmation.
We'd like to explore other possible options to achieve integration of a parachain dApp with Statemine.
- The dApp connects to both app parachain and Statemine, performing app logic on the first and asset transfers on the other
- The dApp lives in an off-chain worker on the parachain. It connects to Statemine as part of business logic execution.
- The dApp lives in the runtime/smart contract. Off-chain worker synchronises part of the state from Statemine to the parachain to.
We'd like to create a PoC app for each solution. Where applicable, we'd extract APIs to allow developers for easier use of our results.
As it's a bit exploratory/research proposal, we may end up implementing some better ways of using assets cross-chain, if we find them.
Team:
We're Ethworks, a blockchain software-house. For the Polkadot/Kusama community, we've implemented the Bounties UI and worked on 2 other UI-related grants: 1, 2.
Details:
You can find all the relevant proposal details in this doc.
Comments (5)
Comments (5)
(1) is the only way. Karura dapp is already connecting Kusama and Karura to transfer KSM between chains. (2), (3) makes no sense at all. I don’t understand what’s the work for this proposal and what will be the deliverables.
The thing to explore is: can we have a dApp on another parachain, acting on Statemine's asset, without transfering the asset to the parachain? Eg. the parachain would not have the assets palette, but could still do a transfer on Statemine as part of its business logic. So having composaibility not only through the UI, but also at a lower, substrate/runtime/smart contract level.
(1) is the only way. Karura dapp is already connecting Kusama and Karura to transfer KSM between chains. (2), (3) makes no sense at all. I don’t understand what’s the work for this proposal and what will be the deliverables.
The thing to explore is: can we have a dApp on another parachain, acting on Statemine's asset, without transfering the asset to the parachain? Eg. the parachain would not have the assets palette, but could still do a transfer on Statemine as part of its business logic. So having composaibility not only through the UI, but also at a lower, substrate/runtime/smart contract level.