From 88b123aff76f636395e610913c732518c8efa19e Mon Sep 17 00:00:00 2001 From: Michael Bianco Date: Sun, 17 Sep 2023 07:13:23 -0600 Subject: [PATCH] docs: improve transaction hint docs --- docs/configuration_file.md | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-) diff --git a/docs/configuration_file.md b/docs/configuration_file.md index 9c0edcfa..936eee79 100644 --- a/docs/configuration_file.md +++ b/docs/configuration_file.md @@ -612,12 +612,20 @@ Builtin sections are used as global configuration of DaLI's behavior. The transaction_hints section is optional and is used to force a transaction to be generated as in, out or intra. This is useful because DaLI doesn't know the user's intentions and in certain cases it needs hints from the user. For example an out transaction could be represented either as a partial intra transaction (as described above) or as a normal out transaction (perhaps a gift to another person): only the user knows the correct meaning of the transaction. In such cases a transaction_hint line can be used to clear the ambiguity. The format of this section is as follows: -
+
+```
 [transaction_hints]
-<unique_id_1> = <direction>:<transaction_type>:<notes>
+_ = ::
 ...
-<unique_id_n> = <direction>:<transaction_type>:<notes>
-
+__ = __:__:__ +``` + +For instance: + +``` +[transaction_hints] +451364dc-e1a1-5eb7-bc11-ea9f485d0159 = in:airdrop:BCH fork airdrop +``` Where: * *`unique_id`* is the unique_id of the transaction that needs to be recast;