Comment on Please Stop
Knock_Knock_Lemmy_In@lemmy.world 3 months agoWho are “they” in the above message?
If you trust all your employees then an internal blockchain is useless, but do banks really totally trust their employees?
Comment on Please Stop
Knock_Knock_Lemmy_In@lemmy.world 3 months agoWho are “they” in the above message?
If you trust all your employees then an internal blockchain is useless, but do banks really totally trust their employees?
hark@lemmy.world 3 months ago
A blockchain won’t solve incorrect transaction information any more than an audit log in this case. This is an entirely internal process controlled by the bank and access would be restricted, so they couldn’t just edit audit logs. How do you think a blockchain would be used to improve this?
Knock_Knock_Lemmy_In@lemmy.world 3 months ago
The actions that an employee could perform would be limited by their private key’s abilities. Blockchain can be preventative. It’s not only for retrospective analysis.
hark@lemmy.world 3 months ago
The actions that an employee could perform in any database would be limited by their account permissions. Blockchain doesn’t change this. I pointed out a retrospective mechanism because a completely internal blockchain wouldn’t prevent tampering either.
Knock_Knock_Lemmy_In@lemmy.world 3 months ago
You end up with a very complex database account management.
I agree in general. Fully internal databases should not be blockchains.
But if external access is required at any point then there may be a blockchain use case.