In this lesson you will learn to:
- Explain the blockchain trilemma.
- Describe the privacy and energy debates.
- Judge when a blockchain is — and is not — a sensible tool.
No free lunch
Throughout this course, every feature came with a cost. Removing the central keeper adds complexity. Strong security requires work or deposits. Openness makes everything public. This final lesson gathers those trade-offs in one place.
The trilemma
A widely used way to describe the main tension is the blockchain trilemma: a blockchain wants to be
- decentralised — many independent participants can run nodes and take part;
- secure — rewriting history or breaking the rules is prohibitively hard; and
- scalable — it can handle many transactions quickly and cheaply.
Improving one usually costs something in another. Larger, faster blocks process more transactions but make running a node more demanding, which reduces the number of independent participants. Many current designs try to escape the trilemma by moving activity to additional layers built on top of a base chain.
Energy
Proof of work deliberately consumes energy, and Bitcoin's electricity use is comparable to that of a mid-sized country, according to estimates by the Cambridge Centre for Alternative Finance. Supporters point to the use of surplus or renewable power; critics point to the absolute scale. Proof of stake uses a tiny fraction of the energy, as Ethereum's 2022 switch showed, but makes different security assumptions. It is a genuine debate with data on several sides.
Privacy
Public blockchains are transparent: every transaction is visible to anyone, forever. Addresses are not names, but analysis can often link them to people. That is useful for audits and investigations, and uncomfortable for ordinary privacy. Cryptographers are developing tools such as zero-knowledge proofs, which can prove a statement is true without revealing the underlying data. Privacy features also attract regulatory attention because of money-laundering concerns.
Immutability cuts both ways
Data that cannot be changed is valuable as evidence. But mistakes, stolen transfers and personal data written to a public chain cannot easily be removed either. This creates tension with laws such as the GDPR's right to erasure, which is why careful designs keep personal data off chain.
When is a blockchain the right tool?
A useful set of questions:
- Do several parties need to share one record?
- Do they distrust each other, or any single keeper?
- Is there no trusted party everyone would accept?
- Is it worth the cost in speed, energy and complexity to remove that party?
If the answer to any of these is "no", an ordinary database run by a trusted organisation is usually faster, cheaper and simpler. Many projects have discovered this the hard way. Understanding when not to use a blockchain is as much a part of understanding the technology as knowing how it works.
Where to go next
You have reached the end of the path. Take the final quiz, revisit any lesson that felt shaky, and keep the glossary handy. The sources listed under each lesson are the best next step for anyone who wants to go deeper.
Key takeaways
- The trilemma describes a trade-off between decentralisation, security and scalability.
- Energy use depends heavily on the consensus method.
- Public ledgers are transparent, which helps audits and hurts privacy.
- A blockchain makes sense only when several distrustful parties need one record and no trusted keeper is acceptable.
Check yourself
What three properties make up the trilemma?
Decentralisation, security and scalability.
Why can public blockchains conflict with data-protection law?
Data written to them is visible and practically cannot be erased.
When is an ordinary database usually the better choice?
When a trusted keeper exists and is acceptable to everyone involved.
Sources
This lesson is for general education about how the technology works. It is not a recommendation to acquire, sell or hold any crypto-asset and is not financial advice.