Mining, staking, and consensus

Agreement under adversarial conditions

A public network cannot assume its participants are honest, cannot verify who they are, and cannot stop anyone from joining. Consensus rules exist to produce a single agreed history anyway. They define how a candidate block is proposed, how others check it, and how the network chooses between competing versions.

Both major approaches work by attaching a real cost to participating dishonestly. Proof of work requires expending computation, so producing an alternative history means redoing that work faster than everyone else combined. Proof of stake requires bonding the network's own asset, so misbehaving can trigger penalties that destroy part of the bond.

The security claim is therefore economic rather than absolute. It says that attacking the network should cost more than the attack can plausibly earn. That holds only while participation stays sufficiently distributed—which is why concentration among a few miners, pools, or staking providers is a live concern rather than a theoretical one.

Rewards have a source

Participants receive newly issued units and transaction fees. Those payments are not free money appearing from nowhere; they are compensation for capital, equipment, and risk, and they dilute existing holders in proportion to the issuance.

For mining, the offsetting costs are hardware, electricity, cooling, downtime, and the falling productivity of equipment as competition increases. For staking, they are lock-up periods, slashing penalties for misbehaviour or prolonged downtime, operator or pool fees, and the plain fact that the reward is paid in an asset whose price can fall further than the reward is worth.

Treat any advertised staking yield the way you would treat any other yield: ask who pays it, in what asset, under what conditions it stops, and what you give up in liquidity to receive it. A double-digit return quoted in a token that has no independent demand is a statement about issuance, not about profit.

• Which asset is the reward paid in?
• Is there a lock-up or unbonding delay, and how long?
• What behaviour triggers a penalty, and who bears it?
• If a provider stakes on your behalf, who holds the keys?

Avoid category errors

Consensus secures one specific thing: agreement about the network's transaction history, under stated assumptions. It is routinely stretched to cover claims it does not support.

A robust consensus mechanism does not make a smart contract free of bugs, does not make a token valuable, does not make a wallet user private, and does not protect anyone who approves a malicious transaction. Almost every loss a beginner is likely to suffer happens in a layer the consensus mechanism never touches.