4 ms·
As long as you trust the owner, administrator and developer of the database. I wouldn't.
by EUROCARE 4y ago
As long as you trust the owner, administrator and developer of the database. I wouldn't.
- dmitriid 4y agoInstead you trust the developer of the blockchain and of all the apps required to write data to and from it. Because blockchain. Even though there are now dozens of instances of crypto developers messing up their own work.
- EUROCARE 4y agoYes indeed, trusting something I can see and compute myself instead of trusting someone's promises. There's no way blockchain will ever be worse than just having to go along with it because there's no way to verify.
- dmitriid 4y ago> I can see and compute myself What exactly can you see and compute? The end result in the blockchain is the output of <something>, where <something> is any number of centralized actors putting data from opaque sources based on extremely complex contracts.
- kube-system 4y agoRun Postgres yourself. If Postgres developers are going to compromise their own software, it isn’t going to be to mislabel your shipping containers. Most of the info in databases is boring and nobody cares about maliciously changing it it. If someone were really interested in changing the number on your shipping container, blockchain can’t prevent someone with a $1 can of spray paint from changing it.
- EUROCARE 4y agoThen others have to trust me. > spray paint Sure, but the point here is to not lose the records too, which someone could trivially change if they own the Postgres DB. When I have a shared record of a container and somebody repaints its SN, at least I know I lost it, and I can also easily claim that I did not forge the records too because they signed the record with their wallet.