The blockchain trilemma explained
Every blockchain design quietly answers one question: who must be able to check the ledger? The answer decides how fast it can go.
Logos are trademarks of their respective owners, shown for identification only. Their use does not imply endorsement. Licences.

On this page
- What is the blockchain trilemma?
- Why can't a blockchain just process more transactions?
- How do real blockchains choose their trade-offs?
- How does node hardware reveal the trade-off?
- Can layer 2s or sharding get around the trilemma?
- What mistakes do people make when talking about the trilemma?
- Questions readers ask
- Sources
- The blockchain trilemma says a blockchain struggles to be scalable, secure and decentralised all at once; improving one usually costs another.
- Vitalik Buterin's 2021 framing ties scalability to what a regular node, such as a consumer laptop, can verify.
- The BIS put Ethereum's limit at about 30 transactions per second in 2022, and found fees on congested days could average over 75 times the usual level.
- Node hardware shows the trade-off: Bitcoin Core's minimum is 2 GB of RAM, an Ethereum node 16 GB, a Solana validator 256 GB or more.
- Layer 2s, sharding and new layer 1s are attempts to bend the trilemma; critics such as the BIS argue they bring new trust points and fragmentation.
The blockchain trilemma is the observation that a public blockchain finds it hard to maximise scalability, security and decentralisation at the same time. Letting a chain handle more transactions usually means bigger, costlier nodes, which fewer people can run — so throughput tends to be bought with decentralisation or security.
What is the blockchain trilemma?
The definitions most writers use come from a 2021 essay by Vitalik Buterin, which the Bank for International Settlements (BIS) cites when it discusses the idea. Buterin defines the three properties precisely:
- Scalability: the chain can process more transactions than a single regular node — think of a consumer laptop — can verify.
- Decentralisation: the chain can run without depending on trust in a small group of large actors.
- Security: the chain can resist a large share of its participants trying to attack it.
The trilemma is the claim that simple designs get at most two of these. The BIS states it bluntly in its 2022 Annual Economic Report: permissionless blockchains can achieve only two of the three. Notice that it is an engineering rule of thumb, not a mathematical theorem — which is why people keep trying to beat it.
Why can't a blockchain just process more transactions?
On a public chain, every full node re-checks every transaction. That is what lets ordinary users verify the ledger without trusting anyone. It also means the chain can only go as fast as the nodes you expect people to run.
Turn the dial up — bigger blocks, faster blocks — and each node needs more processing power, memory and bandwidth. The Lightning Network whitepaper put a number on this for Bitcoin in 2016: matching Visa's holiday peak of 47,000 transactions per second on-chain would need blocks of nearly 8 GB every ten minutes, something only a few large operators could handle.
Keep the dial down and block space stays scarce. The BIS explains that transactions offering higher fees are more likely to be included, so in busy periods users bid against each other. Its 2022 bulletin found Ethereum fees averaging around $1 in modest traffic could average more than 75 times higher on days of heavy congestion.

How do real blockchains choose their trade-offs?
Buterin's essay sorts traditional designs into three families, each giving up one corner of the triangle. The table follows his grouping; the examples in the first column are his.
| Design family | Gets | Gives up | Why |
|---|---|---|---|
| Traditional chains (Bitcoin, pre-proof-of-stake Ethereum) | Decentralisation, security | Scalability | Every participant runs a full node that checks everything |
| High-throughput chains with small validator sets | Scalability, security | Decentralisation | A small group of powerful nodes, often 10–100, runs consensus |
| Many separate chains (multi-chain ecosystems) | Scalability, decentralisation | Security | An attacker only needs to overpower one small chain |
The BIS applies similar logic to newer layer 1s, arguing that chains such as Avalanche and Solana gain capacity at the price of greater centralisation and weaker security. Supporters of those chains weigh it differently; see What is Solana? for how one such design works.
How does node hardware reveal the trade-off?
The clearest evidence is in each project's own documentation of what it takes to participate. The roles are not identical — a Bitcoin full node, an Ethereum full node and a staked Solana validator do different jobs — but the gap shows how much each design asks of its operators.
Buterin's argument is that users should not have to trust a set of nodes they could not join with a consumer laptop. By that yardstick, hardware requirements are not a technical footnote; they decide who gets to check the rules.
Can layer 2s or sharding get around the trilemma?
That is the bet Ethereum has made. ethereum.org explains that its scaling effort now centres on layer 2: rollups execute transactions elsewhere and post the data back, so the base chain stays light enough for ordinary nodes while total capacity grows. Bitcoin's Lightning Network applies a similar idea through payment channels.
Critics see costs elsewhere. The BIS argues that moving activity to layer 2s and rival chains fragments users and liquidity, and that bridges between chains often rely on a small number of validators — a weak point exploited in several high-profile hacks. Whether layer 2 designs truly escape the trilemma or just relocate its trade-offs is still debated.

What mistakes do people make when talking about the trilemma?
- Comparing raw transactions per second. A high number means little without asking who can verify it and at what hardware cost.
- Treating the trilemma as a law of physics. It is a widely cited rule of thumb; researchers are actively trying to weaken it.
- Counting validators instead of independence. Many nodes controlled by a few operators can be less decentralised than the headline count suggests — Buterin's test is whether you depend on a small group of large actors.
- Forgetting the bridge. A fast chain linked to others by a lightly secured bridge is only as secure as that bridge.
Questions readers ask
Who came up with the blockchain trilemma?
It is most closely associated with Vitalik Buterin, whose 2021 essay gives the definitions most writers use. The BIS cites that essay when it discusses the trilemma.
Has any blockchain solved the trilemma?
No design is universally accepted as having solved it. Ethereum's rollup-centric roadmap and sharding research aim to weaken the trade-off; critics argue the costs move to layer 2s and bridges.
Is the trilemma only about speed?
No. It is about who can afford to check the ledger. Speed is the visible symptom; the underlying question is how many independent parties can verify every transaction.
Does proof of stake solve the trilemma?
Not by itself. Proof of stake changes how blocks are agreed, not how much data each node must process. ethereum.org says Ethereum's move to proof of stake did not expand network capacity.
The blockchain trilemma is a useful lens rather than a law: making a chain do more usually makes it harder for ordinary people to check. When you compare networks, look past throughput figures to the hardware they demand and the parties you must trust — that is where each design pays for its speed.
Sources
- Vitalik Buterin, Why sharding is great: demystifying the technical properties (2021)
- Bank for International Settlements, Blockchain scalability and the fragmentation of crypto (BIS Bulletin No 56) (2022)Primary source
- Bank for International Settlements, Annual Economic Report 2022, Chapter III: The future monetary system (2022)Primary source
- bitcoin.org, Running a full node (2026)Primary source
- ethereum.org (Ethereum Foundation), Spin up your own Ethereum node (2026)Primary source
- Anza (Agave documentation), Agave validator requirements (2026)Primary source
- Joseph Poon and Thaddeus Dryja, The Bitcoin Lightning Network: Scalable Off-Chain Instant Payments (2016)Primary source
- ethereum.org (Ethereum Foundation), Scaling (2026)Primary source
- ethereum.org (Ethereum Foundation), The Merge (2026)Primary source
- US National Institute of Standards and Technology, Blockchain Technology Overview (NISTIR 8202) (2018)Primary source
Educational content only — not financial, investment, legal or tax advice. Crypto-assets are high-risk and you could lose all the money you put in. Rules differ by country; check with your national regulator. See our risk disclosure and editorial policy.



