Skip to content
This repository has been archived by the owner on May 21, 2024. It is now read-only.

XCM v3-ready environment #41

Closed
hbulgarini opened this issue Aug 18, 2022 · 6 comments
Closed

XCM v3-ready environment #41

hbulgarini opened this issue Aug 18, 2022 · 6 comments
Assignees

Comments

@hbulgarini
Copy link
Contributor

hbulgarini commented Aug 18, 2022

Create a new local version of polkadot with XCM v3 changes back ported into it.

XCM v3 PR in Polkadot:
https://github.com/paritytech/polkadot/pulls?q=is%3Apr+is%3Aopen+xcm+v3

Main PR: paritytech/polkadot#4097

Cumulus companion account: paritytech/cumulus#697

@arturgontijo

@bernardoaraujor
Copy link
Contributor

bernardoaraujor commented Aug 18, 2022

please correct me if I'm wrong:

the work here can be split into three pieces:

  • a polkadot executable with XCMv3 enabled (coming from a branch of github.com/paritytech/polkadot with XCM v3 polkadot#4097 and Some late fixes for XCMv3 polkadot#5237 merged)
  • a polkadot-collator executable with XCMv3 enabled (coming from a branch of github.com/paritytech/cumulus with XCM v3 Companion cumulus#697 merged and xcm_config.rs properly configured)
  • a trappist-collator executable with XCMv3 enabled (coming from a branch on this repo, with xcm_config.rs properly configured)

@hbulgarini
Copy link
Contributor Author

hbulgarini commented Aug 18, 2022

Please take into account that XCM configurations involves client and runtime. So for dmp/ump set up your statements are correct. Then for Polkadot, Trappist and any other parachain that we might use we need to configure the xcm_config.rs configuration file.

FYI on the runtime level the xcm_config.rs contains the pallet configuration for the XCM executor and the XCM pallet implemented in the runtime.

@arturgontijo
Copy link
Contributor

Leaving my "working" branches here as references:

https://github.com/arturgontijo/polkadot/tree/trappist-xcm-v3
https://github.com/arturgontijo/cumulus/tree/trappist-xcm-v3
https://github.com/arturgontijo/trappist/tree/xcm-v3

All of them are using a "static" substrate repo:
https://github.com/arturgontijo/substrate

@bernardoaraujor
Copy link
Contributor

I updated the forks from @arturgontijo to be compatible with v0.9.28.

But I had to fork again, which started to get a bit too complex to maintain.
So I asked permission to @dvdplm and created some branches for us on the upstream repos.

The following branches have been successfully tested for asset teleport and reserve-based transfers with XCMv3 and v0.9.28:

@hbulgarini
Copy link
Contributor Author

@stiiifff can we close this issue as it has to be replaced by a new PR with the latest xcm v3 changes backported during the release? Also i think the efforts should be documented in a more descriptive way.

@stiiifff
Copy link
Contributor

stiiifff commented May 1, 2023

@hbulgarini closing as not relevant anymore.

@stiiifff stiiifff closed this as completed May 1, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants