> Use cases like storing the history of a car on chain, transparent supply chains, public voting... What you'll tend to find is that adding computers and crypt

> Use cases like storing the history of a car on chain, transparent supply chains, public voting... What you'll tend to find is that adding computers and cryptography can't solve this problem. Because it still relies on someone to truthfully put data into the database. The sketchy used car salesman can still swap the sticker saying "look for the blockchain under address 123456" with one saying "789123" like they do today, or just lie about the sales price when selling it off. That's the fraud that happens today. Similarly, supply chains: it doesn't matter where the supplier entered "2,000 bananas", whether it's a database or a blockchain if an empty box still shows up on your doorstep. Public voting? There's no way to tie an address to an identity; what's preventing someone from doing a Sybil attack? DAOs try to work around this with "one vote per dollar", which is not a voting structure everyone thinks is useful, for hopefully obvious reasons. If you can tie an address to an identity, you have to be careful not to lose the pseudonymous property: you might not want your boss to know which way you voted.