curl --request POST \
--url https://nd-326-444-187.p2pify.com/9de47db917d4f69168e3fed02217d15b \
--header 'Content-Type: application/json' \
--data '
{
"id": 1,
"jsonrpc": "2.0",
"method": "minimumLedgerSlot",
"params": []
}
'{
"jsonrpc": "<string>",
"id": 123,
"result": 123
}curl --request POST \
--url https://nd-326-444-187.p2pify.com/9de47db917d4f69168e3fed02217d15b \
--header 'Content-Type: application/json' \
--data '
{
"id": 1,
"jsonrpc": "2.0",
"method": "minimumLedgerSlot",
"params": []
}
'{
"jsonrpc": "<string>",
"id": 123,
"result": 123
}minimumLedgerSlot method returns the lowest slot that the node has information about in its ledger.
As validators prune old ledger data, this value increases over time. This method is useful for determining how far back in history a node can serve data.
result (integer) — the minimum ledger slot number available on the node.minimumLedgerSlot is in determining whether a node can serve historical data for a given slot. Before requesting block or transaction data for a specific slot, you can check minimumLedgerSlot to verify the data is still available. This is especially relevant when deciding between a full node and an archive node.Was this page helpful?