What Blockchain CAN'T Do (Honest Limitations)

A clear-eyed look at what blockchain technology fundamentally cannot do well, where traditional databases beat blockchains, and how to identify when blockchain is the right tool versus when it is being applied for marketing rather than substance.

24 min · beginner · part of Blockchain: The Trust Machine

The Inverse of the Hype

Most explanations of blockchain focus on what it can do: cryptographically verifiable history, censorship resistance, permissionless access, programmable money, ownership without intermediaries. These are real properties and the earlier lessons in this module covered them in detail. The proper response to a wave of marketing claims, though, is not to multiply the claims further. It is to look honestly at the limits. Blockchain is a tool. Like every tool, it does some things well and other things poorly. The "everything will be on blockchain" thesis that emerged in the 2017 to 2021 period (often paired with NFT-everything and Web3-everything claims) ran into reality when builders tried to apply blockchain to problems it does not fit. By 2023 to 2024 the hype had collapsed in many sectors, even as the underlying technology continued to mature for the use cases it actually does serve. This lesson is the inverse of the optimistic case. We will look at the throughput limitations relative to traditional databases, the privacy limitations of pseudonymous public chains, the off-chain enforcement problem (smart contracts cannot make humans do anything in the real world), the oracle problem revisited from a skeptical angle, the cost of decentralization, the difference between real and fake decentralization, and the practical question of when traditional databases are simply better. The goal is not to dismiss blockchain. It is to give you the intellectual tools to evaluate any "blockchain solution" claim on its merits. Once you understand the real tradeoffs, you can tell the difference between a problem genuinely improved by decentralization and a problem where the blockchain is structural theater.

Also in this lesson

Database Performance: Postgres vs Bitcoin
Privacy by Default: A Myth
Off-Chain Enforcement: The Hard Limit
The Oracle Problem Revisited
Decentralization Theatre: Identifying Fake Decentralization
When Blockchain Actually Solves a Problem
For Deeper Reading

Key terms

Throughput (TPS): Transactions per second. Bitcoin processes ~7 TPS, Ethereum mainnet ~15-30 TPS, Solana up to 4,000-5,000 TPS in practice. Visa averages 24,000 TPS; PostgreSQL on a laptop handles 10,000+ writes per second.
Pseudonymous: A transaction system where addresses are not tied to legal identities by default, but every transaction is publicly visible and traceable. Bitcoin and Ethereum are pseudonymous. This is different from anonymous, which would mean transactions cannot be traced to participants at all.
Off-chain enforcement: The problem that smart contracts cannot make people do anything in the physical world. They can move on-chain assets, but cannot ensure goods are delivered, services are performed, or court orders are obeyed.
Oracle problem: A blockchain by design knows only about itself. To know anything about the outside world, it must trust an external data source (an oracle). The trust requirement does not disappear; it is shifted to the oracle.
Decentralization theatre: Marketing a system as decentralized when in practice it has admin keys, upgradable contracts without time delays, concentrated token supply, centralized infrastructure, or other markers of central control. Common in 2017-2024 era projects.
Admin key: A private key held by a project team that can pause contracts, change parameters, upgrade code, or in some cases drain user funds. A protocol with active admin keys is not meaningfully decentralized at the technical level.
Time-lock (governance timelock): A delay (typically 24 hours to 7 days) between when a governance change is approved and when it takes effect. Provides users a window to react or exit if they disagree with the change. A marker of meaningful decentralization.
Chain analysis: The practice of analyzing public blockchain data to deanonymize transactions, identify wallet ownership, and trace illicit flows. Major firms include Chainalysis, TRM Labs, Elliptic, and CipherTrace.
Composability: The ability of smart contracts to call each other and combine functionality. Enables DeFi "money legos" but also creates systemic risk: a vulnerability in one protocol can cascade through dependent protocols.
Cost of decentralization: The performance, complexity, and operational costs that decentralized systems pay to provide their unique guarantees. Throughput is lower, iteration is slower, governance is harder, and bug fixes are more expensive than centralized alternatives.
Tamper-evident timestamping: A legitimate use case for blockchains: anchoring a hash of a document on-chain provides a cheap, durable, publicly verifiable timestamp. Used for proof of authorship, evidence preservation, and audit trails.
Validator centralization: When the set of nodes producing blocks (validators in PoS, miners in PoW) is small or concentrated. Many Layer 2 systems have a single sequencer; many newer L1s have fewer than 100 validators. Limits censorship resistance.

Continue this lesson — 7 more sections in the CryptoBipto app.

Open lesson

Educational only — not financial advice.