XCM: Deny barrier checks for nested XCMs with specific instructions to be executed on the local chain #7200
+178
−5
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.
Resolves (partially): #7148
Depends on: #7169
Description
For context and additional information, please refer to Problem 2 - Barrier vs nested XCM validation.
TODO
DenyInstructionsWithXcmFor
.DenyThenTry
, so we wouldn’t needDenyInstructionsWithXcm
. However, this approach wouldn’t be as general.DenyInstructionsWithXcm::Inner
for the actualmessage
, so we don’t need duplication for top-level and nested (not sure, maybe be explicit is good thing) - see Problem2 - example. Instead of this:DenyInstructionsWithXcmFor
DenyThenTry
, but at first we need to merge xcm: fix for DenyThenTry Barrier #7169 or rebase this branch on the top ofyrong:fix-for-deny-then-try