getEpochSchedule

POSTSlots & EpochsAll plans

Returns the cluster's epoch-length parameters.

Try itSends a real request from your browser to the selected region.
POST
/

getEpochSchedule returns the fixed parameters for how slots group into epochs: slots per epoch, whether the cluster is in its initial warmup period, and the first epoch/slot where normal-length epochs began. These are set at genesis and do not change, unlike the live numbers in getEpochInfo.

A single call supports converting between absolute slot numbers and epoch/epoch-relative-slot pairs locally, instead of calling getEpochInfo repeatedly.

Plans & rate limitsAll plans
Free5/s
Operator50/s
Blade Runner200/s
Nexus500/s

Parameters

This method takes no parameters.

Result

resultobject

The cluster's epoch schedule parameters.

Show propertiesProperties
slotsPerEpochintegerrequired

Number of slots in a normal (post-warmup) epoch.

leaderScheduleSlotOffsetintegerrequired

Number of slots before an epoch boundary that its leader schedule is computed.

warmupbooleanrequired

Whether epochs start short and grow geometrically toward slotsPerEpoch (true only very early in a fresh cluster's life).

firstNormalEpochintegerrequired

First epoch with the full slotsPerEpoch length.

firstNormalSlotintegerrequired

First absolute slot belonging to firstNormalEpoch.

Notes

  • On mainnet-beta, warmup: false and firstNormalEpoch: 0 mean every epoch has always been the full 432,000 slots.