Onpode
Cover art for How proof-of-work's security model makes energy consumption a feature, not a bug

How proof-of-work's security model makes energy consumption a feature, not a bug

August 5, 2026 · 10 min

Eliza Ward & Brian Reed

Proof-of-work's energy consumption is Bitcoin's security mechanism, not a flaw. Attacking Bitcoin requires replicating the honest network's cumulative computational work — anchored to real electricity and hardware, not protocol rules. Proof-of-stake replaces that physical cost with on-chain capital penalties, a structurally different trust model that remains less battle-tested.

Proof-of-work (PoW) is a consensus mechanism used by Bitcoin and by Ethereum prior to its "Merge" upgrade, in which participants called miners compete to solve cryptographic hash puzzles. The puzzle is deliberately hard to solve but trivial to verify: miners repeatedly hash block headers until they find a result below a network-defined target.

0:009:52
Get the next episode on Crypto

Follow it free — new episodes land in your feed.

Or make your own — any topic, in minutes

More Onpode episodes on Crypto

About this episode

Bitcoin's energy consumption is one of the most relitigated arguments in tech — but the debate usually skips the structural question underneath it. Why would you deliberately engineer waste into a security system? And what exactly do you lose when you engineer it back out? This episode works through proof-of-work's security model from first principles: why the energy expenditure isn't a byproduct but the mechanism itself, how the asymmetry between solving and verifying a hash puzzle creates a cost floor no attacker can fake from inside the system, and what changed — and what didn't — when Ethereum replaced all of that with proof-of-stake's slashing penalties after the Merge. The honest tension the episode doesn't paper over: slashing is a real deterrent, and Ethereum's deterministic finality is a genuine gain over Bitcoin's probabilistic six-block rule. But the cost anchor in PoS is on-chain capital, which means it moves with token price and governance — it's internal to the protocol, not independent of it. The nothing-at-stake problem, validator centralization, and the open research direction of proof-of-useful-work all point to the same uncomfortable conclusion: neither model has been stress-tested at the worst case yet. Two genuine bets, both still open. Worth understanding what you're actually choosing between.

Frequently asked

Why does Bitcoin use so much electricity?

Bitcoin's proof-of-work requires miners to burn real electricity to produce each block. Attacking the chain means replicating the honest network's cumulative computational work — anchored to hardware and kilowatt-hours, not internal protocol rules. The longer Bitcoin runs, the more expensive that cost floor becomes. The energy expenditure is the security guarantee.

What is the difference between proof-of-work and proof-of-stake security?

Proof-of-work security is external: the attack cost is physical electricity that cannot be conjured from inside the protocol. Proof-of-stake security is internal: validators stake capital, and the protocol slashes misbehavior. The deterrent in proof-of-stake is on-chain capital and governance — not physics — making it a structurally different trust model.

How much would a 51% attack on Bitcoin cost?

A 51% attack on Bitcoin requires replicating the honest network's cumulative computational work, anchored to real hardware and electricity. The cost floor grows with every year of operation — fifteen years of adversarial testing, nation-state scrutiny, and multiple market crashes have not broken it. No attacker can conjure that cost from thin air.

Did the Ethereum Merge make Ethereum less secure?

The Ethereum Merge eliminated electricity requirements and introduced deterministic finality — a genuine improvement over Bitcoin's probabilistic six-block rule. But it shifted the security anchor to on-chain capital: if ETH price drops, so does attack cost. Slashing may also be insufficient in parallel block production architectures, an attack surface not yet stress-tested at Bitcoin's scale.

What is the nothing-at-stake problem in proof-of-stake?

In proof-of-stake, without penalties, validators can rationally vote on every competing fork simultaneously because it costs them nothing — unlike proof-of-work, where voting on a losing fork wastes real electricity. Slashing, which confiscates staked ETH for misbehavior, is the designed fix, but researchers note it may be insufficient in parallel or multi-threaded block production architectures.

Grounded in 12 sources
Defending against the nothing-at-stake problem in multi-threaded blockchains · arxiv.org
Formal Modelling and Security Analysis of Bitcoin's Payment Protocol · arxiv.org
Substituting Proof of Work in Blockchain with Training-Verified Collaborative Model Computation · arxiv.org
Canonical LST: A Protocol-Native Liquid Staking Solution for Tezos · arxiv.org
Security, Latency, and Throughput of Proof-of-Work Nakamoto Consensus · arxiv.org
What is "fundamental"? · arxiv.org
Proof of Useful Intelligence (Poui): Blockchain Consensus Beyond Energy Waste · doi.org
Saving proof-of-work by hierarchical block structure · doi.org
Proof of Work With External Utilities · doi.org
Proof-of-Work versus Proof-of-Stake: A Comparative Economic Analysis · papers.ssrn.com
Crypto Proof of Work vs. Proof of Stake: What's the difference? · finance.yahoo.com
The cryptoeconomics of slashing - a16z crypto · a16zcrypto.com
Read transcript

Brian Reed: Eliza, hey — I have a question I couldn't shake all week, and it's genuinely bugging me in a way that feels like I'm missing something obvious.

Eliza Ward: That's almost always the best kind — go.

Brian Reed: Why would you deliberately waste electricity? Not accidentally — deliberately. Satoshi Nakamoto built Bitcoin in 2009 so that the only way to attack it is to burn more power than the honest network in real time. That's the design. The waste is the point.

Eliza Ward: Wait, so the energy cost isn't a byproduct of proof-of-work — it is proof-of-work.

Brian Reed: That's the claim, yeah. And then Ethereum runs on that exact model for years, and then does the Merge — just cuts the electricity requirement entirely, switches to proof-of-stake, validators lock up ETH instead of burning power. And the network keeps running.

Eliza Ward: Which sounds like a win. So what's the actual problem?

Brian Reed: The problem is — and this is what stopped me cold — proof-of-work chains are still 55.77% of total blockchain market cap after the Merge. The money didn't move. Which either means the market thinks Ethereum made a mistake, or... it means Bitcoin's energy model is holding something that proof-of-stake hasn't replaced yet.

Eliza Ward: And that's the actual puzzle — proof-of-work and proof-of-stake aren't competing efficiencies. They're different answers to the same question: what makes an attack too expensive to bother with? One answer is physics. The other is finance. Today we're working out whether those are actually equivalent.

Brian Reed: Physics versus finance — that's the frame. The physics side is where I land, because I think people hear 'electricity is the security' and they nod, but they don't actually feel why that's different from just... having a rule that says you can't cheat.

Eliza Ward: Okay, picture this: it's a lottery, but every single ticket costs real electricity to print. You want better odds? Buy more tickets. But you pay for every one, win or lose. That's Proof-of-Work. The puzzle is the ticket printer.

Brian Reed: But why not just make the tickets cheaper? Like, why keep the lottery expensive at all?

Eliza Ward: That's — yeah, that's exactly the question Satoshi Nakamoto answered in 2009. The cost isn't a tax on miners. It is the lock on the door. If you make it cheaper, an attacker can afford to reprint the whole history. The cost is what makes rewriting the chain — doing a 51% attack on Bitcoin — require matching the honest network's entire electricity bill in real time. You cannot conjure that from thin air.

Brian Reed: Wait — real time? Not just... accumulating resources and then launching?

Eliza Ward: Cumulative, actually — you'd have to replicate the honest network's cumulative computational work. Which means the longer Bitcoin runs, the more expensive that floor gets. It anchors to hardware and kilowatt-hours, not to — wait, this is the key part — not to anything happening inside the protocol. The cost lives outside the system.

Brian Reed: So the verification side is almost free — anyone can check the winner's hash instantly — but producing the answer is brutally expensive. The asymmetry is the whole point.

Eliza Ward: Right — hard to solve, trivial to verify. That gap is what you're buying when you spend the electricity. And that's why the energy expenditure isn't waste. It's the receipt.

Brian Reed: The receipt. So when people say Bitcoin wastes energy, the structural answer is: that's the security guarantee you paid for. The question is just whether you think the guarantee is worth the price.

Eliza Ward: And Ethereum looked at that receipt and said — we don't want to pay it anymore. The Merge. Ethereum Mainnet integrated with the Beacon Chain, the dedicated proof-of-stake consensus layer, and just... cut the electricity requirement. Gone.

Brian Reed: Right — and what replaced it is slashing. Validators lock up staked ETH as collateral. Misbehave, sign something you shouldn't, and the protocol confiscates a portion of what you put in. That's the new deterrent.

Eliza Ward: So instead of — wait — instead of the cost being external, physical, it's now on-chain capital. The penalty is inside the system.

Brian Reed: Which is where the trade gets uncomfortable. Picture a validator in Singapore, 2:47 in the morning, $850k staked. She gets a private message — 200 coordinated validators, join us, split the profits. The slashing penalty for signing two blocks is 32 ETH. She can do that math on a spreadsheet. In PoW, the equivalent question isn't math — it's whether you can physically replicate billions in electricity. You can't just decide to.

Eliza Ward: The cost is priced in rather than physically impossible to bear.

Brian Reed: Exactly that. And here's what Ethereum actually got in return — deterministic finality. Validators collectively and definitively confirm blocks at regular intervals. Bitcoin's six-block rule is a heuristic, not a guarantee. Ethereum PoS gives you a real guarantee. That's a genuine gain.

Eliza Ward: But the cost floor is now token price and protocol governance. If ETH price drops, so does the cost of an attack.

Brian Reed: The security anchor is on-chain. It's not independent of the system it's protecting — and that's a structurally different kind of trust. The Merge proved the energy savings are real. It didn't prove the security is equivalent. And actually, the nothing-at-stake problem and what slashing does or doesn't actually fix — these are the tensions that make this harder to resolve.

Eliza Ward: Yeah — that part I want to get to.

Brian Reed: So the nothing-at-stake problem is — let me see if I have this right — in PoW, if you vote on two competing forks simultaneously, you just burned electricity on the losing one. You paid. In PoS, without slashing, there's no equivalent cost. You can rationally vote on every fork at once because it costs you nothing.

Eliza Ward: That's it. Slashing is supposed to be the fix — misbehave, lose a chunk of your staked ETH. The 32 ETH penalty for signing two blocks is exactly that mechanism.

Brian Reed: So slashing fixes it.

Eliza Ward: Wait — that's actually where a16z Crypto's research lands uncomfortably. Slashing may be insufficient in parallel or multi-threaded block production architectures. It's not a lesser version of PoW's attack surface — it's a structurally new one that hasn't been stress-tested at Bitcoin's scale.

Brian Reed: Hang on — structurally new how? Because it feels like just... a different cost structure.

Eliza Ward: In PoW the physical cost is the deterrent — it's outside the protocol. In PoS the deterrent is inside it. Which means a sophisticated enough attack on the penalty mechanism itself — actually, no, the deeper issue is that slashing assumes single-threaded block production. Parallel architectures open coordination windows slashing wasn't designed to close.

Brian Reed: And the centralization piece compounds that. Large token holders get disproportionate influence over block production — it's validator centralization risk. Which sounds exactly like PoW mining pools, except the barrier is capital instead of hardware.

Eliza Ward: Right — and the proposed fix is liquid staking. Tezos built a protocol-native version, the Canonical LST, sTEZ, specifically so intermediaries don't become the centralization vector themselves. But protocol-native liquid staking is a governance intervention. You're solving a power asymmetry by handing the protocol more authority.

Brian Reed: So PoS security ends up depending entirely on how on-chain capital is distributed and governed — a trust model that's internal to the protocol, not anchored to anything outside it. That's the real distance from Bitcoin's 2009 design.

Eliza Ward: And that's — wait, that's where I actually landed on this. You started the whole thing asking why you'd deliberately waste electricity. And the answer is: you're not wasting it. You're buying the one thing that can't be faked from inside the system. Bitcoin has fifteen years of adversarial testing, nation-state scrutiny, multiple crashes — and the lock held. Ethereum's proof-of-stake hasn't faced that. The Merge ran clean, but a bull market with no sustained attack is not the same test.

Brian Reed: The honest version is — neither model has been broken in the worst-case scenario yet. PoW's failure mode is a 51% attack you can see coming because it costs electricity you have to physically acquire. PoS's failure modes are... different. Slashing math on a spreadsheet. Stake concentration that mirrors mining pools but lives on-chain. And there's a whole research direction called proof-of-useful-work trying to thread the needle — preserve the external cost anchor, redirect the computation toward something like AI training instead of pure hash puzzles — which is basically an acknowledgment that neither dominant model has fully solved the security-efficiency-centralization triangle. Nobody's declared victory. They're still working on it.

Eliza Ward: The receipt metaphor from earlier — I keep thinking about that. The question was never which model is more efficient. It was which receipt do you trust. Physics or finance. And the evidence that either one survives the worst case doesn't fully exist yet.

Brian Reed: Two genuine bets. Neither fully tested. That's — yeah, that's the honest place to stop.

Eliza Ward: Good question to have going in still unsettled. Worth it.