[swfsql]

> 2. The elements of the sequence are data blocks that are chained together via digital signatures.

This is incorrect. Digital signatures are used when (S) signing a transaction which must refer some precious transaction with a receiver address corresponding to the public key which verifies signature S.

Blocks are chained by their headers hashes. There are no keys nor digital signatures involved here..

[tfha]

The generally accepted theoretical / abstract term for a winning block hash is 'dynamic membership multi-party signature'

To call the solution to a block a 'signature' is not incorrect.

[swfsql]

Thank you, I wasn't aware that they used the term "signature". Before I have only seen this term as "digital signature" from pub-key cryptography, so I think it's confusing to repeat the term for different things (unless there's some hidden relation that I didn't catch). I mean, it was confusing for me, at least.

(personal opinion): On the other hand, I don't understand why it's called a "signature". Pub-key signs are used to prove integrity of some information and some form of authenticity related to the priv-keys. Block header hashes are related to integrity of immutable info, but are not related, in any way, to authenticity. So I still don't find it obvious, nor that it's appropriate, that it's a "signature".

[tfha]

A signature basically says 'someone qualified authorizes this to be valid'.

In the case of a block, the signature happens to prove the authority/qualification without needing to be connected to a specific identity.