Epoch (Blockchain)

In blockchain systems, an epoch is a fixed unit of time, or a fixed number of blocks or slots, that a network uses as a regular cycle for housekeeping tasks. At epoch boundaries, a network may select or reshuffle the validators responsible for producing blocks, calculate and distribute staking rewards, apply penalties, take a snapshot of who has staked what, change protocol parameters or mark blocks as final. Each network defines its own epoch length, from a few minutes to several days.

Epochs are most important in proof-of-stake networks, where the protocol must regularly decide which participants are eligible to validate. They are related to, but longer than, a slot, which is the short window in which a single block can be produced, and to block time. The word also has other meanings in computing: the "Unix epoch" is the reference date of 1 January 1970 from which many computer systems count time, and in machine learning an epoch is one full pass through a training dataset.

Think of a school year divided into terms. During each term, lessons happen every day, but some things only happen at the end of a term: reports are written, class lists are changed and prizes are handed out. A blockchain epoch works the same way. Blocks are produced constantly, but some decisions are taken only once per epoch.

Grouping these decisions makes the network easier to run. Everyone knows when the next change of validators will happen, rewards are worked out in regular batches, and the system has fixed points at which it can say with certainty that earlier records will not change.

• Ethereum. Time on Ethereum's consensus layer, coordinated by the Beacon Chain, is divided into 12-second slots, and 32 slots make one epoch of 6.4 minutes. Validators are assigned to committees for each epoch, attest to blocks once per epoch, and checkpoints at epoch boundaries are used to finalize the chain.
• Solana. Solana epochs last 432,000 slots, roughly two to three days depending on slot speed. The schedule of block leaders is set per epoch, and staking changes take effect at epoch boundaries.
• Cardano. Cardano uses five-day epochs of 432,000 one-second slots. Stake snapshots and reward calculations follow the epoch cycle, so delegated rewards arrive some epochs after the stake is delegated.
• Bitcoin. Bitcoin does not use the term formally, but some writers call the 2,016-block interval between mining difficulty adjustments, or the 210,000-block period between halvings, an epoch.

The duration of an epoch follows from the number of slots and the length of each slot:

For Ethereum, $32 \times 12 \text{ seconds} = 384$ seconds, or 6.4 minutes. Ethereum's finality mechanism usually needs two epochs: a checkpoint is justified when validators holding at least two-thirds of the stake vote for it, and it is finalized once the following checkpoint is also justified. A transaction therefore typically becomes final after about two epochs, or around 12.8 minutes, compared with the probabilistic finality of proof-of-work chains, where confidence grows gradually with each new block.

For people who stake, epochs set the rhythm of rewards and waiting times. Rewards are often calculated or paid per epoch, and requests to stake, unstake or move a delegation may take effect only at the next boundary, or after several epochs. On Ethereum, the number of validators that can join or leave per epoch is limited, so queues can form when demand is high, as discussed in the Dencun upgrade, which tightened the limit on new validators. Exchanges and wallets that offer delegated staking usually show the current epoch and estimated time to the next one.

Penalties follow the same cycle. On Ethereum, a validator that misses its attestations loses a small amount each epoch, and a validator that is slashed for signing conflicting messages is forced out over a long exit period measured in epochs, with an extra penalty that depends on how many others were slashed around the same time. For anyone staking through a third party, epoch timing therefore affects when rewards appear, how quickly funds can be withdrawn and how long an operator's mistakes take to show up in the account.

Short epochs let networks respond quickly, rotating validators often and finalizing blocks sooner, but they increase communication and computation, since the housekeeping happens more often. Long epochs reduce overhead and make reward accounting simpler but slow down changes in the validator set and delay finality. Frequent reshuffling of validators also improves security by making it harder for an attacker to predict or corrupt the group responsible for a given period. Designers balance these factors against the network's goals and the number of participants, and some networks have changed epoch parameters through upgrades.