`epochHistory`

Recent consensus epochs and the current epoch

Each entry records where an epoch starts, as both a global block number and a snapshot version. Entries are ordered oldest first, so the last one is the current epoch.

POST/infotype epochHistory

Map block numbers to consensus epochs.

Request body

typestringrequired

Request example

curl -X POST https://rpc.txflow-testnet.xyz/info \
  -H "Content-Type: application/json" \
  -H "x-api-version: 2026-08-16" \
  -d '{
  "type": "epochHistory"
}'

Try it

POST https://rpc.txflow-testnet.xyz/info

Response · EpochHistoryResponse 200

codeinteger

`0` on success.

dataEpochHistoryResponse

currentEpochinteger · int64

Current epoch. Equals the `epoch` of the last entry in `epochs`.

epochsEpochHistoryEntry[]

Recent epochs in ascending order, oldest first.

successboolean

`false` on error, with `code` set and the text in `message` instead of `data`.

Response example

{
  "success": true,
  "code": 0,
  "data": {
    "currentEpoch": 0,
    "epochs": [
      {
        "blockNumOffset": 0,
        "epoch": 0,
        "previousHash": "",
        "snapshotVersionOffset": 0,
        "validatorIndex": 0,
        "validatorsCount": 0
      }
    ]
  }
}