This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
XCM v2/3 is not XCMP-full compatible #6543
Comments
For example, HydraDX send DAI to Acala, this is the outgoing message from HydraDX that got executed by Polkadot
this is the hrmp message received by Acala
|
I might have misunderstood something & have some bugs in Chopsticks handling HRMP. Closing for now. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Right now we have XCMP lite that parachain send XCM to another parachain via relaychain route.
In future, we will have XCMP full that parachain send XCM to another parachain directly without any intermediary.
Currently, for many operations such as reserved transfer, the XCM is sent to relaychain, relaychain execute it, and dispatch a modified XCM to dest chain for execution. This is not XCMP compatible as there will be no intermediary chain to execute the XCM before delivering it to dest chain.
Relaychain should really only do the message delivery and no execution for HRMP. Otherwise XCMP-lite won't be XCMP-full compatible, which is the goal of XCMP-lite.
The text was updated successfully, but these errors were encountered: