The trilemma sales pitch

Wonder

1. Why does increasing the speed of a blockchain usually reduce the number of people who can verify its history?
2. What specific hardware or bandwidth requirements determine whether a chain remains permissionless in practice?
3. How does the choice to sacrifice decentralization for scalability alter the security model of a network?

Explore

1. Vitalik Buterin popularized the ‘scalability trilemma’ around 2017, arguing that a distributed system can easily achieve two of three properties—decentralization, security, and scalability—but rarely all three. This framework became the primary lens through which new chains evaluated their architectural choices. While earlier discussions touched on these tensions, Buterin’s formulation provided a standardized vocabulary for developers to justify trade-offs. A chain that prioritizes high throughput often must accept higher hardware requirements or centralized coordination, sacrificing decentralization in exchange for speed.
2. In practice, achieving higher transaction throughput typically requires one of three mechanisms: larger block sizes, faster block intervals, or more computationally intensive consensus rules. Each mechanism increases the cost of running a full node that verifies every rule independently. When block data grows, bandwidth and storage requirements rise; when blocks arrive more frequently, synchronization load increases. These technical demands filter out casual participants, leaving only well-resourced entities capable of maintaining the infrastructure necessary to validate the chain’s state.
3. Bitcoin chose cheap verification over raw throughput on its base layer. A Bitcoin node runs on modest hardware, such as a standard laptop or single-board computer, allowing anyone with an internet connection to verify the entire transaction history. This design preserves decentralization by ensuring that no specialized enterprise-grade infrastructure is required to participate in consensus. Throughput constraints are managed through scaling layers like the Lightning Network (Level V), which process transactions off-chain while settling finality on the main chain.
4. Ethereum illustrates the tension differently. In 2020 its roadmap moved from sharding execution to a rollup-centric plan: the base layer stays verifiable while rollups carry most activity, and ‘danksharding’ expands the data space rollups use (lesson 8.2.6). The trade-off is explicit: pushing more data onto the base layer increases verification costs, while keeping it off-chain requires trust in the integrity of those secondary layers.
5. Nearly every new chain launched since 2017 has claimed to solve the trilemma by achieving all three properties simultaneously. In practice, these claims usually rest on subtle shifts in what ‘decentralization’ or ‘security’ means for that specific network. Some chains reduce the number of required validators to a small set of powerful machines, trading broad participation for high speed. Others introduce trusted relayers or committee-based finality. The critical question is not whether a chain is fast, but who can verify its rules and at what cost.
6. To evaluate any new chain’s pitch, examine two concrete metrics: the minimum hardware specifications required to run a full node that checks every rule, and the actual number of independent parties running such nodes. If a chain requires enterprise servers or dedicated data centers to participate in consensus, it has traded decentralization for scalability. If only a handful of entities can afford to verify the state, security depends on their honesty rather than mathematical proof. This check reveals the true trade-off hidden behind marketing claims.

Key facts

Exercise nine, six, three, one

Fact check

Dates, figures and claims checked against the published sources listed below.

• V. Buterin, 'Scalability Trilemma' (blog writing and Ethereum sharding FAQ)
• Bitcoin Core documentation, 'System Requirements'
• Ethereum.org, 'Scaling' section of the roadmap
• J. Poon & T. Dryja, 'The Bitcoin Lightning Network: Scalable Off-Chain Instant Payments' (2015/2016)