Testnet Data Availability
1. Testnet Data Availability Scope
The Nodit Web3 Data API Testnet environment currently provides only data from the last 90 days (3 months). This policy applies to Testnets of chains where the Mainnet is also supported, and does not apply to Testnet-only chains.
Data that returns only the current state without specifying a query time or range is not subject to the retention limit. For example, data such as the current state of an address or account, token holder information, and contract metadata is not queried based on a specific block or past timestamp, so it is available without a time restriction in the Testnet environment.
Aggregated data is not calculated over the full historical period. Only data within the most recent 90 days — the current available range — is used as the basis for calculation.
Affected Testnet Networks
The following Testnet networks are subject to this Testnet data availability policy.
Chain | Testnet | Retention Policy |
|---|---|---|
Arbitrum | Sepolia | 90 days |
Base | Sepolia | 90 days |
Ethereum | Sepolia, Hoodi | 90 days |
Kaia | Kairos | 90 days |
Optimism | Sepolia | 90 days |
The following Testnet networks are classified as Testnet-only chains with no corresponding Mainnet, and are not subject to this policy.
Chain | Testnet | Retention Policy |
|---|---|---|
GIWA | Sepolia | No Limit |
2. How the Policy Affects API Responses
2.1 Range-based Queries
When querying data by specifying a block/ledger or date range, requests are not treated as errors even if the requested range extends beyond the currently available range. In such cases, the API evaluates the full requested range and returns only the data that falls within the currently available period on the Testnet. Data outside the available range is not returned, but its inclusion in the request does not cause an error.
2.2 Multi-item Queries
For bulk query APIs that retrieve multiple resources in a single request, each item in the request is evaluated individually for availability. Only items that fall within the currently available Testnet period are included in the response. Items outside the available range are excluded from the results without triggering an error.
2.3 Single-item Queries
For APIs that query a single explicitly specified resource, if the requested resource falls outside the currently available Testnet range, the API cannot serve that resource and returns a 404 Not Found error. This does not indicate a malformed request; it reflects a policy-based limitation that the resource is not currently available in the Testnet environment.
{
"code": "RESOURCE_NOT_FOUND",
"message": "Resource not found: { RESOURCE_NAME = RESOURCE_VALUE }. Testnet only retains data from the past 3 months. To access older data, please use a Node API."
}
2.4 Aggregated or Accumulated Data
For APIs that return aggregated or statistical data, the values in the response are not based on a full historical accumulation. Instead, they are calculated using only data from the most recent 90 days — the currently available period on the Testnet. As a result, the same request may return different values compared to the Mainnet environment, which is the expected behavior given the difference in data availability ranges.