This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
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.
Implement AliasOrigin processing in XCVM #7245
Implement AliasOrigin processing in XCVM #7245
Changes from 4 commits
43044fc
59b6056
cb0ff78
7efcc39
c1c41f6
97f1f31
d984c95
19e3123
312461d
f115cca
c7c3473
39743b6
de583b6
7530772
f29f111
56c7e03
e3f71ed
a325ee9
31c12fd
9b74bfb
e2c2da2
0f9bba5
cb82d9b
26f2062
e5c910b
f3e4342
da0c6d4
c34c201
046c7d1
e7d8749
a6350e1
2f2c80c
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
@KiChjang @vstam1
I dont see any usage of
AliasOrigin
now, and cannot find any restrictions or recommendation for this instruction,but if we have
ClearOrigin
beforeAliasOrigin
in XCM message, then it wont work, I dont know maybe it is intended,just thinking, what if we change:
to:
would that be a problem or issue?
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.
I was thinking about that as well, but instead of using the original origin (could very easily lead to an origin escalation attack), we could also just have
Aliasers::contains
accept anOption<MultiLocation>
as the origin ML. This will then allow custom logic to be used when the origin register is set toNone
.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 question with this approach now is to really ask ourselves whether
AliasOrigin
is a privileged operation or not. To be safe, I've erred on the side of caution and made it so, but it does not necessarily have to be the case if we document it properly, letting other chains know that they absolutely need to know how to handle theNone
case appropriately in theirAliasers
implementation.