4 ms·
Not a good case for shared write access. Just shared read access. DB's come with their own logs. If one wanted to provide verification one only needs to provide
by nstart 9y ago
Not a good case for shared write access. Just shared read access. DB's come with their own logs. If one wanted to provide verification one only needs to provide logs that other people can read and maintain diffs/copies of
- Karunamon 9y agoYou can’t prove that logs haven’t been tampered with, though. The running system is a black box that could be doing anything to that file before making it available.
- lalaland1125 9y agoThis is quite simple. You simply have the running system constantly have the file or data be readable to the public. Now anyone can prove that the logs haven't been tampered with. Even better, you can just use a merkle tree data storage solution like Git to make that verification easy and fast. See Certificate Authority for a fully fleshed out solution in this nature. (I guess you could claim that merkle trees are blockchains, but in that case I would argue that the word "blockchain" is pretty meaningless. Just call them merkle trees.)
- Karunamon 9y agoBut it's turtles all the way down. How does the public know that they're getting the data and not a surrepetitiously modified version? At some point you're relying on the system to be truthful about its contents.
- nstart 9y agoHonestly you brought up really valid points. Thanks. That got me thinking a plenty :)