Encyclopedia Ethereum · Entry 15
Ethereum proof of stake: blocks, votes and checkpoint finality
In this article
At a glance
Key facts
One role proposes; other participants verify and attest
A selected proposer supplies a block for a slot. Other nodes check execution, and validators attest under the consensus rules. A slot can be missed, so a fixed schedule does not guarantee that every slot contains a block.
Time is grouped into epochs of 32 slots. At 12 seconds per slot that is 384 seconds, or 6 minutes 24 seconds, per scheduled epoch. This is arithmetic from the documented parameters, not a guaranteed payment completion time.
Example: two-thirds refers to weight, not two-thirds of users
Imagine total active voting weight normalized to 300 units. A two-thirds checkpoint supermajority requires at least 200 units supporting the relevant link. Two hundred website users are irrelevant if they do not represent that stake weight.
Checkpoint justification and finalization follow the sequence of qualifying links. A wallet displaying a recent transaction receipt is reporting execution in a block; it should not silently label that observation finalized.
Conflicting finality implies a serious consensus failure
Two conflicting two-thirds supermajorities must overlap by at least one-third of the total weight. This is the intuition behind Ethereum’s accountable-finality security argument: conflicting finalized histories imply substantial slashable voting behavior.
It is an economic and protocol security property, not a claim that software bugs or extraordinary recovery decisions are logically impossible. Use finalized as a specific consensus status rather than a synonym for zero conceivable risk.
Keep inclusion, the current head and finality separate
A transaction can appear in an included block before that block is finalized. An RPC query can distinguish latest, safe and finalized block contexts where supported; a receipt’s successful status describes execution rather than the block’s consensus status.
If finality stalls, new head blocks may still be observed. An interface should report what it actually checked instead of turning a growing block count into a claim of finalization. Preserve the block reference and observation time for a reproducible statement.
Direct answers
Questions people ask
Does one Ethereum block mean finality?
No. Inclusion and finalization are distinct. Finality depends on the checkpoint voting process, not merely the existence of one receipt.
Does every 12-second slot produce a block?
No. Slots schedule block opportunities, but a proposer can miss its turn and leave a slot without a block.
Is finality based on one vote per account?
No. Validator votes carry stake-based weight. Counting accounts, users or computers does not reproduce the protocol’s supermajority calculation.
Inspect the evidence
The answer and key facts have stable claim links. These records retain the scope and qualification when reused.
Ethereum validators propose blocks and vote using staked ETH. Fork choice selects the current chain head; checkpoint voting establishes finality. Under the documented rules, slots are 12 seconds and epochs contain 32 slots. Inclusion in a block is earlier than finalization, and finality can stall when participation is insufficient.
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T18:16:35.976Z.
Link to this claimTiming unit: 12-second slots; 32 slots per epoch
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T18:16:35.976Z.
Link to this claimVoting weight: Stake weight matters, not simply the count of people
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T18:16:35.976Z.
Link to this claimDistinction: Chain-head selection and finality are related but different
Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T18:16:35.976Z.
Link to this claimRevision history
- — First publication after primary-source research and independent automated verification.
- — Expanded explanation: Keep inclusion, the current head and finality separate. Worked examples are illustrative; source checks and independent verification are recorded separately.
On the Understand Ethereum path · You have reached the final entry in this path.
On the Follow a transaction path · You have reached the final entry in this path.
Source register
Sources and references
Retrieval dates and locators are recorded individually.- Proof of stakeethereum.org contributors
Supports 12-second slots, 32-slot epochs, stake-weighted checkpoint voting and block verification.
Locator: Validators; transaction execution; finality; fork choice · Version / scope: dcc900ff125891da5b6c723b905a7113cf1bd864 · Retrieved: 2026-10-02T14:35:43.818781+00:00Open source - Gasperethereum.org contributors
Supports fork choice versus checkpoint finality and the at-least-one-third conflicting-vote overlap argument.
Locator: What is finality; fork choice; inactivity leak · Version / scope: dcc900ff125891da5b6c723b905a7113cf1bd864 · Retrieved: 2026-10-02T14:35:43.699844+00:00Open source - Nodes and clientsethereum.org contributors
Supports execution/consensus client roles, independent validation, RPC services and node-versus-validator distinctions.
Locator: What are nodes and clients; benefits to you; alternatives · Version / scope: dcc900ff125891da5b6c723b905a7113cf1bd864 · Retrieved: 2026-10-02T14:35:47.541421+00:00Open source - Proof-of-stake rewards and penaltiesethereum.org contributors
Supports ordinary nonparticipation penalties versus slashable conflicting proposals/votes. Inconsistent numeric examples are not reused.
Locator: Penalties; slashing; inactivity leak · Version / scope: dcc900ff125891da5b6c723b905a7113cf1bd864 · Retrieved: 2026-10-02T14:35:43.680530+00:00Open source - Ethereum JSON-RPCethereum.org contributors
RPC response fields, transaction receipts, call simulation and log filtering.
Locator: eth_getTransactionByHash; eth_getTransactionReceipt; eth_call; eth_getLogs; eth_getCode; eth_estimateGas; eth_getBalance; eth_getStorageAt; eth_getTransactionCount; default block parameter · Retrieved: 2026-10-02T17:03:42.060ZOpen source - Ethereum transactionsethereum.org contributors
Signed transaction fields, nonces, propagation, inclusion and transaction types.
Locator: The transaction lifecycle; Typed transaction envelope · Retrieved: 2026-10-02T17:03:41.854ZOpen source
Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.
Editorial method and correctionsDegrees of Satoshi editorial project. “Ethereum proof of stake: blocks, votes and checkpoint finality.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/ethereum-proof-of-stake-finality/