03-09-2023, 10:58 PM
(03-09-2023, 09:45 PM)Dimster Wrote: For one thing there is the verification or validation of the data written. The data is simply not just written as a typical database entry but checked for accuracy.
This is simply a feature of the program interacting with the blockchain and the data you store on it, not the blockchain itself. Nothing prevents you from adding anything you want to a blockchain beyond the code you write to verify the changes, in the same way that the code would prevent you from making bad modifications to a database. You can also add tables and entries to your database for the purpose of verifying the database contents in the future (though the history on the database would also allow this).
(03-09-2023, 09:45 PM)Dimster Wrote: There would also be the security feature of it as well. While I wouldn't have the numbers of people accessing the data as a bank or corporation has, but where someone else has access to the data, blockchain structure pretty much ensures the data will not be corrupted without breaking the chain.
Maybe, but then typical SQL databases offer ways to setup read-only accounts or accounts with restricted access that would prevent them from changing the history. Additionally there's little reason to give people direct access to the database anyway, it's much better to setup a service that talks to the database and exposes some of the data through an authenticated API, that really restricts who can access the database and makes it easier to track changes. Similar to a blockchain you can also replicate a database elsewhere so that even if they manage to completely screw up the master copy you still have others.
I also again mention that detecting a "break in the chain" is not as simple as you're suggesting. Anybody can create a new valid chain starting at any point in the past, so how do you determine which chain is the "correct" one? This is the hard problem of using a blockchain that Bitcoin solves with a POW algorithm, but that doesn't work at a small scale.
git for example simply leaves it up to the user to determine this. It will warn you when your chain does not match what is somewhere else, but it can't tell you what the "correct" chain is because it has no way of knowing. Depending on what has happened there's not necessarily a "correct" chain anyway.