TRE Instruction for simpler multicalls #639
Open
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.
[Link to related issue(s) here, if any]
[Short description of the changes.]
This pull request adds documentation for a new instruction to the Fuel VM instruction set, specifically describing the
TREoperation for transferring coins to an external context. The most important changes are grouped below:Instruction Set Documentation Updates
TREinstruction ("Transfer coins to external context") to the instruction index list insrc/fuel-vm/instruction-set.md.TREinstruction, including its description, operation, syntax, encoding, effects, usage notes, panic conditions, receipt structure, and state changes. This explains how assets are transferred from an internal contract context to the external script context and the requirements for successful execution.This functionality enables simpler patterns for chaining multi-calls across different applications with scripts. If TRE is used to return the funds to the user after each operation such as "swap" or "borrow", applications won't need to have any special logic to manage transfers between each other (see workarounds here).
Before requesting review
After merging, notify other teams
[Add or remove entries as needed]