On this page
The RealValidator Team Editorial team

A Solana epoch is a fixed window of 432,000 slots — approximately 2 days of actual wall-clock time on the current network — that serves as the protocol's primary clock for stake activation, leader scheduling, inflation reward distribution, and commission rate changes. At ~400ms per slot, a single epoch maxes out at roughly 2 days, 8 hours theoretically; current mainnet performance keeps it closer to a flat 2 days.

The epoch is the discrete unit on which most validator-relevant state changes take effect. Newly delegated stake does not earn rewards in the epoch it is delegated; it activates at the next epoch boundary (see stake activation). Commission rate changes submitted by a validator's withdraw authority apply to the next epoch's reward distribution, not the current one. Inflation rewards mint at the end of each epoch and credit to stakers' accounts during the first ~150 slots of the following epoch.

The leader schedule is precomputed per epoch

At the start of each epoch, the protocol generates a complete leader schedule for the entire epoch's 432,000 slots, sampling validators weighted by their active stake. A validator with 0.087% of network stake is assigned roughly 376 leader slots over the epoch. This schedule is fixed for the epoch; mid-epoch stake changes do not re-randomize it, which is why stake delegated mid-epoch cannot affect that epoch's leader assignments.

Why every metric citation must name the epoch

Most validator-level metrics are computed against a per-epoch or trailing-N-epoch window:

  • Skip rate is reported per-epoch and as a 30-epoch trailing average (per Stakewiz).
  • Vote credit ratio under TVC is reported per-epoch; SFDP evaluates it as ≥97% of cluster average per-epoch.
  • APY is computed from inflation rewards distributed across recent epochs; the figure changes each epoch as the inflation schedule decays (~15% per year toward the 1.5% long-term floor).
  • Commission rate is the rate in effect for a specific epoch; a validator can change it between epochs.

A statement like "Validator X has a 6.1% APY" is incomplete without the epoch number — the figure was different two epochs ago and will be different two epochs from now. The wiki's editorial standard requires the epoch number on every percentage citation; the styleguide forbids APY or commission figures without an epoch tag.

Epoch numbering

Solana epochs are numbered sequentially from network genesis. Mainnet beta launched at epoch 0 in March 2020; the network is at epoch 971 as of 2026-05-15 (per Solana Beach). Epoch numbers are observable on-chain via the getEpochInfo RPC method, returning the current epoch and slot offset within it.

The epoch number is the easiest way to verify the freshness of a metric. A profile citing skip rate "as of epoch 742" is approximately 458 epochs (roughly 2.5 years) stale at epoch 971 and unsuitable for current-decision use.

Terminology traps

  • An epoch is not 2.5 days on the current network. The 2.5-day figure is the theoretical maximum at exactly 400ms per slot; actual slot times average somewhere between 380-420ms depending on cluster performance, so realized epochs are closer to 2 days. The styleguide uses "approximately 2 days actual on the current network, ~2.5 days theoretical maximum."
  • An epoch is not a "round." Some sources use "round" loosely; Solana's protocol-defined unit is the epoch.
  • Slot ≠ epoch. A slot is ~400ms; an epoch is 432,000 slots.

Sources

Current epoch reference: epoch 971, 2026-05-15. Network slot timing averages used in this entry reflect Solana Beach cluster data on that date.