> If each block contains the hash of the previous block, then I think that it is a blockchain […] Or simply a 'hash chain': > A hash chain is similar to a blo

> If each block contains the hash of the previous block, then I think that it is a blockchain […] Or simply a 'hash chain': > A hash chain is similar to a blockchain, as they both utilize a cryptographic hash function for creating a link between two nodes. However, a blockchain (as used by Bitcoin and related systems) is generally intended to support distributed agreement around a public ledger (data), and incorporates a set of rules for encapsulation of data and associated data permissions. * https://en.wikipedia.org/wiki/Hash_chain https://en.wikipedia.org/wiki/Hash_chain Or perhaps: > Linked timestamping creates time-stamp tokens which are dependent on each other, entangled in some authenticated data structure. Later modification of the issued time-stamps would invalidate this structure. The temporal order of issued time-stamps is also protected by this data structure, making backdating of the issued time-stamps impossible, even by the issuing server itself. * https://en.wikipedia.org/wiki/Linked_timestamping https://en.wikipedia.org/wiki/Linked_timestamping An(other) example of the latter: This document describes a mechanism, called syslog-sign in this document, that adds origin authentication, message integrity, replay resistance, message sequencing, and detection of missing messages to syslog. Essentially, this is accomplished by sending a special syslog message. The content of this syslog message is called a Signature Block. Each Signature Block contains, in effect, a detached signature on some number of previously sent messages. It is cryptographically signed and contains the hashes of previously sent syslog messages. The originator of syslog-sign messages is simply referred to as a "signer". The signer can be the same originator as the originator whose messages it signs, or it can be a separate originator. * https://datatracker.ietf.org/doc/html/rfc5848 https://datatracker.ietf.org/doc/html/rfc5848