fix(xcm): use single encoding for XCM messages #2278
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Closes #_
cargo-contract
orpallet-contracts
?A later release of
pallet-contracts
changes the expected XCM message format forxcm_execute
andxcm_send
from requiring a double encoded message to a single encoded message.Compatible with
pallet-contracts
onpolkadot-v1.11.0
and greater.Description
ink!'s XCM support was originally merged on
polkadot-v1.10.0
, where XCM usedexecute_blob
andsend_blob
. These accepted an encoded XCM message, which required that ink! double encode XCM messages.However, in this commit Revert execute_blob and send_blob (#4266) ,
execute_blob
was replaced byexecute
which accepts aVersionedXcm<RuntimeCall>
message. This requires that ink! single encodes the XCM message.XCM support in ink! has not had an official release, and remained in the master branch only. Additionally, since the initial support,
pallet-contracts
has stabilized the XCM host fns.Checklist before requesting a review
CHANGELOG.md