-
Notifications
You must be signed in to change notification settings - Fork 17
XCM v3-ready environment #41
Comments
please correct me if I'm wrong: the work here can be split into three pieces:
|
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 FYI on the runtime level the |
Leaving my "working" branches here as references: https://github.com/arturgontijo/polkadot/tree/trappist-xcm-v3 All of them are using a "static" substrate repo: |
I updated the forks from @arturgontijo to be compatible with But I had to fork again, which started to get a bit too complex to maintain. The following branches have been successfully tested for asset teleport and reserve-based transfers with XCMv3 and |
@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. |
@hbulgarini closing as not relevant anymore. |
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
The text was updated successfully, but these errors were encountered: