[acjohnson55]

> The consensus problem requires agreement among a number of processes (or agents) for a single data value. Some of the processes (agents) may fail or be unreliable in other ways, so consensus protocols must be fault tolerant or resilient. The processes must somehow put forth their candidate values, communicate with one another, and agree on a single consensus value.

This seems to me to be exactly what Bitcoin does, where the "value" is the sum of all facts asserted on the blockchain.

[dozzie]

Wikipedia page is about a very concrete problem described in a specific paper. Have you read the paper?

Then, Bitcoin does not allow to choose "the sum of all facts asserted on the blockchain", not any more than a typical DHT or a gossip protocol in a peer-to-peer network. In fact, there is nothing resembling the end state as in "we now terminate the protocol with this value as the outcome", which is required by definition of any type of "consensus" term.

Also, have you tried, as I said two comments ago, swapping sealing transactions using proof-of-work with a trusted third party that provides unique timestamps for the transactions? Have you read what timestamping is?

[acjohnson55]

What paper are you even talking about? You might even be right, but you are a poor communicator.

[dozzie]

Well, I sort of assumed that since you voice your opinion about consensus as defined in computer science, you at least should know what it is. I talk about Leslie Lamport's (plus Shostak and Pease) original publication about Byzantine generals problem, from 1982.