getEpochSchedule

getEpochSchedule returns the parameters that define how the cluster maps slots to epochs. These values come from the cluster's genesis configuration and do not change for the life of the cluster, so the response is effectively static — you can fetch it once at startup and cache it indefinitely.

Use it to convert between slots and epochs on the client side without an extra round trip: knowing slotsPerEpoch, firstNormalEpoch, and firstNormalSlot lets you compute which epoch any given slot belongs to. The warmup flag and the leader-schedule offset describe the cluster's early bootstrap behavior, where epochs ramp up in length before reaching the steady-state slotsPerEpoch.

This method takes no parameters and is not commitment-sensitive — the schedule is the same regardless of slot or finality.

This method takes no parameters. Send an empty params array.

The example above reflects a mainnet-style genesis config: 432,000 slots per epoch with warmup disabled, so the first normal epoch and slot are both 0.

Errors are returned in the standard JSON-RPC error envelope. See the shared errors reference for the full envelope shape and shared codes.

JavaScript (fetch)

const res = await fetch("https://api.triport.io/v1/sol", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.TRIPORT_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    jsonrpc: "2.0",
    id: 1,
    method: "getEpochSchedule",
    params: [],
  }),
});


const { result } = await res.json();


// Convert an arbitrary slot to its epoch (warmup disabled).
const slot = 348392041;
const epoch = Math.floor(
  (slot - result.firstNormalSlot) / result.slotsPerEpoch
) + result.firstNormalEpoch;
console.log(`Slot ${slot} is in epoch ${epoch}`);

TypeScript SDK (@triport/sdk)

import { TriportClient } from "@triport/sdk";


const client = new TriportClient({ apiKey: process.env.TRIPORT_API_KEY });


const schedule = await client.solana.getEpochSchedule();


console.log(`Slots per epoch: ${schedule.slotsPerEpoch}`);
console.log(`Warmup: ${schedule.warmup}`);

Python (triport-sdk)

import os
from triport import TriportClient


client = TriportClient(api_key=os.environ["TRIPORT_API_KEY"])


schedule = client.solana.get_epoch_schedule()


print(f"Slots per epoch: {schedule['slotsPerEpoch']}")
print(f"Warmup: {schedule['warmup']}")

• Cache it: the schedule is fixed for the life of the cluster. Fetch once and reuse rather than calling on every request.
• No commitment parameter: unlike most read methods, the result does not depend on slot or commitment, so there is no config object.
• Warmup epochs: when warmup is true, epochs before firstNormalEpoch are shorter than slotsPerEpoch; account for firstNormalSlot when mapping early slots to epochs.
• Related methods: use getEpochInfo for the current epoch, slot, and progress, and getSlot to read the slot the cluster has currently reached.