Meet the New Boss
How crypto quietly became the thing it was built to replace
There’s a quote that gets applied to revolutions so often it’s become a cliché: meet the new boss, same as the old boss. It’s a cliché because it keeps being true. Crypto was supposed to be different. For a while, it was easy to believe it might be. It isn’t.
This isn’t a hit piece. The underlying technology is real, the cryptography is sound, and some of the problems it solved are genuinely hard problems that hadn’t been solved before. But the gap between what was promised and what was delivered — and more troublingly, what was known to be undeliverable while the promises kept coming — is worth talking about honestly. Almost nobody does.
The Veto That Was Never Removed
Crypto was supposed to make financial censorship technically impossible. Not merely difficult, not legally discouraged — impossible, at the protocol level. That was the point. If no single entity can block a transaction, then no government, no bank, no ideologically motivated payment processor can freeze you out of the economy because they disapprove of what you’re doing or who you are.
This matters far more than most discussions acknowledge, and it matters for a reason that has nothing to do with criminality or privacy in the abstract.
The power to block a transaction is, functionally, the power to decide who is allowed to participate in economic life. And the historical record of who exercises that power, and against whom, should give anyone pause. WikiLeaks was cut off by Visa, Mastercard, and PayPal simultaneously — before any court had found it guilty of anything. Canadian truckers had personal accounts frozen for participating in a legal protest. Palestinians have had banking and payment access revoked wholesale. In various countries, the wrong religion, ethnicity, or political affiliation is sufficient grounds for economic exclusion. The targets change depending on who holds power at a given moment; the mechanism remains constant.
The chilling effect doesn’t even require action. The possibility of having funds frozen changes behaviour. That’s the point of it.
Crypto was supposed to eliminate the mechanism entirely. Instead, KYC and AML requirements were installed at every fiat on and off ramp, and the veto was quietly handed back — not to governments alone, but to whoever controls the classification systems. That now includes compliance officers acting on vague guidance, exchanges responding to social media pressure, and automated sanctions-screening tools with false positive rates nobody audits. In some ways the veto is easier to exercise than in traditional banking, because crypto exchanges have weaker legal protections for customers and less regulatory accountability than actual banks.
The state never actually ceded ground. It let the experiment run until it was large enough to be worth regulating, then walked in through the front door it had always owned. The “exit from the financial system” was always a round trip that began and ended inside the system.
The revolution was real. The veto survived it.
Lightning in a Bottle — That Was Never Going to Light
You can’t buy a coffee with Bitcoin. Lightning Network was supposed to fix that. The pitch was compelling: take small transactions off-chain, settle periodically on-chain, get fast cheap payments without clogging the base layer.
The reality is messier. To open a Lightning channel you need an on-chain transaction — which at current fee levels is often economically irrational for the amounts you’d use Lightning for in the first place. Routing payments reliably requires well-connected, well-funded nodes, and in practice that means a small number of large hubs, which are increasingly regulated entities subject to the same veto infrastructure described above. Inbound liquidity — the problem of ensuring you can receive payments, not just send them — is a genuine unsolved UX nightmare that normal people simply cannot navigate.
But the deeper problem is rarely discussed, and it’s not a UX problem. It’s a routing problem, and it’s arguably unsolvable as stated.
Channel balances in Lightning are private — by design, for privacy reasons — which means routing nodes are trying to find a path through a graph where the edge weights are hidden and change dynamically. A route is discovered, but the network state has shifted by the time the payment attempts to execute. Liquidity has moved, a node has gone offline, something crashed. The payment fails. Failed payment penalties then degrade the network state further. You’re trying to optimise a system using information that doesn’t exist, in a state that changes faster than you can measure it.
This isn’t a hard optimisation problem that better algorithms will eventually crack. It’s a categorically different kind of problem. The information needed to solve it is, by design, unavailable. The “we’ll fix routing eventually” roadmap assumes a solvability that the architecture itself prevents.
Lightning is not Bitcoin. It is, charitably, a clever workaround that introduces custodial risk, routing complexity, and centralisation — while delivering coffee payments to a small number of technically sophisticated users under favourable conditions. Less charitably, it’s the most elaborate way yet devised to make a decentralised system depend on centralised infrastructure while retaining the branding.
The L2 Sleight of Hand
Ethereum’s Layer 2 ecosystem — Optimism, Arbitrum, Base, and others — is where the sleight of hand gets most sophisticated.
As of mid-2026, every major L2 still runs a centralised sequencer operated by a single entity. Arbitrum is run by Offchain Labs. OP Mainnet is run by OP Labs. Base is run by Coinbase. The sequencer receives all transactions, orders them, and posts batches to Ethereum mainnet. It is, functionally, a server. A fast, clever server with some cryptographic guarantees bolted on, but a server. And because it’s a server run by a company, it is subject to exactly the same legal pressure and veto mechanisms as any other financial intermediary.
The standard response is that this is temporary. Decentralised sequencers are on the roadmap. They’ve been on the roadmap for years. They will remain on the roadmap, because the problem they’re trying to solve is not merely difficult — it’s structurally contradictory with the thing that makes optimistic rollups work.
Here’s why.
Optimistic rollups derive their security from fraud proofs. The system assumes transactions are valid, posts them to L1, and allows a challenge period during which anyone can prove the sequencer cheated. But “proving the sequencer cheated” requires a canonical ground truth — a definitive record of what the correct transaction ordering was — to compare against. That’s the whole point.
Now introduce multiple sequencers. Whose ordering is canonical? To answer that, you need consensus. Consensus requires all sequencers to agree before a block is finalised. But agreeing takes time, and that time cost is precisely what building an L2 was supposed to eliminate. You’ve reintroduced the latency you were escaping.
It gets worse. Transaction ordering isn’t just a consensus problem — it’s a time problem. Determining a canonical order requires a canonical clock. In a distributed system, there is no canonical clock. You can approximate with logical timestamps, NTP synchronisation, or “close enough” timing assumptions baked into the protocol. All of these work fine under normal conditions and fail in exactly the adversarial or high-load conditions where you most need them to hold.
The sequencer’s hidden function isn’t just ordering transactions. It’s serving as the sole temporal authority for the chain. Every transaction must pass through a single point with a single clock — there is no other way to establish a definitive ordering. That role cannot be distributed without either reintroducing a single time reference (centralisation through the back door) or accepting that ordering becomes probabilistic and contested, which destroys the fraud proof model entirely.
This isn’t obscure. Anyone who thinks carefully about what a fraud proof actually requires hits this wall quickly. The people building these systems are not people who failed to think carefully. Which means they hit the wall and kept building anyway — because the network effects, the TVL, and the token valuations accrue to the centralised version now, and the unsolvable problem is a future version’s headache.
The roadmap says “late 2026 to 2027.” It will say “2028 to 2029” when that arrives.
The Unacknowledged Experiment
Here’s a thought experiment that hasn’t been run, and probably won’t be, because no one who could run it has an incentive to.
Imagine an L2 sequencer goes dark. Not in a planned migration — just gone. The team goes silent. No announcement, no handover, no warning.
The theory says recovery is possible. All the transaction data is anchored to Ethereum L1. Someone with sufficient knowledge, infrastructure, and motivation could reconstruct the chain state and get things running again.
But “theoretically possible” and “practically happens” are very different things. How long does “indefinitely silent” have to be before liquidity evaporates? How many dependent protocols — bridges, DeFi positions, wrapped assets — collapse in the ambiguous period while everyone waits to see if someone steps up? Does anyone outside the original team actually have the knowledge to reconstruct from L1 data? How long does that take? What happens to users whose funds are in mid-flight?
The “trustless recovery from L1” guarantee is load-bearing architecture that has never had weight put on it. The market prices it as if it has been tested. It hasn’t.
The reason this experiment won’t be run intentionally is that everyone knows, at some level, how the market would respond. That response would reveal, plainly and permanently, exactly what these systems actually are versus what they’re marketed as. The gap between those two things — held open deliberately, by people who understand both — is where the intellectual dishonesty lives.
What’s Actually True
The technology is real. Digital scarcity is real. The cryptography works. Bitcoin, at the base layer, still functions more or less as designed — a censorship-resistant store of value that no single entity can inflate away. That’s not nothing.
But the access layer is almost entirely captured. Most people interact with Bitcoin through custodial products. Most Ethereum activity runs through centralised L2 sequencers subject to legal jurisdiction. The fiat ramps are fully gated. The veto that crypto was supposed to eliminate has been reinstalled at every practical entry and exit point.
Monero gets closer to the original intent than almost anything else in the space — genuinely private, fungible, actually usable as cash, resistant to the kind of transaction tracing that makes financial censorship possible. Which is presumably why it’s being systematically delisted from every major exchange. The message is unambiguous: we support decentralised finance, unless it actually works as advertised, in which case it becomes a compliance problem and disappears.
Bitcoin is possibly the last major chain that still approximates the original vision at the protocol level — and even there, the majority of mining is controlled by a small number of entities, and the average user never touches the base layer at all.
The new boss looks a lot like the old boss. It runs faster, charges different fees, and has much better branding. But it’s still a server, still gatekept at the ramps, and still operated by entities that can be leaned on by anyone with sufficient legal or political leverage.
The revolution was real. The mechanism it was built to dismantle survived, adapted, and moved in.
These are my own views, worked out through conversation and reading. I’m happy to be wrong about any of it — but I haven’t been persuaded yet.
Born suspiciously male on a small blue planet during its one thousand nine hundred and seventy first orbit chasing an unremarkable star in a galaxy tucked away at the edge of the universe where nothing of much interest happens and even less is remembered.