Lesson 10 — What If...?
How Does Blockchain Actually Work?
Learning Material
1 pagesLesson 10 — What If...?
Understanding the Complex: How Does Blockchain Actually Work?
Thought experiments aren't predictions. They're ways of testing what we understand by pushing assumptions to their limits. The three scenarios below are grounded in what we've learned about how blockchains actually work — and they're meant to be unsettling in productive ways.
What if a quantum computer breaks SHA-256?
Bitcoin's security rests on two cryptographic pillars: the hash function SHA-256, used in mining and block linking, and elliptic curve digital signatures, used to authorize transactions.
A sufficiently powerful quantum computer — using Grover's algorithm — could search for a valid proof-of-work hash roughly twice as fast as classical computers. This would require miners to find harder puzzles, but the protocol can adjust its difficulty target. Bitcoin's block hashing is probably manageable.
The more serious threat is to elliptic curve cryptography. Using Shor's algorithm, a quantum computer could — in principle — derive private keys from public keys. If your Bitcoin address has been used (meaning your public key is exposed on the blockchain), a cryptographically capable quantum computer could reconstruct your private key and steal your funds.
The crucial qualifier is "cryptographically capable." Current quantum computers have dozens to hundreds of qubits and are nowhere near the millions of error-corrected qubits that would be required to run Shor's algorithm against real-world key sizes. Most estimates put this capability fifteen to thirty years away — but the uncertainty is genuine.
What happens if the timeline is shorter than expected? Bitcoin's developers have known about this risk for years. The transition would require a protocol upgrade replacing elliptic curve signatures with post-quantum cryptography — schemes based on lattice problems or hash functions, which resist quantum attacks. NIST finalized the first post-quantum cryptography standards in 2024. Migrating Bitcoin would require a hard fork: a network-wide upgrade that every node must adopt. Hard forks in Bitcoin are politically contentious and technically complex.
The scenario is survivable — if the timeline gives adequate warning and the community can coordinate. If a capable quantum computer appears suddenly, with no preceding advance notice, the story becomes much darker.
What if the digital euro launches — does Bitcoin still matter?
The European Central Bank's digital euro would be a programmable form of central bank money: issued by the ECB, distributed through commercial banks, holding the full legal status of euro banknotes. It would run on infrastructure partly inspired by distributed ledger technology, but controlled entirely by central authorities.
Central bank digital currencies and decentralized cryptocurrencies are often presented as competitors. In the narrow sense of "means of payment," they overlap: both are digital, both enable direct transfers, both could operate on smartphones.
But the design intent is fundamentally different. A digital euro is programmable money within the existing sovereign monetary framework: it can be tracked, frozen, and managed by monetary authorities. Bitcoin is designed to be resistant to exactly that kind of control.
These properties appeal to different users for different reasons. The digital euro would likely displace a significant portion of current stablecoin use — Tether, USDC — in European markets, because it would offer the same functionality with central bank backing and no counterparty risk. It is less obvious that it would displace Bitcoin, which is used by people who specifically want an asset outside the control of any government.
The more interesting question is whether CBDCs — by demonstrating that digital money can work at scale, with good user experience — would normalize the concept and inadvertently increase comfort with crypto, or whether they would crowd it out by offering a regulated, trusted alternative.
The honest answer: we don't know. No large economy has fully launched a retail CBDC. We're in the experimental phase.
What if all major governments ban crypto?
China banned it. The network survived, with hashrate migrating to Kazakhstan, the US, and elsewhere within months. What would happen if the US, EU, and major Asian economies coordinated a simultaneous ban?
This scenario has not happened — and the coordination required would be historically unprecedented. But thinking it through reveals what "decentralized" actually means in practice.
Protocol bans: you cannot ban the Bitcoin protocol the way you ban a company. The code is open-source, distributed across thousands of nodes, and implementable by anyone with a computer. A government can make running a node illegal; it cannot make the protocol cease to exist.
Exchange bans: this is where enforcement can bite. Removing licensed exchanges, forcing banks not to process crypto-related transactions, and treating crypto holdings as illegal all impose real costs and friction. Most casual users would exit; the network would shrink dramatically in trading volume.
Mining bans: as China demonstrated, effective mining bans can shift large amounts of hashrate rapidly. But the network adjusts its difficulty, and mining hardware is relatively portable.
What would likely survive: a smaller, slower-growing Bitcoin network, used primarily in jurisdictions without effective bans and by individuals who specifically seek censorship-resistant money. Whether that's a meaningful fraction of current use depends on how widely useful you think censorship resistance is as a feature.
The scenario reveals a core tension: blockchain's genuine decentralization makes it difficult to ban technically, but the on-ramps and off-ramps — exchanges, banks, payment processors — are regulated entities that governments can constrain effectively.
Next lesson: What you're taking away — the central insights, the open questions, and how this course connects to the larger Understanding the Complex series.
Reading time: approx. 8–9 minutes