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

Migrate all existing foreign assets to XCMv4. #209

Open
acatangiu opened this issue Mar 1, 2024 · 2 comments
Open

Migrate all existing foreign assets to XCMv4. #209

acatangiu opened this issue Mar 1, 2024 · 2 comments

Comments

@acatangiu
Copy link
Contributor

We should also migrate all existing foreign assets to V4.

Originally posted by @joepetrowski in #187 (comment)

@franciscoaguirre
Copy link
Contributor

When updating the foreign assets from v3 to v4, I get an error in asset_test_utils::test_cases_over_bridge::receive_reserve_asset_deposited_from_different_consensus_works because it requires the runtime to have v3::Location for foreign assets in the version being used.

So in order to do it, the runtimes need to be updated to stable2409 (tested with stable2407 and it didn't cut it) because we need the parachains-runtimes-test-utils crate with version 17.0.0 and right now it's in 15.0.0.

We should move forward with #457

@acatangiu
Copy link
Contributor Author

acatangiu commented Oct 4, 2024

I suggest skipping polkadot sdk stable2407 (#457) and going straight for polkadot sdk stable2409.

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

2 participants