getEpochSchedule

getEpochSchedule is a Solana JSON-RPC method that returns the epoch schedule baked into the cluster's genesis configuration — the fixed rules that say how slots map to epochs on the chain securing SOL. The response includes slotsPerEpoch, the leaderScheduleSlotOffset, the warmup flag, and the firstNormalEpoch / firstNormalSlot markers that bound the early warmup period. Because it comes from genesis, the values never change for a given cluster. Send it as a JSON-RPC 2.0 POST with an empty positional params array to https://solana.therpc.io/YOUR_API_KEY.

Use cases

• Convert freely between slots and epochs when running historical queries over the SOL ledger, using slotsPerEpoch as the divisor.
• Compute which epoch a given absolute slot falls into — for slots past firstNormalSlot it is simply firstNormalEpoch + (slot - firstNormalSlot) / slotsPerEpoch.
• Account for the warmup period so early epochs map correctly, since they were shorter before the schedule reached its normal length.

Parameters

Este método no acepta parámetros. Pasa un array vacío [].

Response

Example request

1curl https://solana.therpc.io/YOUR_API_KEY \
2  -X POST \
3  -H "Content-Type: application/json" \
4  -d '{
5  "jsonrpc": "2.0",
6  "id": 1,
7  "method": "getEpochSchedule",
8  "params": []
9}'

Errors & troubleshooting

Common pitfalls

• When warmup is true, early epochs ramp up in length and a naive slot / slotsPerEpoch will be wrong — anchor your math on firstNormalEpoch and firstNormalSlot for exact results.
• This is static genesis config that never changes for a cluster, so fetch it once and cache it rather than calling it on every request.

Supported networks

• Mainnet
• Devnet

See also

• getEpochInfo
• getLeaderSchedule