What Is the Blockchain Trilemma?
Anyone reading about blockchain design eventually runs into the term “trilemma,” usually attached to a claim that a network can only be good at two out of three things at once. Understanding what those three things are helps explain why blockchains look so different from one another.
The short answer
The blockchain trilemma is the idea that a blockchain network faces inherent tradeoffs among three properties — decentralization, security, and scalability — and that strengthening one tends to come at the expense of one or both of the others. It’s a useful mental framework for understanding why different networks make different design choices, rather than a strict mathematical law.
The three properties, defined
- Decentralization. How widely distributed the network’s decision-making and validation power is, rather than being concentrated among a small number of participants.
- Security. How resistant the network is to attacks that would let a bad actor alter transaction history or disrupt normal operation.
- Scalability. How many transactions the network can process in a given period, which affects speed and cost for everyday use, closely tied to transaction throughput.
Why these three tend to pull against each other
A highly decentralized network typically requires many independent participants to agree before a transaction is confirmed, which strengthens security but slows things down, since consensus among more parties takes longer. A network built for speed can process more transactions by reducing the number of participants who validate each one, or by relying on more powerful specialized hardware, but that concentration can undercut decentralization. Choices about how block times and difficulty adjust reflect this same underlying tension between keeping the network open to broad participation and keeping it fast.
How different approaches address the tradeoff
Some networks prioritize decentralization and security, accepting slower transaction speeds and higher costs during periods of heavy use as a tradeoff. Others prioritize throughput, often by limiting the number of validators or using different consensus mechanisms, accepting a greater degree of centralization in exchange for speed. A separate approach involves building additional layers on top of a base blockchain — commonly called layer 2 networks — that handle transactions off the main chain before settling back to it, aiming to ease the tradeoff rather than eliminate it entirely.
Why the trilemma is a framework, not a fixed rule
It’s worth noting that the trilemma describes tendencies and design pressures rather than an unbreakable law of computer science. Researchers and developers continue to explore techniques that push against these tradeoffs, and some improvements in one area have come with only modest costs to the others rather than a strict one-for-one exchange. Even so, no current blockchain design has fully escaped the underlying tension, which is why the concept remains a common reference point when comparing networks.
Why this matters for understanding blockchain design
Recognizing the trilemma helps explain why one network might process transactions quickly and cheaply while another moves more slowly but claims broader participation and stronger resistance to attack. Neither approach is objectively correct — they reflect different priorities among the same three competing goals, similar to how questions about what a blockchain actually is start with understanding the fundamental tradeoffs built into its design.
What to weigh
There’s no single “best” blockchain when it comes to the trilemma, only different combinations of tradeoffs suited to different purposes. Understanding which of the three properties a given network has prioritized — and which it has sacrificed to get there — is a more useful lens than assuming any one network has solved the problem outright.