Distributed Trust: Is “Blockchain” the answer?
summary
Claims that blockchain gives universal Byzantine robustness fail against concrete issues: forks from network partitions or greater compute power, so immutability depends on the mining community having more CPU than any attacker; bitcoin adjusts difficulty to target ten minutes per block and currently consumes roughly 7.7 gigawatts. Private blockchains often behave like slow, awkward databases; public ledgers force full nodes to keep large ledgers (~0.25 TB) and still rely on trusting individual full nodes. For many problems simple alternatives like multiple independent clouds, notary stamps, signed data, or tailored routing protocols work better.
AI-written summary · about
chapters (11)
- 0:00The hype around blockchain
- 2:01What is blockchain
- 3:30How the ledger works
- 5:29Security and consensus
- 8:37Centralized vs distributed
- 13:04Human factors in security
- 16:47Robust distributed design
- 26:16Data storage challenges
- 30:45Blockchain forks and risks
- 37:59Evaluating use cases
- 42:04Q&A and conclusion
related talks
54mDistributed Trust: Is “Blockchain” the answer?
33mByzantine generals: How the blockchain solves the distributed consensus...
47mCant we just agree
49mCrypto FinTech Systems: Can the Ultimate Trust Machine Be Trusted?
56mA sledgehammer to crack a nut: why blockchain is not (always) a good idea
43mOf course I'll use blockchain in my next application
11mHarnessing Blockchain in Modern Enterprises
01h 05mPBFT and Blockchains