← Protocols
GetBlock
RPC / Node·EVM · Bitcoin · Solana · Cosmos · Tron · Multi-chain

GetBlock

01Description

Multi-chain RPC and dedicated nodes covering 100+ networks with regional endpoints (EU/US/Asia) and access-token-in-URL authentication.

02Best for
  • 01wide chain coverage (100+)
  • 02regional endpoint pinning (EU/US/APAC)
  • 03shared and dedicated nodes
  • 04Bitcoin, Tron, Doge, and long-tail UTXO chains
  • 05quick free-tier prototyping
03Install
  • pnpm add viem
04Environment variables
VariableScopeDescription
GETBLOCK_ACCESS_TOKENServerGetBlock access token (per-endpoint, generated in the dashboard). The token IS the credential — embedded in the URL path. Server-side only.
GETBLOCK_RPC_URLServerFull GetBlock endpoint URL with region + token, e.g. `https://go.getblock.io/<GETBLOCK_ACCESS_TOKEN>/`. Server-side only.
05Prompt snippet
Use GetBlock for multi-chain RPC. Endpoint URL is region-prefixed and embeds the access token: EU `https://go.getblock.io/<TOKEN>/`, US `https://go.getblock.us/<TOKEN>/`, APAC `https://go.getblock.asia/<TOKEN>/`. Each access token is bound to one chain (selected when generated), so you'll have one token per (chain, network) pair. Wire into `viem` via `createPublicClient({ chain: mainnet, transport: http(process.env.GETBLOCK_RPC_URL) })`. WebSocket: same path on `wss://go.getblock.io/<TOKEN>/`. Coverage includes Ethereum, BSC, Polygon, Avalanche, Arbitrum, Optimism, Base, Solana, Bitcoin, Tron, Doge, Litecoin, and 100+ others. For Bitcoin-family chains, use the standard `bitcoin-cli`-style JSON-RPC body — GetBlock proxies to a real node.
06Gotchas
  • The access token IS the URL — leaking the URL leaks the credential. Never expose `go.getblock.io/<TOKEN>` in a client bundle; proxy via a server route.
  • Each token is single-chain and single-region — multi-chain apps spawn token sprawl in the dashboard. Rotate tokens on staff offboarding because they cannot be IP-restricted.
  • Free tier has a daily request cap and only shared nodes — production loads (especially `eth_getLogs` over wide ranges) hit caps fast and start 429ing.
  • Archive vs full node: most shared chains expose pruned (full-node) state by default; archive access is a separate paid SKU and not all chains have it.
  • Regional latency is real — `go.getblock.io` (EU/Frankfurt) from US-East adds 80–100ms RTT vs `go.getblock.us`. Pick the region nearest to your server cluster.
  • Eviction policy on shared Bitcoin/UTXO nodes can drop large `gettransaction` calls or cap mempool depth; batch carefully.
  • Dedicated nodes are sold as monthly subscriptions (not pay-per-request) and provisioning takes hours — plan capacity in advance for launches.
07Alternatives