From 9ffc6ffd46d63c36a67c2ade0b4ba72a0bd22049 Mon Sep 17 00:00:00 2001 From: Braqzen Date: Tue, 28 Jun 2022 13:31:42 +0100 Subject: [PATCH 1/2] Linked receipts --- specs/protocol/abi.md | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/specs/protocol/abi.md b/specs/protocol/abi.md index c9813e42..6526cd37 100644 --- a/specs/protocol/abi.md +++ b/specs/protocol/abi.md @@ -375,17 +375,17 @@ Upon execution of ABI calls, i.e scripts being executed, a JSON object represent All receipts will have a `type` property: - `type`: String; the type of the receipt. Can be one of: - - "Call" - - "Return" - - "ReturnData" - - "Panic" - - "Revert" - - "Log" - - "LogData" - - "Transfer" - - "TransferOut" - - "ScriptResult" - - "MessageOut" + - "[Call](#call-receipt)" + - "[Return](#return-receipt)" + - "[ReturnData](#returndata-receipt) + - "[Panic](#panic-receipt) + - "[Revert](#revert-receipt) + - "[Log](#log-receipt) + - "[LogData](#logdata-receipt) + - "[Transfer](#transfer-receipt) + - "[TransferOut](#transferout-receipt) + - "[ScriptResult](#scriptresult-receipt) + - "[MessageOut](#messageout-receipt) Then, each receipt type will have its own properties. Some of these properties are related to the FuelVM's registers, as specified in more detail [here](../vm/instruction_set.md). From 58ffb2109849c36824a0af6c5df13e22e122802b Mon Sep 17 00:00:00 2001 From: Braqzen Date: Tue, 28 Jun 2022 13:34:21 +0100 Subject: [PATCH 2/2] Forgot to click save when removing quotes --- specs/protocol/abi.md | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/specs/protocol/abi.md b/specs/protocol/abi.md index 6526cd37..d7197324 100644 --- a/specs/protocol/abi.md +++ b/specs/protocol/abi.md @@ -375,17 +375,17 @@ Upon execution of ABI calls, i.e scripts being executed, a JSON object represent All receipts will have a `type` property: - `type`: String; the type of the receipt. Can be one of: - - "[Call](#call-receipt)" - - "[Return](#return-receipt)" - - "[ReturnData](#returndata-receipt) - - "[Panic](#panic-receipt) - - "[Revert](#revert-receipt) - - "[Log](#log-receipt) - - "[LogData](#logdata-receipt) - - "[Transfer](#transfer-receipt) - - "[TransferOut](#transferout-receipt) - - "[ScriptResult](#scriptresult-receipt) - - "[MessageOut](#messageout-receipt) + - [Call](#call-receipt) + - [Return](#return-receipt) + - [ReturnData](#returndata-receipt) + - [Panic](#panic-receipt) + - [Revert](#revert-receipt) + - [Log](#log-receipt) + - [LogData](#logdata-receipt) + - [Transfer](#transfer-receipt) + - [TransferOut](#transferout-receipt) + - [ScriptResult](#scriptresult-receipt) + - [MessageOut](#messageout-receipt) Then, each receipt type will have its own properties. Some of these properties are related to the FuelVM's registers, as specified in more detail [here](../vm/instruction_set.md).