> ## Documentation Index
> Fetch the complete documentation index at: https://goldrush.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Edge Tier

> Production GoldRush JSON-RPC with archive depth, debug and trace, sub-100ms p50 latency, and an SLA.

The **Edge tier** is the production endpoint for GoldRush JSON-RPC. It runs from regional edge POPs in front of an analytics-driven multi-provider router, with archive depth, the `debug_*` and `trace_*` namespaces, and an SLA.

## Endpoint

```
https://rpc.goldrushdata.com/v1/{chain}
```

See [Authentication](/goldrush-json-rpc/authentication) for header setup.

## What you get

| Feature                               | Edge                         |
| ------------------------------------- | ---------------------------- |
| `eth_*`, `net_*`, `web3_*` methods    | ✅                            |
| `debug_*` namespace                   | ✅                            |
| `trace_*` namespace                   | ✅                            |
| Archive depth (full historical state) | ✅                            |
| Sub-100ms p50 latency                 | ✅                            |
| 99.9% uptime SLA                      | ✅                            |
| Rate limit                            | Account-scoped, configurable |
| Multi-provider failover               | ✅                            |

## How requests are routed

```
                          ╔═ Edge POP (closest) ════════════════════════════╗
                          ║                                                 ║░            ╔══════════╗
╔══════════╗              ║   ╔══════╗    ╔═══════╗    ╔══════════════════╗ ║░            ║ Upstream ║░
║ Your App ║░ ──HTTP/2──▶ ║   ║ Auth ║ ─▶ ║ Cache ║ ─▶ ║ Analytics Router ║ ║░ ──route──▶ ║ nodes    ║░
╚══════════╝░             ║   ╚══════╝    ╚═══════╝    ╚══════════════════╝ ║░            ╚══════════╝░
 ░░░░░░░░░░░░             ║                                                 ║░             ░░░░░░░░░░░░
                          ╚═════════════════════════════════════════════════╝░
                           ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
```

The Edge layer:

1. **Authenticates** the request, so invalid keys never hit the upstream.
2. **Caches** safe-to-cache reads (e.g. `eth_getBlockByNumber` for finalized blocks) at the edge.
3. **Routes** the call to whichever upstream provider currently scores highest on cost and performance for that specific `(chain, method)` route. Scores are continuously updated from rolling-window success rate, latency, error class, and cost analytics.
4. **Re-routes on failure** to the next-best provider, and feeds the failure back into the score so the routing table self-corrects in seconds.

The result: lower p99 latency than any single provider, and no single-vendor dependency.

## Archive depth

Edge serves historical state and traces back to the chain's earliest available archive block. Depth varies by chain. See [debug and trace](/goldrush-json-rpc/debug-trace) for the per-chain matrix.

## SLA and rate limits

* **Uptime SLA**: 99.9% per calendar month
* **Rate limit**: configurable per account; defaults to 1,000 RPS
* **Burst**: 2× the configured RPS for up to 60 seconds

Need a higher limit? Contact your GoldRush account manager.

<CardGroup cols={2}>
  <Card title="debug_* and trace_*" href="/goldrush-json-rpc/debug-trace" icon="bug">
    Method list and per-chain availability.
  </Card>

  <Card title="Failover and SLA" href="/goldrush-json-rpc/failover-and-sla" icon="shield">
    How the Edge layer handles upstream failures.
  </Card>

  <Card title="Pricing" href="/goldrush-json-rpc/pricing" icon="coins">
    Per-method credit rates.
  </Card>

  <Card title="Migration" href="/goldrush-json-rpc/migrating-from-other-providers" icon="right-left">
    Side-by-side diffs from other providers.
  </Card>
</CardGroup>