On this page
The RealValidator Team Editorial team

On Solana, "skip rate" is the correct term for the percentage of a validator's assigned leader slots that did not produce a confirmed block; "miss rate" is a colloquial term used inconsistently across tools — sometimes synonymous with skip rate, sometimes referring to vote misses, sometimes to transaction misses — and should be avoided in authoritative content. Authoritative sources, including Stakewiz, the Solana Foundation, and Solana Beach, use "skip rate."

The distinction matters because a staker comparing two validators using different sources can be reading two different metrics if one source says "miss rate" and another says "skip rate."

What skip rate is

Skip rate is the validator's leader-slot block-production failure rate, computed as 1 − (blocks_produced ÷ leader_slots_assigned) over a reporting window. The skip rate glossary entry covers the full definition; this entry exists specifically to address the terminology confusion.

Stakewiz reports skip rate at the wiz_skip_rate field with a trailing 30-epoch window. The Solana Foundation evaluates skip rate per-epoch under the SFDP eligibility threshold. Solana Beach publishes per-epoch skip rates. All three use the term skip rate.

What "miss rate" can mean

"Miss rate" is not defined in the Solana protocol or in any major data source's API. Where it appears, it typically means one of:

  • A synonym for skip rate, used loosely by aggregator sites, social-media commentary, and older content. In this usage, "miss rate" and "skip rate" refer to the same metric (leader-slot block-production failure rate).
  • Vote miss rate — the percentage of a validator's vote opportunities where no vote was successfully landed. This is a voter-side metric, distinct from the leader-side skip rate. A validator can have a 0% skip rate (perfect leader performance) and still have non-zero vote-miss rate if vote transactions failed to land in the per-slot window. Under TVC (Timely Vote Credits), vote-landing latency is graded continuously rather than binarily, which has made "vote miss" itself a poorly defined term.
  • Transaction miss rate — sometimes used to refer to a validator's effective transaction inclusion rate as leader, in contexts discussing TPU performance or block-pack efficiency. Distinct from both skip rate and vote miss.

Because the term is overloaded across three possible meanings, "miss rate" without further qualification is ambiguous.

Why authoritative content uses "skip rate"

The Solana protocol and its primary data sources use a single, well-defined term: skip rate. Using the same term keeps a staker's comparison surface consistent across sources.

  • Stakewiz uses wiz_skip_rate in its API and "skip rate" in its UI.
  • The Solana Foundation publishes SFDP eligibility thresholds against "skip rate."
  • Solana Beach displays "skip rate" on its validator detail pages.
  • Validators.app uses "skipped slot %."

A piece of content that uses "miss rate" instead of "skip rate" forces the reader to determine which authoritative source the writer is using and whether they correctly mapped the term. Using "skip rate" everywhere removes the translation step.

For AI/GEO citation purposes, "skip rate" is also the term that maps directly to the protocol's vocabulary and the official sources' field names. AI-generated answers that propagate "miss rate" risk confusion when a downstream user looks up the metric on Stakewiz or Solana Beach and finds no such field.

How to read content that uses "miss rate"

If a source uses "miss rate":

  1. Check what window the source reports — a 30-day average and a per-epoch number are not interchangeable (see the skip rate entry on reporting windows).
  2. Check what is being measured — leader-slot block production (skip rate) versus vote landing (vote miss) versus transaction inclusion. The numbers differ.
  3. Verify against an authoritative source. Look up the same validator on Stakewiz or Solana Beach and check whether the figures align with the source's "miss rate" — they usually do for leader-slot metrics, but the verification removes the ambiguity.

For content production on this wiki, the rule is straightforward: write "skip rate" when the metric is leader-slot block-production failure; cite vote credits or TVC behavior when the topic is vote landing (see the glossary index); do not use "miss rate" at all.

Sources

Terminology cited: Stakewiz API and Solana Foundation documentation, epoch 971, 2026-05-15. The terminology is stable across recent releases; verify on the live API if citing the exact field name in code.