GetBlock Brings Archive Data Access to Shared Node Endpoints

Archive calls added to GetBlock Shared RPC

GetBlock, a trusted provider of blockchain infrastructure services, is rolling out a meaningful upgrade to its blockchain node API services. Today, we introduce an Archive Mode – a new feature that adds full historical-state access to our Shared tier RPC endpoints.

TL;DR:

Historically, GetBlock provided archive data access to supported blockchains only via Dedicated Nodes. Now, Shared RPC endpoints can also handle historical data queries when set to an Archive Mode.

Chains supported at launch include Ethereum and major EVM chains, plus non-EVM chains such as Cardano and Sui.

Archive endpoint setup is available on paid Shared tiers with no additional plan charge. Requests to these endpoints consume 2x the usual Compute Units (CUs).

This upgrade makes archive onchain data more accessible, without ops of running archive servers or forcing into more expensive dedicated plans.

If you consider moving from a self-hosted setup or another provider, contact our team and tell us your needs. We’ll craft the right archive setup for you.

GetBlock delivers easy access to deep blockchain history with Archive Mode

RPC endpoints created from the GetBlock’s Shared Nodes dashboard can now be configured with Archive Mode. When enabled, the endpoint’s RPC calls are serviced by archive nodes rather than regular full nodes.

Archive RPC endpoint is set up via GetBlock's self-serve dashboard

At launch, this functionality is added for select protocol mainnets where historical-state access is most in demand, including Ethereum, Base, Polygon, Arbitrum, HyperEVM, BNB Chain, TRON, Cardano, and Sui. We’ll add more networks over time – check the GetBlock dashboard for availability.

Commenting on Archive Calls going live for Shared Node users, GetBlock CEO Vasily Rudomanov introduces new opportunities for developers:

While we've released a ton of new features in 2025, the Archive Calls functionality now available to Shared Node users represents a zero-to-one change in pricing. Previously, you needed to deploy a dedicated node to access archive data in blockchains. Now, it's available even to Starter plan users. The new option is already live for all Tier 1 blockchains, with more networks on the way. We're welcoming more sophisticated and data-heavy apps on GetBlock's Shared Node service.

Vasily Rudomanov — CEO, GetBlock

Archive capability has traditionally been a specialist, high-cost feature – offered only as a dedicated, enterprise-grade service because of associated operational expenses. By placing archive nodes behind Shared endpoints, GetBlock is lowering the barrier for developers and teams to access historical blockchain state while preserving Shared Nodes cost efficiencies.

How Archive Mode works

Archive setup is available on all paid Shared Node tiers – Starter, Advanced, Pro, and Enterprise – with no additional subscription fee.

RPC requests to an archive endpoint continue to consume Compute Units (CUs), which are deducted from the quota included with the selected plan.

These types of queries are significantly more resource-intensive to serve, so CU usage for endpoints in Archive Mode is set to reflect the extra compute required:

Each request to an archive endpoint consumes twice the standard CU amount.

The 2x multiplier is applied to every request sent to an archive endpoint, regardless of whether a call accesses historical state.

This model keeps billing transparent and aligns CU consumption with the actual resources required to serve archive blockchain data.

Archive endpoint setup steps

The archive endpoint setup follows the familiar flow. From the GetBlock dashboard:

Open the Shared Nodes tab and click Get endpoint.

Select the desired blockchain protocol. Chains that support archive access display a small history icon.

Switch Mode to Archive.

Complete other settings (API interface, region) and receive an endpoint URL.

With this setup, archive data access is immediately available inside your Shared Node subscription, ideal for occasional historical reads and analytics. It eliminates the need to provision and operate costly archive nodes, enabling simpler access to full blockchain history.

For heavy, repeated historical reads, GetBlock still recommends Dedicated Nodes.

Dedicated archive nodes provide predictable performance, higher concurrency, and single-tenant resources – essential when historical access becomes the core of the product.

If that’s your case, reach out using our contact form to request a tailored deployment.

What’s next?

We’re already working on the next upgrade to make GetBlock’s infrastructure even more flexible. Stay tuned! Another major improvement is just around the corner.