Skip to main content

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.

Most JSON-RPC providers embed the API key in the URL path. GoldRush uses an Authorization header instead, so keys never appear in URLs, server logs, or screenshots. This means migrating involves two steps:
  1. Swap the URL.
  2. Add the Authorization: Bearer <key> header.
Below are concrete diffs for the most common providers.

From Infura

- https://mainnet.infura.io/v3/{INFURA_PROJECT_ID}
+ https://rpc.goldrushdata.com/v1/eth-mainnet
+ Authorization: Bearer YOUR_GOLDRUSH_API_KEY
For libraries that take a URL string only, you’ll need to switch to the custom-headers pattern:
const provider = new ethers.JsonRpcProvider(
  `https://mainnet.infura.io/v3/${process.env.INFURA_PROJECT_ID}`
);

From Alchemy

Alchemy embeds the API key at the end of the URL path:
- https://eth-mainnet.g.alchemy.com/v2/{ALCHEMY_API_KEY}
+ https://rpc.goldrushdata.com/v1/eth-mainnet
+ Authorization: Bearer YOUR_GOLDRUSH_API_KEY
debug_* and trace_* continue to work. See debug and trace for the per-chain support matrix.

From Ankr

- https://rpc.ankr.com/eth/{ANKR_API_KEY}
+ https://rpc.goldrushdata.com/v1/eth-mainnet
+ Authorization: Bearer YOUR_GOLDRUSH_API_KEY

Chain slug mapping

Most providers use short chain names. GoldRush uses the canonical chain slugs from the supported chains list.
Common nameInfura/QuickNode subdomainGoldRush slug
Ethereummainneteth-mainnet
Polygonpolygon-mainnetmatic-mainnet
BNB Smart Chainbnb-mainnetbsc-mainnet
Arbitrumarb-mainnetarbitrum-mainnet
Basebase-mainnetbase-mainnet
HyperEVMn/ahyperevm-mainnet
MegaETHn/amegaeth-mainnet
Monadn/amonad-mainnet
Tempon/atempo-mainnet

Provider extensions are not supported

GoldRush JSON-RPC implements the standard eth_*, net_*, web3_*, debug_*, and trace_* methods. Provider-specific extensions are intentionally not supported:
Extension namespaceProviderGoldRush equivalent
qn_*QuickNodeFoundational API
Token balance / transfer enrichmentvariousFoundational API: token balances and transfers
bor_*Polygon (Bor)n/a
If you depend on a provider extension, use the GoldRush Foundational API (decoded, typed REST) or the Streaming API (real-time event streams) instead.

Authentication

Header reference and per-library setup.

Quickstart

Copy-paste examples for every library.