~$ crypto-under-the-hood

# The machinery behind the coins

~/notes / consensus and blocks

Proof of Work vs Proof of Stake, Without the Tribalism

Two answers to the same question. Each buys security with a different resource, and each has a failure mode the other does not.

Ivan Kruse · · 3 min

Both mechanisms solve one problem: how do machines that do not trust each other agree on a single history without a referee.

They differ in what makes attacking expensive.

Proof of work

Producing a block requires finding a value whose hash meets a difficulty target. There is no shortcut; you try until you find one. That costs electricity and hardware.

Security model. Rewriting history requires redoing the work of every block since the point you want to change, faster than the rest of the network is extending the current chain. The cost is external: energy and machines that must be bought and powered in the physical world.

Strengths. The cost is real and outside the system. An attacker cannot conjure hash power from the asset itself. The rules are simple and have run without a consensus failure for a long time.

Weaknesses. Energy consumption is large and visible. Mining concentrates where electricity is cheapest, creating geographic and regulatory exposure. Security is paid for by continuous issuance, which must eventually be replaced by fees.

Proof of stake

Block production rights are assigned to participants who lock up the asset as collateral. Misbehaviour is punished by destroying part of that collateral.

Security model. Attacking requires controlling a large share of the staked asset, and doing so visibly costs you that stake. The cost is internal: it is denominated in the asset being secured.

Strengths. Energy consumption is negligible. Attacks are punished directly rather than merely outcompeted. Faster finality is achievable.

Weaknesses. The security budget is denominated in the asset it secures, which is circular in a way proof of work is not. Staking tends to concentrate in large providers. The protocol is considerably more complex, and complexity is where bugs live.

The comparison table

Proof of work Proof of stake
Cost of attack External: energy and hardware Internal: the staked asset
Energy use Large Negligible
Finality Probabilistic, strengthens with depth Explicit after a defined interval
Concentration risk Mining pools and cheap power regions Large staking providers
Protocol complexity Low High
Recovery from a successful attack Social coordination Slashing plus social coordination

The arguments that are not serious

“Proof of work wastes energy.” It converts energy into security. Whether that is a good trade is a legitimate question; calling it waste assumes the answer.

“Proof of stake is just the rich getting richer.” Rewards are proportional to stake, which is also true of every interest-bearing instrument. The distributional question is real and is not unique to this design.

“One is obviously more decentralised.” Both concentrate, through different mechanisms. Mining concentrates through capital and electricity access; staking concentrates through convenience and liquid staking providers. Measure it rather than assert it.

What actually matters for a holder

Neither mechanism has failed catastrophically on a major network. Both have identified weaknesses that have not been exploited at scale.

The practical consequences are narrower: finality timing affects how long you wait before treating a transaction as settled, and the security model affects what a long-term attack would cost.

Finality timing is why deposit crediting differs between assets at any venue, and platforms such as exchanges that let you specify the network publish the confirmation counts they require for each chain.

For everything else, the choice between them is not a question you answer by holding an opinion. It is a design trade-off with costs on both sides, and the tribalism around it obscures that both have been running production networks successfully for years.

# Corrections and technical nitpicks are welcome. Send them over. They get published with the fix.

consensusproof-of-workproof-of-stake

# related notes