From be84cad5556093ef380b13650c9aac1d388c91f4 Mon Sep 17 00:00:00 2001 From: Mario Pastorelli Date: Mon, 18 Mar 2024 17:43:08 +0000 Subject: [PATCH] fix --- standards/ICRC-3/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/standards/ICRC-3/README.md b/standards/ICRC-3/README.md index ee37f2c..dd82729 100644 --- a/standards/ICRC-3/README.md +++ b/standards/ICRC-3/README.md @@ -126,7 +126,7 @@ A generic ICRC-1 or ICRC-2 Block: Operations that require paying a fee: Transfer, and Approve. -The type of a generic ICRC-1 or ICRC-2 Block is defined by either the field `btype` or the field `tx.op`. The first approach is preferred, the second one exists for backward compatibility. If both are specified then `tx.op` should be ignored and `btype` should be used. +The type of a generic ICRC-1 or ICRC-2 Block is defined by either the field `btype` or the field `tx.op`. The first approach is preferred, the second one exists for backward compatibility. If both are specified then `btype` defines the type of the block regardless of `tx.op`. `icrc3_supported_block_types` should always return all the `btype`s supported by the Ledger even if the Ledger doesn't support the `btype` field yet. For example, if the Ledger supports mint blocks using the backward compatibility schema, i.e. without `btype`, then the endpoint `icrc3_supported_block_types` will have to return `"1mint"` among the supported block types.