-
Notifications
You must be signed in to change notification settings - Fork 443
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
fix(xcm): use single encoding for XCM messages #2278
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Make sense I think if the tests are passing with a runtime that has the changed mentioned here, then it should be good to merge
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The CI failing here /~https://github.com/use-ink/ink/actions/runs/10586570908/job/29335623282?pr=2278 I think is the same problem we have building the docker image in cargo-contract
: /~https://github.com/use-ink/cargo-contract/actions/runs/10556354226/job/29241730113
The nightly Rust version nightly-2024-02-08
is currently hardcoded for linting in the rust-toolchain.toml file. Does it needs to be updated?
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2278 +/- ##
=======================================
Coverage 60.53% 60.53%
=======================================
Files 141 141
Lines 5739 5739
Branches 2374 2374
=======================================
Hits 3474 3474
Misses 2265 2265 ☔ View full report in Codecov by Sentry. |
🦑 📈 ink! Example Contracts ‒ Changes Report 📉 🦑These are the results when building the
Link to the run | Last update: Wed Nov 6 14:45:42 CET 2024 |
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