Skip to main content
Boost reads the JSON-RPC method and parameters, then chooses the response source. The API key identifies your project’s Boost; that project’s network configuration supplies the upstream for calls that need your provider.

​
Routing model

A failed or incomplete cache lookup falls back to your upstream. A cache miss can add proxy latency, but it does not substitute a different historical result.

​
Methods eligible for indexed data

Eligibility does not guarantee a hit. If Goldsky does not have the requested data, Boost forwards the request.

​
Block tags always forward

Requests using latest, pending, safe, finalized, or earliest are always forwarded. The same rule applies to eth_getLogs when either range bound is a tag. Your upstream is the authority on the chain head. Serving a tag from indexed data could otherwise return a block behind your provider or a block affected by a reorganization. Use a concrete hexadecimal height when you want an eligible historical read.

​
Everything else forwards

Writes, traces, and state reads such as eth_call and eth_getBalance go to your configured upstream. Boost also forwards methods it does not recognize as eligible. For a forwarded call, Boost preserves the JSON-RPC method, parameters, and ID. The result body comes from your upstream. HTTP headers are handled separately; see request and response forwarding.

​
Batch requests

Boost evaluates JSON-RPC batches per item. Eligible items can come from Goldsky data while the remaining items are sent to your upstream together in one onward batch.
  • Give every item a unique id. JSON-RPC does not guarantee response order, so match results by ID.
  • Use x-edge-billable as the served-item count. x-cache is HIT only when Boost serves every item in the batch.
  • Keep arrays at 100 items or fewer. Larger arrays are forwarded whole without cache lookups.
For example, a batch where Boost serves 44 of 45 items reports x-cache: MISS and x-edge-billable: 44.

​
Authentication and endpoint selection

The endpoint format is:
The chain path selects the network. The Goldsky key identifies your project’s Boost, and that network’s configuration selects the active upstream. Your provider URL and persistent provider credentials stay in the configuration rather than traveling in each request.