[XCM]: Execution hints mechanism #107
Conversation
franciscoaguirre
changed the title
|
/rfc propose |
|
Hey @franciscoaguirre, here is a link you can use to create the referendum aiming to approve this RFC number 0107. Instructions
It is based on commit hash 598a0c4627063f9a4be1fa3b0b8d5de4ed680c36. The proposed remark text is: |
|
Jumped the gun before. Have to generate hash again. |
|
/rfc propose |
|
Hey @franciscoaguirre, here is a link you can use to create the referendum aiming to approve this RFC number 0107. Instructions
It is based on commit hash 22f9eb7328e800b1757c5ea28e5343f5b319bd1b. The proposed remark text is: |
|
PR can be merged. Write the following command to trigger the bot
|
|
/rfc process 0x3327c42aa87e7ab3812ffd18a043ae26627bab2d6a9be7e62cff472568d103ef |
|
The on-chain referendum has approved the RFC. |
Moved from polkadot-fellows/xcm-format#59.
This RFC proposes a framework for specifying "execution hints", much like window hints in GLFW.
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.