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

Bug: XCM transfer from Battery Station (2101) to Basilisk (2090) fails with XcmError: AssetNotFound #657

Open
Chralt98 opened this issue Dec 21, 2023 · 0 comments

Comments

@Chralt98
Copy link

XCM transfer from Battery Station to Basilisk fails.

Description

https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fbasilisk-rococo-rpc.play.hydration.cloud#/explorer/query/0x65eadbbffa2cce55af9c6940c5e795f46eab3031e58930f13486a1eca4a67360

Expected Behavior

XCM transfer should not fail and tokens balance for Battery Station / Zeitgeist asset id 12 should increase.

Actual Behavior

XCM transfer fails with StagingXcmV3TraitsError AssetNotFound.

Possible Fix

Update the asset registry for xcm transfers to allow parachain id 2101 for Basilisk.

Steps to Reproduce

  1. Fund your battery station account via the #testnet-faucet Zeitgeist discord channel like this !drip <your_account> 50000
  2. Use the following XCM transfer on the Battery Station of Zeitgeist: 0x7e000400e8764817000000000000000000000003010200a9200100d43593c715fdd31c61141abd04a99fd6822c8558854ccde39a5684e7a56da27d00

Context

I added an integration test to our system and realised that the basilisk parachain was incapable to successfully process the XCM transfer from Battery Station.

Your Environment

  • Toolchain versions:
  • Version used:
  • System type:
  • Operating System and version:
  • System specs:
@jak-pan jak-pan transferred this issue from galacticcouncil/hydration-node Feb 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant