Skip to main content
Boost reduces the traffic sent to an RPC provider you already use. Eligible historical reads come from Goldsky’s indexed data. Every other JSON-RPC call forwards to your configured endpoint. Your application keeps one RPC interface and one response shape. You keep control of the upstream provider, while repeatable reads can avoid reaching it at all.

Set up Boost

Configure an upstream and verify your first cache hit.

See what Boost serves

Understand cache eligibility, block tags, batches, and forwarding.

​
How Boost fits into your stack

  1. Your application sends JSON-RPC requests to a Boost URL instead of directly to your provider.
  2. Boost serves eligible reads when Goldsky has the requested historical data.
  3. Calls Boost cannot serve are forwarded to the active upstream configured for that network.
The routing decision uses the request method and parameters. It does not require an additional request to your provider.
Boost preserves the JSON-RPC interface, but it is still an HTTP proxy. It normalizes some transport headers and manages CORS at the edge. See request and response forwarding for the exact contract.

​
Use Boost when

  • You want to keep your current provider and client libraries.
  • Your workload repeatedly reads fixed blocks, transactions, receipts, or log ranges.
  • You want to reduce upstream request volume without changing application behavior on a cache miss.
  • You need to measure which requests Boost served and which reached your provider.
Boost is not a replacement for WebSocket subscriptions or a way to cache chain-head queries such as latest. Those calls remain with your provider. If you want Goldsky to operate the RPC provider layer as well, use Edge RPC.

​
Explore Boost

Quickstart

Make a cache hit, compare a forwarded request, and update an existing client.

How it works

Cached methods, block tags, batch behavior, and the forwarding contract.

Configure upstreams

Provider connections, custom URLs, credentials, headers, CORS, and timeouts.

Measure results

Read response headers and calculate the share of calls that avoided your provider.

Reference

Endpoint syntax, supported networks, billing, and limits.

Troubleshooting

Diagnose misses, provider errors, CORS, large batches, and verification issues.

​
Getting help

Can’t find what you’re looking for? Reach out to us at support@goldsky.com for help.