> 2. Why can't an SQL database with whatever levels of cryptographic assurance you'd like to add do the job?
> 3. What does a blockchain add to (2) that no other technology does, regardless of cost?
I'll preface this by saying that I'm not a blockchain expert, but from the comfort of my own armchair I consider that the main benefit over a regular SQL database is the fact that you don't need to make it secret and protect it.
There might be other methods for storing a well-ordered list of events in a difficult to tamper with but at the same time public repository, but I don't know of any.
> I'll preface this by saying that I'm not a blockchain expert, but from the comfort of my own armchair I consider that the main benefit over a regular SQL database is the fact that you don't need to make it secret and protect it.
What are you needing to make secret or protect?
> There might be other methods for storing a well-ordered list of events in a difficult to tamper with but at the same time public repository, but I don't know of any.
Look at all the repositories up on github that are doing exactly this. I don't know why you would need to store voting results as well-ordered, but if you wanted to it's easily possible.
> 3. What does a blockchain add to (2) that no other technology does, regardless of cost?
I'll preface this by saying that I'm not a blockchain expert, but from the comfort of my own armchair I consider that the main benefit over a regular SQL database is the fact that you don't need to make it secret and protect it.
There might be other methods for storing a well-ordered list of events in a difficult to tamper with but at the same time public repository, but I don't know of any.