diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/ledger.1 | 11 | ||||
| -rw-r--r-- | doc/ledger3.texi | 9 |
2 files changed, 18 insertions, 2 deletions
diff --git a/doc/ledger.1 b/doc/ledger.1 index febfaf1e..0e5ac7e7 100644 --- a/doc/ledger.1 +++ b/doc/ledger.1 @@ -1,4 +1,4 @@ -.Dd November 23, 2023 +.Dd November 30, 2023 .Dt LEDGER 1 .Os .Sh NAME @@ -639,7 +639,14 @@ Record the hash of each transaction in a .Ar Hash metadata value, according to the hashing algorithm given by the .Ar ALGO -argument. Note that if a +argument. Support algorithms are +.Ar sha512 +or +.Ar sh512_256 +where both use SHA512, but the latter only stores the first half of +the hash value. +.Pp +If a .Ar Hash metadata value is explicitly provided and does not match what would have been generated, an error is reported. Hashes depend on previous diff --git a/doc/ledger3.texi b/doc/ledger3.texi index 494847ca..13219758 100644 --- a/doc/ledger3.texi +++ b/doc/ledger3.texi @@ -6765,6 +6765,15 @@ they do not match, an error is reported. You may also write just a prefix of the @var{Hash}, which is less verbose but still gives quite good assurance. +The support algorithms are: + +@table @code +@item sha512 +Use the SHA512 hashing algorithm. +@item sha512_256 +Same as SHA512, but record only the first 256 bits. +@end table + Somewhat like balance assertions, which give assurance that previous posting amounts are correct, these @var{Hash} tags give assurance that all previous journal entries (in parse order) are unchanged (or at |