Proof of stake is a family of consensus mechanisms in which protocol participants commit value under defined rules and take part in ordering or confirming blocks. The exact design differs from network to network.

Educational scope. This guide explains technology and terminology. It does not offer investment advice, trading signals, wallet services, exchange services, staking services or projected financial returns.

What you'll understand

  • Distributed networks need a way to decide which valid history to follow.
  • A validator typically runs network software, remains online, verifies data and may be selected to propose or attest to blocks.
  • Many proof-of-stake systems change participant balances according to correct or incorrect behavior.
  • Some proof-of-stake systems provide explicit finality rules.

Why proof of stake exists

Distributed networks need a way to decide which valid history to follow. Proof of stake uses protocol-defined economic commitments rather than the energy-intensive hashing competition associated with proof of work.

The goal is consensus security, not the creation of a consumer investment product.

Validators and attestations

A validator typically runs network software, remains online, verifies data and may be selected to propose or attest to blocks. Some protocols divide responsibilities across committees or epochs.

Terms such as validator, delegator, nominators and attesters can mean different things on different networks.

Rewards and penalties are protocol mechanics

Many proof-of-stake systems change participant balances according to correct or incorrect behavior. These changes are commonly called rewards and penalties. They are part of network security design and should not be interpreted as a guaranteed yield.

Actual outcomes can be affected by uptime, protocol changes, penalties, service fees, token price changes and other risks.

Finality

Some proof-of-stake systems provide explicit finality rules. Once enough protocol participants have attested to a checkpoint, reversing it may require severe protocol violations by a large fraction of stake.

Finality models vary, so statements about one network should not automatically be applied to another.

Key takeaway

The clearest way to understand this topic is to separate the protocol, the digital asset, the software interface and any third-party service. Each layer has different responsibilities, dependencies and risks.