Skip to content
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

Assets transfer between our parachain and other parachains #36

Open
serg-temchenko opened this issue May 23, 2024 · 2 comments · Fixed by #31
Open

Assets transfer between our parachain and other parachains #36

serg-temchenko opened this issue May 23, 2024 · 2 comments · Fixed by #31
Assignees
Labels
enhancement New feature or request frozen PR/Issue is on hold

Comments

@serg-temchenko
Copy link
Contributor

As described on the Teleporting Assets page, to move assets between parachains, XCM and the assets teleporting functionality should be used.

In the scope of this task, the mechanism for moving assets should be configured.

Related to Issuer #14.

@th7nder
Copy link
Contributor

th7nder commented May 23, 2024

PR #31 partially sets this up.
With current local setup just testnet, we're able to transfer assets from the Native Chain to our Parachain using extrinsics:
pallet_xcm.teleportAssets.

However, something is misconfigured on a local relaychain node and we cannot receive assets back. I was able to replicated that using the runtimes provided out of the box for asset-hub as well.

ents: 0, interior: X1([Parachain(1000)]) }
2024-05-22 16:32:24.009 TRACE tokio-runtime-worker xcm::fungible_adapter: can_check_in origin: Location { parents: 0, interior: X1([Parachain(1000)]) }, what: Asset { id: AssetId(Location { parents: 0, interior: Here }), fun: Fungible(69100) }
2024-05-22 16:32:24.009 TRACE tokio-runtime-worker xcm::execute: !!! ERROR: NotWithdrawable
2024-05-22 16:32:24.009 TRACE tokio-runtime-worker xcm::execute: result: Err(ExecutorError { index: 0, xcm_error: NotWithdrawable, weight: Weight { ref_time: 157409000, proof_size: 3593 } })

As well, teleporting between other system parachains, was not tested. E.g. (AssetHub -> Polka Storage and back).
For now, we're parking this stuff, as it's not critical.

@th7nder th7nder added the enhancement New feature or request label May 24, 2024
@serg-temchenko
Copy link
Contributor Author

Please do not close this issue until it is fully functioning. For now, it is on hold.

@jmg-duarte jmg-duarte added the frozen PR/Issue is on hold label Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request frozen PR/Issue is on hold
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants