Documentation Index
Fetch the complete documentation index at: https://docs.orbitflare.com/llms.txt
Use this file to discover all available pages before exploring further.
Parameters
This method does not require any parameters.
Response
The maximum number of slots in each epoch
The number of slots before beginning of an epoch to calculate a leader schedule for that epoch
Whether epochs start short and grow
First normal-length epoch, log2(slotsPerEpoch) - log2(MINIMUM_SLOTS_PER_EPOCH)
MINIMUM_SLOTS_PER_EPOCH * (2.pow(firstNormalEpoch) - 1)
Code Examples
Basic Request
curl http://fra.rpc.orbitflare.com?api_key=YOUR-API-KEY -X POST -H "Content-Type: application/json" -d '{
"jsonrpc": "2.0",
"id": 1,
"method": "getEpochSchedule"
}'
Using web3.js
import { Connection } from '@solana/web3.js';
const connection = new Connection('http://fra.rpc.orbitflare.com?api_key=YOUR-API-KEY');
const epochSchedule = await connection.getEpochSchedule();
console.log(epochSchedule);
Using Python
from solana.rpc.api import Client
client = Client("http://fra.rpc.orbitflare.com?api_key=YOUR-API-KEY")
response = client.get_epoch_schedule()
print(response)
Notes
- Returns epoch schedule information from the cluster’s genesis configuration
- The returned data is static and does not change for a given network/cluster
- Useful for calculating epoch boundaries and leader schedule timing
- The warmup parameter indicates if epochs start short and grow to their full size
Best Practices
- Cache this information locally as it does not change
- Use the returned values to calculate epoch transitions
- Use firstNormalEpoch and firstNormalSlot for epoch timing calculations
- Handle network errors and retry when appropriate