Sign in

What Bitcoin gave up and what it gained

Suggest an edit

Every design choice is a trade. Bitcoin made specific choices about what to optimise for, and those choices closed certain doors permanently while opening others.

Small blocks trade throughput for a node anyone can run

A Bitcoin block arrives every ten minutes, which is 600 seconds, and has room for a few thousand transactions. That gives about seven transactions per second on the base layer. A credit card network handles tens of thousands. Faster throughput on Bitcoin happens off the base layer, via Layer 2 systems like Lightning that settle to Bitcoin periodically rather than living on it.

The 10-minute block time and the conservative block size limit are deliberate. Every full node has to download, check and store every block. Bigger or more frequent blocks need more bandwidth and disk, so a node costs more to run and fewer people run one. The trilemma lesson goes through this in more detail. With small blocks, a full Bitcoin node can be run by one person on consumer hardware.

Solana chose the other way. It handles 1,000 to 3,000 transactions per second, and its validators need at least 256 GB of RAM and a 1 Gbps connection, with monthly costs in the four-figure range. Solana has validators in the low thousands, against well over ten thousand nodes for Bitcoin, as What Solana traded for what explains.

A limited Script trades applications for simple validation

Script, the language a coin's spending condition is written in, is intentionally limited. There are no loops, no recursion, no persistent state, no general computation. You can write conditions for spending coins and nothing else. There's no concept of a contract that has its own balance and code that other transactions can call, so you can't build a lending market or an automated exchange on Bitcoin.

In return, every node can run every script cheaply and reach the same answer, which is the public verifiability requirement from the design philosophy lesson. The whole protocol is small enough for one developer to understand fully, and every additional complexity is somewhere a bug can hide.

Ethereum chose the other way. It was designed in 2013 to run arbitrary programs, because Bitcoin's scripting language could not express the applications people wanted to build on it. Richer programs come with more attack surface. In 2016 a bug in one of them, a contract called The DAO, let an attacker move about 3.6 million of Ethereum's coin, ETH, out of it. Where Ethereum came from tells that story.

Slow upgrades trade new features for predictability

No central party can update Bitcoin's rules, and the people who run nodes adopt changes slowly. Taproot took roughly four years from proposal to activation, as the previous lesson showed. Other chains release comparable features in months. The cost is that ideas which could improve the system either wait years to be released or end up released on other chains first.

Bitcoin's deliberate slowness around upgrades is the source of the predictability that makes long-term contracts and trust possible on the chain. If the rules could change rapidly, the asset's reliability as a store of value would erode along with the rules.

The DAO story shows the other side here too. Ethereum's community changed the rules within weeks to reverse the attacker's transactions and return the ETH. The price was a permanent split into two chains, Ethereum and Ethereum Classic, and the knowledge that the community can step in and change an outcome on the chain.

A fixed supply trades a lasting miner subsidy for a policy nobody can change

The supply schedule (50 BTC subsidy halving every 210,000 blocks, capped at 21 million) is enforced by every node and effectively impossible to change. No one can vote to issue more. A monetary asset whose supply policy is fixed and verifiable is a rare thing.

The cost is that the subsidy cannot keep paying miners. The block reward is what pays them to protect the chain, and its subsidy part halves every four years, so fees have to cover a growing part of it, as the economics lesson showed. Other chains have continuous low inflation, deflationary mechanisms, or dynamic issuance keyed to network activity. Each model implies different assumptions about who should be compensated for securing the chain and how.

A public ledger trades privacy for verification by anyone

Every Bitcoin transaction is permanently visible to anyone with internet access. With no operator to vouch for transactions, every node has to verify every transaction itself, and it can only verify what it can read. So anyone can trace any coin back through its whole history, and nobody has privacy by default. Tools and patterns (CoinJoin, Lightning, fresh addresses) can improve privacy, but the base layer is public. Some chains made privacy a first-class design goal, and Bitcoin did not.

Proof of work trades energy for entry without identity

Bitcoin chose proof of work and bought security through energy expenditure. Miners spend on hardware and electricity roughly what the block reward pays them, for every block, whether or not anyone attacks. In return, the network needs no list of participants. Anyone can run a node, mine a block, send a transaction, receive a payment, all without asking anyone's permission, anywhere on the planet, at any time. There is no allowlist and no identity check at the protocol level. Bitcoin has run this way continuously since January 2009 without a successful attack on its consensus layer.

Proof-of-stake chains buy similar properties through bonded capital. Ethereum switched to proof of stake in September 2022. Its validators lock up 32 ETH each in place of spending electricity, and the network's electricity use fell by about 99.95%. The price is more moving parts, and many validators are run by staking services, exchanges, or pools, so what matters is how much stake the largest operators hold. Consensus on Ethereum covers this.

Ask the same questions of any chain

Bitcoin's trade-off: what it gave up vs. what it gainedA two-column chart titled "The trade in one picture." The left column, Gave up, lists throughput, expressiveness, feature velocity, stateful applications, and privacy by default, each with a short note explaining the limit. The right column, Gained, lists deepest security record, credible monetary policy, operational simplicity, predictability, and permissionless participation, each with a short note explaining the benefit. The trade in one picture Gave up Throughput ~7 base-layer transactions per second Expressiveness no general-purpose programmability Feature velocity years between major upgrades Stateful applications no contracts that hold balances or run code Privacy by default every transaction is public Gained Deepest security record 15+ years of continuous operation Credible monetary policy 21M cap, enforced structurally Operational simplicity runs on consumer hardware, auditable Predictability rules are slow to change and well understood Permissionless participation anyone can run a node, mine, or transact

The two columns are connected. You cannot keep the strengths while discarding the limitations, because each strength comes from the same choice as one of the limitations.

Bitcoin sits at one specific point in a design space with several axes, and each trade above is one axis. Other chains sit at different points. These axes are the framework you'll take with you into the rest of the course. When you meet a new chain later, ask: where does it sit on each of these? What did it gain by choosing as it did? What did it accept losing?