Proof of stake
Proof of stake selects and disciplines consensus participants using assets placed at risk under a network's validation rules.
Category: StakingStacked bars category cue
System record
Start with the economic purpose, participants, resources, and entitlements before studying implementation detail.
Why it exists
Proof of stake gives a network an economic way to choose block producers, confirm history, and penalize conflicting behavior without relying on proof-of-work mining.
Traditional-finance analogy
Performance bond for a shared settlement operator is the closest comparison recorded for this concept.
Where the analogy stops
- Validators collectively decide a replicated ledger rather than perform under one legal clearing authority.
- Stake weight, fork choice, finality, issuance, penalties, and social recovery are protocol-specific and can expose the network token itself.
Main actors
- ActorStaker or delegator
- ActorValidator operator
- ActorOther validators and full nodes
- ActorConsensus protocol
- ActorClient implementers
- ActorNetwork governance or social coordination
Assets and claims
Assets — controlled or transformed resources
Assets are resources the mechanism moves, holds, values, or transforms.
- AssetNative or protocol-approved staking asset
- AssetTransaction fees and protocol issuance
Claims — entitlements and corresponding dependencies
Claims are rights to value, repayment, redemption, control, or another party's performance; each depends on an obligation or system that must honor it.
- ClaimValidator balance and withdrawal right
- ClaimAccrued reward entitlement
Proof of stake uses assets placed at risk to select and discipline participants that validate a replicated ledger.
Why it exists
Section titled “Why it exists”A decentralized network needs a way to order proposed state transitions, reject invalid history, and make rewriting agreed history costly. Proof of stake ties consensus weight and fault penalties to assets recorded by the protocol rather than to proof-of-work computation.
Traditional-finance analogy
Section titled “Traditional-finance analogy”A performance bond for a shared settlement operator is a useful analogy. Unlike a regulated clearing operator, validators follow replicated fork-choice and finality rules without one legal authority. Stake weight, issuance, penalties, slashing, upgrades, and social recovery are defined by each network.
Actors, assets, and claims
Section titled “Actors, assets, and claims”Stakers commit the network’s accepted asset directly or through delegation. Validator operators run clients and control signing infrastructure. Other validators and full nodes independently verify messages and state transitions. Client teams implement protocol rules, while governance or social coordination can change software and recover from exceptional failures.
The staked token and paid fees are assets. An active validator balance, accrued rewards, exit status, and withdrawal right are protocol records and claims; they are not necessarily freely transferable while active.
Step-by-step mechanism
Section titled “Step-by-step mechanism”- Deposit or delegate an eligible asset and bind the protocol’s signing and withdrawal credentials.
- Wait through the network’s activation or validator-set update process.
- Select proposers, attesters, voters, or committees under the current consensus rules.
- Verify proposed state transitions and sign only messages consistent with local validation and slashing protection.
- Aggregate stake-weighted messages to choose history and, where supported, finalize checkpoints.
- Credit rewards and fees for qualifying duties; apply missed-duty penalties or severe-fault slashing.
- Process voluntary or forced exit, unbonding, and withdrawal under the protocol’s delay and queue rules.
State and flow view
Section titled “State and flow view”| Stage | Stake state | Validator authority | Claim state |
|---|---|---|---|
| Before activation | Deposited or delegated | Not yet active | Pending activation or delegation |
| Active | Bonded and exposed to protocol loss | Can perform assigned consensus duties | Rewards and penalties accrue |
| Exit requested | Still subject to stated rules | Duties end under network timing | Withdrawal remains delayed or queued |
| Withdrawn | Released to authorized destination | No active consensus weight from position | Claim is settled |
Capital flow moves stake, issuance, fees, rewards, penalties, and withdrawals. Claim flow records ownership or delegation of bonded stake, accrued rewards, pending exits, and any pooled staking entitlement. Information and control flow carry blocks, state roots, votes, fork choice, validator-set changes, and software upgrades. Return flow allocates user-paid transaction fees and protocol issuance to eligible stake under the network’s rules; issuance expands supply and dilutes other holders unless another mechanism offsets it. Risk flow begins with the bonded stake and can reach delegators, staking pools, liquid claims, and protocols that accepted those claims as collateral.
Return source and loss allocation
Section titled “Return source and loss allocation”Base returns can come from protocol issuance and transaction-related fees paid by users; networks may add other incentive sources. Issuance is also dilution to non-recipients. Operating costs, missed-duty penalties, slashing, token-price changes, and exit delays belong in net return. The validator’s bonded stake is the first intended loss-bearing asset for protocol-defined faults.
Engineer or auditor lens
Section titled “Engineer or auditor lens”Review domain-separated signatures, validator-set transitions, activation and exit queues, fork-choice and finality assumptions, conflicting-message evidence, reward and penalty accounting, withdrawal credentials, key rotation, client diversity, network partitions, upgrades, and exceptional recovery. A passing implementation test is not proof that consensus safety holds under every fault threshold or social-recovery scenario.
Ethereum’s proof-of-stake documentation describes one network’s validators, attestations, fork choice, finality, rewards, penalties, and slashing. Its duties and thresholds are examples rather than a universal proof-of-stake specification. The documentation was reviewed 2026-08-10.
Common misunderstandings
Section titled “Common misunderstandings”- “Staking is lending tokens to the network.” Direct staking commits assets to consensus duties and protocol loss conditions; no ordinary borrower necessarily exists.
- “More stake alone guarantees decentralization.” Operator, client, hosting, delegation, governance, and key concentration also matter.
- “Finalized means physically irreversible.” It means reversal violates the network’s stated economic and consensus assumptions; software and social actors still exist.
Next separate the human, software, key, and asset roles in validator.
Machine-readable model
Key equations
Canonical expressions come from the structured concept record. KaTeX renders the notation, while the plain-text expression and variable table keep its meaning and units inspectable without JavaScript. Read the narrative above for the model's domain, assumptions, and rounding rules.
This concept does not require one canonical equation. Its mechanism and state transitions remain the authoritative explanation; do not invent a formula merely to make the topic look quantitative.
Assurance contract
Security properties
These structured statements define desired behavior. Their stable IDs can bind tests, invariants, specifications, audit findings, or proof results without turning descriptive review advice into an assurance claim.
Desired · not evaluated: No test, audit, or proof result is implied until scoped evidence is linked to this property.
Only validly activated stake participates with the weight and duties defined by the current protocol state
Conflicting or invalid consensus messages cannot finalize state without the protocol's stated stake and fault assumptions
Rewards, penalties, slashing, activation, exit, and withdrawals reconcile to explicit validator balances
Signing authority, withdrawal authority, operator control, delegation, and governance powers remain distinguishable
Knowledge check
Quiz
Answer in your own words, then open the model answer.
What problem does Proof of stake exist to address?
Model answer
Proof of stake gives a network an economic way to choose block producers, confirm history, and penalize conflicting behavior without relying on proof-of-work mining.