Finding the merkle tree in the block chain forest
summary
Clear, technical walkthrough of how Bitcoin-style ledgers actually work: transactions signed with ECDSA produce 64-character SHA-256 hashes, transactions are compressed into a Merkle root, miners search nonces under a proof of work target, blocks appear roughly every 10 minutes and the chain is ~8 years old in 2016 so rewriting history requires >100% of current hashing power. Covers Ethereum/Solidity smart contracts, Tendermint/Eris tooling, Merkle-tree uses like Google Certificate Transparency, and practical risks like key theft and the DAO-class failures.
AI-written summary · about
chapters (14)
- 0:00Start
- 4:27Digital Signatures
- 5:50One-Way Hash
- 10:32Log Integrity
- 10:57Certificate Transparency
- 11:17Bitcoin
- 16:36Byzantine Generals
- 19:16Miners
- 22:49Difficulty
- 26:09Aetherium
- 36:16Digital Signatures
- 38:56Recap
- 39:18Things That Are Important about Blockchain
- 41:02Home Messages







