From 67de3bce35de8158cd25750901a322cc02071c95 Mon Sep 17 00:00:00 2001 From: John Wiegley Date: Fri, 24 Nov 2023 23:33:59 -0800 Subject: Make xact hashes independent of posting order Also, support matching provided hashes against a prefixed of the generated hash. --- doc/ledger3.texi | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) (limited to 'doc') diff --git a/doc/ledger3.texi b/doc/ledger3.texi index b4f3baab..ad41b985 100644 --- a/doc/ledger3.texi +++ b/doc/ledger3.texi @@ -6760,9 +6760,15 @@ Record the hash of each transaction in a @var{Hash} metadata value, according to the hashing algorithm given by the @var{ALGO} argument. Note that if a @var{Hash} metadata value is explicitly provided and does not match what would have been generated, an error is -reported. Hashes depend on previous entries, such that setting a single -hash value is sufficient to guarantee the shape of the entire history -leading up to that entry. +reported. This provided value can also just be a prefix, at whatever +length the user wishes, in which case only this amount of text is +compared to the generated hash. Printing the entry with hashes enabled +will display both this explicit metadata setting and the internally +generated hash value. + +Hashes depend on previous entries, such that setting a single hash value +is sufficient to guarantee the shape of the entire history leading up to +that entry. @item --head @var{INT} @itemx --first @var{INT} -- cgit v1.2.3