>>
>>17578
Oh! You mean you include in each message the input to the hash in the previous message. Sorry, I misunderstood. What you're referring to is known as proof of knowledge.
>Also, blockchains have consensus mechanisms such as PoS, FBA and PoW.
A blockchain is merely a data structure where each block is linked to the previous block (or some number of blocks) via a hash. It does not imply a distributed system. Even if there is a distributed system, the consensus algorithm can be as simple as "whatever the authoritative source says", which is pretty much how Git is typically used.
>>17579
>I said prove authenticity "given the authenticity of the first", not absolutely.
If that's all the assurance you want, you could also include your ECDSA public key in the first message and the signature for each subsequent message. Then you wouldn't need to keep track of which secret message you used as input to the previous hash.
Needless to say, neither method protects you if the site's operator decides to rewrite you messages.
>All in all, it seems like a pretty useless protocol compared to something like RSA or Lamport signatures. Oh well, it might end up being useful as part of something else, or in a different form.
Well, you're just using it wrong, I'd say. Proofs of knowledge are typically used to prove that you had a piece of information at an earlier time that you decide to disclose that information. For example, you might make public a hash predicting that the stock market will crash this week, and after it crashes you make public that information, which should hash into the previous hash.