Attestations

What are Attestations?

Attestations are the fundamental mechanism by which validators participate in proof-of-stake consensus. Each attestation represents a validator’s vote on the current state of the blockchain, signaling which blocks they believe should become part of the canonical chain. Without attestations, proof-of-stake networks would have no way to reach agreement on the correct chain history, making them essential to the security and operation of modern blockchain protocols.

The attestation mechanism serves two critical consensus protocols simultaneously. The first is LMD-GHOST (Latest Message Driven Greediest Heaviest Observed SubTree), which determines the head of the chain by following the fork with the most accumulated validator votes. Each validator’s most recent attestation counts as their vote, and the protocol selects the chain tip that has garnered the greatest support. This approach ensures that the network converges on a single chain even when temporary forks occur.

The second protocol that attestations power is Casper FFG (Friendly Finality Gadget), which provides economic finality to the chain. While LMD-GHOST determines which blocks are likely canonical, Casper FFG determines which blocks are irreversibly final. Validators cast votes on checkpoint boundaries, and when enough validators agree, those checkpoints become justified and eventually finalized. This dual-purpose design allows attestations to efficiently serve both fork choice and finality in a single cryptographic signature.

Attestation Contents

Every attestation contains several key pieces of information that enable both consensus protocols to function. The source vote references the most recent justified checkpoint that the validator is aware of, serving as the starting point for the Casper FFG vote. The target vote points to the checkpoint at the current epoch boundary, representing where the validator believes the chain should be finalized next. Together, these source and target votes form the Casper FFG component of the attestation.

The head vote specifies which block the validator believes should be the current head of the chain, directly feeding into the LMD-GHOST fork choice rule. This vote includes the slot number and block root of the attested block, allowing other nodes to count this validator’s support for that particular chain branch. The head vote typically points to a block in the current or recent slots, reflecting the validator’s view of the most recent valid block.

Attestations also include committee information that identifies which group of validators the attester belongs to. In each slot, validators are divided into committees, and each committee is responsible for attesting to blocks in that slot. The attestation specifies the committee index and includes an aggregation bitfield showing which validators within that committee have signed. This committee structure enables parallel processing of attestations and helps distribute the workload across the network.

Attestation Aggregation

Processing individual attestations from every validator would create an enormous burden on the network, as thousands of validators attest in each slot. Attestation aggregation solves this scalability challenge by combining multiple attestations with identical vote contents into a single aggregated attestation. This aggregation relies on BLS signature schemes, which have the unique property that multiple signatures on the same message can be combined into a single signature that verifies against the combined public keys.

Aggregators are validators selected through a verifiable random process to collect and combine attestations from their committee. When multiple validators vote for the same source, target, and head, their individual signatures can be merged into one aggregated signature. The aggregated attestation includes a bitfield indicating which validators contributed to the combined signature, allowing verifiers to determine the total stake weight behind the vote without processing each signature individually.

This aggregation mechanism dramatically reduces the data that must be propagated through the network and included in blocks. Instead of thousands of individual attestations consuming block space, a small number of aggregated attestations can represent the same voting information. The efficiency gains enable proof-of-stake networks to support large validator sets while maintaining reasonable bandwidth and storage requirements, making decentralization more accessible.

Attestation Rewards

Validators earn rewards for producing correct attestations that align with the eventual canonical chain. The reward structure incentivizes three types of correct votes: correct source votes that match the justified checkpoint, correct target votes that match the finalized checkpoint target, and correct head votes that match the canonical chain head. Each component contributes to the validator’s total reward, encouraging accurate participation in both Casper FFG and LMD-GHOST.

Inclusion delay plays a significant role in attestation rewards, penalizing validators whose attestations take longer to be included in a block. An attestation included in the immediately following slot earns full rewards, while attestations included later receive proportionally reduced rewards. This mechanism incentivizes validators to maintain good network connectivity and encourages block proposers to include attestations promptly, improving overall network health and consensus speed.

Validators who produce incorrect attestations do not receive rewards for the incorrect components and may face penalties in certain circumstances. Attesting to the wrong head or target results in forfeited rewards rather than direct slashing, as these mistakes might result from network latency rather than malicious intent. However, validators who produce contradictory attestations that could facilitate attacks face severe slashing penalties, creating a strong economic deterrent against Byzantine behavior.

Attestations and Finality

The path to finality in proof-of-stake networks depends entirely on attestations reaching supermajority thresholds. A supermajority is defined as two-thirds of the total staking balance, representing overwhelming consensus among validators. When attestations from validators controlling at least two-thirds of the stake agree on a source-to-target vote, the target checkpoint becomes justified, marking it as a strong candidate for finalization.

Justification is the first step toward finality, indicating that the network has reached strong agreement on a checkpoint. Once a checkpoint is justified and the next checkpoint is also justified with the first as its source, the earlier checkpoint becomes finalized. This two-phase process ensures that finality only occurs when validators have demonstrated sustained agreement across multiple epochs, providing robust protection against chain reorganizations.

Finalized checkpoints represent irreversible consensus that cannot be undone without at least one-third of validators being slashed. The economic guarantee behind finality comes directly from the attestations: if conflicting chains both achieved finality, it would mean validators controlling at least one-third of the stake produced contradictory attestations. Since such behavior triggers slashing of their entire stake, the cost of reverting finalized blocks becomes prohibitively expensive, giving users confidence that finalized transactions will never be reversed.