Most JSON-RPC providers embed the API key in the URL path. GoldRush uses anDocumentation Index
Fetch the complete documentation index at: https://goldrush.dev/docs/llms.txt
Use this file to discover all available pages before exploring further.
Authorization header instead, so keys never appear in URLs, server logs, or screenshots.
This means migrating involves two steps:
- Swap the URL.
- Add the
Authorization: Bearer <key>header.
From Infura
From Alchemy
Alchemy embeds the API key at the end of the URL path:debug_* and trace_* continue to work. See debug and trace for the per-chain support matrix.
From Ankr
Chain slug mapping
Most providers use short chain names. GoldRush uses the canonical chain slugs from the supported chains list.| Common name | Infura/QuickNode subdomain | GoldRush slug |
|---|---|---|
| Ethereum | mainnet | eth-mainnet |
| Polygon | polygon-mainnet | matic-mainnet |
| BNB Smart Chain | bnb-mainnet | bsc-mainnet |
| Arbitrum | arb-mainnet | arbitrum-mainnet |
| Base | base-mainnet | base-mainnet |
| HyperEVM | n/a | hyperevm-mainnet |
| MegaETH | n/a | megaeth-mainnet |
| Monad | n/a | monad-mainnet |
| Tempo | n/a | tempo-mainnet |
Provider extensions are not supported
GoldRush JSON-RPC implements the standardeth_*, net_*, web3_*, debug_*, and trace_* methods. Provider-specific extensions are intentionally not supported:
| Extension namespace | Provider | GoldRush equivalent |
|---|---|---|
qn_* | QuickNode | Foundational API |
| Token balance / transfer enrichment | various | Foundational API: token balances and transfers |
bor_* | Polygon (Bor) | n/a |
Authentication
Header reference and per-library setup.
Quickstart
Copy-paste examples for every library.