Lecture 2: Blockchain as a Database
MIT OpenCourseWare · 1:15:56 · 2 days ago
Blockchains function as databases that track transactional history through immutable, linked records, serving as a modern iteration of traditional accounting ledgers. While these systems offer a unified platform for managing assets, they are bound by the technical constraints of distributed networks—such as the trade-offs between consistency and availability—and often struggle to reconcile data across legacy financial institutions.
- Blockchain structure — It functions as a ledger for transactions, storing data in immutable, linked blocks that require replaying the entire history to determine the current state .
- Accounting alignment — Financial tracking, whether household or corporate, relies on three core accounts—cash flow, income, and balance sheets—to ensure systematic record-keeping .
- Unified ledgers — Current financial systems are fragmented into silos; a shared, programmable platform could bridge these gaps to improve efficiency .
- System constraints — The CAP theorem dictates that distributed systems must prioritize two of three goals: consistency, availability, or partition tolerance, making it impossible to guarantee all three simultaneously .
- Money defined — An object is classified as money if it exhibits high velocity, meaning it changes hands frequently in exchange for goods and services .
- Data reconciliation — Standard financial processes and survey methods often fail to synchronize account records, leading to gaps in accuracy and delayed settlement .
- Infrastructure gaps — Modernizing financial networks is difficult because many depository institutions still rely on outdated legacy systems that are not designed for instant processing .
- Community economies — Localized credit networks function as mutual aid systems, using vouchers or digital credits to facilitate trade within a network without needing central fiat currency .
How does the CAP theorem influence the design of distributed financial ledgers?