> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chainstack.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Extended history

> Extended Global Nodes are full nodes that keep more history than a standard full node of the protocol, but not a complete archive. Requests are billed the same as on a Full node.

An Extended [Global Node](/docs/global-elastic-node) is a full node that keeps more history than a standard full node of the same protocol, but not a complete archive from genesis. Extended does not change request-unit billing.

## Which nodes are Extended

Extended applies only to Global Nodes. The protocols and networks that offer Extended Global Nodes show Extended in the Global Node Mainnet Support and Global Node Testnet Support columns on [Networks](/docs/protocols-networks). Each protocol's history depth is listed in [How much history each protocol keeps](#how-much-history-each-protocol-keeps).

## Billing

Extended is not a separate billing class. Requests to an Extended Global Node are billed the same as requests to a Full Global Node of the protocol. See [Full vs archive by protocol](/docs/request-units#full-vs-archive-by-protocol).

## How much history each protocol keeps

History depth depends on the protocol and the network, and it can change over time. Each protocol reports its current range at runtime, so read the range from the node instead of assuming a fixed depth:

* Sui — the gRPC `LedgerService/GetServiceInfo` method reports `lowestAvailableCheckpoint`, the oldest checkpoint the node holds. Plan against the window from that checkpoint to the tip on both gRPC and JSON-RPC. See [Checkpoint retention](/docs/sui-grpc-endpoint#checkpoint-retention). On Mainnet, GraphQL reports its windows through `serviceConfig.availableRange`, and its filtered transaction and event queries keep a shorter window — see [How far back GraphQL history goes](/docs/sui-graphql-endpoint#how-far-back-graphql-history-goes).
* XRP Ledger — keeps more recent ledgers than a default `rippled` server. `server_info` reports the range the node holds in `complete_ledgers`. See [How much ledger history your node holds](/docs/xrpl-tooling#how-much-ledger-history-your-node-holds).
* Stellar — `getHealth` reports the retention window, from `oldestLedger` to `latestLedger`, which bounds transaction and event queries on both networks. On Mainnet, `getLedgers` also serves ledgers older than the window, back to ledger 2. On Testnet, `getLedgers` is limited to the window. See [Historical data availability](/docs/stellar-tooling#historical-data-availability).