Skip to content
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

[RFC] Execution hints #59

Conversation

franciscoaguirre
Copy link
Contributor

RFC#37 introduces a SetAssetClaimer instruction.
This idea of instructing the XCVM to change some implementation-specific behavior is useful.
In order to generalize this mechanism, this RFC introduces a new instruction SetExecutionHints
and makes the SetAssetClaimer be just one of many possible execution hints.

@xlc
Copy link
Contributor

xlc commented May 24, 2024

Do you have some examples of other potential hints that we may have?

@franciscoaguirre
Copy link
Contributor Author

franciscoaguirre commented May 24, 2024

@xlc Thinking of the leftover fees in #53, we could have a LeftoverFeesDestination hint to send all leftover fees to that location.

Another idea could be a PreferredFeeAsset to hint the executor so it can know what asset is going to be used for fees to pay them for example.

@franciscoaguirre
Copy link
Contributor Author

Closing in favor of polkadot-fellows/RFCs#107

@franciscoaguirre franciscoaguirre deleted the set-execution-hints branch July 23, 2024 12:07
paritytech-rfc-bot bot pushed a commit to polkadot-fellows/RFCs that referenced this pull request Aug 26, 2024
Moved from polkadot-fellows/xcm-format#59.

This RFC proposes a framework for specifying "execution hints", much
like [window hints in
GLFW](https://www.glfw.org/docs/3.3/window_guide.html#window_hints).
The first one is `AssetClaimer`, that allows the user to specify who can
claim trapped assets resulting from that program execution. That was an
instruction already approved and targeted at XCMv5. This RFC proposes to
move it to this hints mechanism.

Another potential hint is `LeftoverAssetsDestination`, which, when set,
would send all leftover assets to a particular location instead of
trapping. This additional hint is not covered by the RFC. It could be
proposed in a new one.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants