🗄️ Archival Data

Tatum Gateway Overview

The Tatum Gateway simplifies blockchain connectivity, ensuring efficiency and reliability. Powered by an advanced balancing engine, it automatically routes your requests to the most optimal node with the most relevant data.

Additionally, we have integrated an internal layer called Smart Gateway. This layer offers advanced functionalities that ensure faster access to the latest block—outperforming competitors. Alongside these features, we have implemented several enhancements that provide the following benefits to our customers:

• Lower latency for faster response times
• Guaranteed latest block accuracy—you will never encounter a mismatch or missing block when requesting the latest data
• Enhanced security through improved request handling

This setup reduces complexity by providing a single entry point for all your blockchain needs, eliminating the hassle of managing multiple connections or dealing with node-specific requirements.

Pricing

• 5 credits per eth_call method (for EVM-based blockchains)
• 2 credits per other RPC methods
• 50 credits per debug / trace method (for EVM-based blockchains)
• 50 credits per EOS Trace API methods

Node Data History

We aim to maintain full historical blockchain data (from genesis) for all supported chains. However, this is not always possible. Below is a list of blockchains where full history is unavailable.

Mainnets

• Algorand – Performance degradation is observed when querying blocks older than ~19,000,000 (approximately February 2022 and earlier). Queries to this archival range may exceed 60 seconds or time out entirely due to limitations in algorand-mainnet-indexer archive indexing. We are actively evaluating alternate providers for improved historical access but currently offer the service without guaranteed performance for deep archive queries.
• Arbitrum one - Two empty blocks are missing between Nitro and Classic (22,207,816 and 22,207,817)
• EOS Mainnet - Available from block 254,699,235
• NEAR - Some blocks were skipped. This simply means the assigned block producer was unable to produce the block in time. This is normal behavior for the chain, as described in the Consensus chapter of the Nomicon.
  Skipped blocks are not displayed in the explorer, and the response from the node contains the message: "DB Not Found Error."
• SUI Mainnet - Three days (epoch) of data.

Testnets

• BSC Testnet – Only the last 128 blocks are available

Good to Know

• Request Cost: The credits required for different RPC methods are subject to change. We advise you to regularly review pricing details to ensure accurate project budgeting and cost management.
• Archival Data access requires an account with an active Paid Plan.