Skip to main content

​
Onchain data at the edge

Every product below runs on edge.goldsky.com with the same API key. Start with whichever problem sounds like yours.

​
At a glance

​
Boost

Bring your endpoint. We answer what we’ve indexed; everything else passes through untouched.
  • Cached: blocks, transactions, receipts, logs at fixed heights.
  • latest, tags, writes, everything else: your endpoint, free.
  • Boost is available on networks with indexed coverage from genesis. See the current network list.
  • Enable one Boost per project, then connect a provider account or add a custom URL in the dashboard or with goldsky boost enable (CLI reference). Every request then uses /boost/{chain}?key=….
Full docs →

​
Edge RPC

A standard JSON-RPC endpoint. $5/M, every method equal: traces cost the same as eth_blockNumber.
  • Built on eRPC: failover, hedging, dedup, upstream scoring, integrity checks.
  • Indexer-aware: archive routing, eth_getLogs auto-splitting.
  • gRPC block streaming: early access, ask us.
  • Live chain list: GET https://edge.goldsky.com.
  • CLI: goldsky edge create <name> gives you a key; goldsky edge networks lists chains. See the CLI reference.
Full docs →

​
Edge Fanout

Reads verified by a quorum of independent providers. Disagreement returns an error, never a guess.
  • Quorums sized per network: 2-of-3 up to 4-of-5, 46 networks.
  • Deep integrity checks: state and receipt roots recomputed.
  • eth_sendRawTransaction broadcasts to every provider at once.
  • $15/M requests; each read fans out to multiple providers. For DeFi, agents, settlement.
Fanout is mainly for clients that can’t protect themselves: indexers or apps that don’t handle reorgs and reverted data, or can’t verify block and log integrity on their own. No RPC provider, ours or anyone’s, can compensate for a limited client implementation. Fanout moves those checks server-side, so every response arrives already verified.
On request: book a call, email sales@goldsky.com, or read the full docs.

​
Edge Data

Protocol data as an API. No indexer to build, run, or backfill.
  • Polymarket (Polygon): positions with PnL, token balances, trade activity.
  • Blocks: block headers by number, hash, or number/timestamp range, plus chain head.
  • Roadmap: USDC transfers and supply, ENS, token balances, DeFi positions.
  • CLI: goldsky edge create <name> --product data gives you a key; goldsky edge sources lists datasets. See the CLI reference.
$10 per million compute units. One returned row is one CU today; CU weight can change per dataset. Private beta: ask your Goldsky contact for data access.

​
Blocks

The usual job is turning a timestamp into a block number. Ask for the newest block at or before it:
head reports head_lag_seconds, so you can tell a quiet chain from a stalled one.

​
Supported chains

Edge RPC support doesn’t imply a Blocks dataset. This list is shorter, and anything else returns 400 unknown chain. The live set is the chain enum in the API reference.

​
Edge Enterprise

The suite, assembled for your requirements.
  • Contractual SLAs, 24/7 on-call, named CSM, shared Slack.
  • BYOC, static IPs, custom network integrations.
  • AWS Marketplace: retire up to 25% of an annual AWS commit.
Book a call or email sales@goldsky.com.

​
Still deciding?

  • Happy with your provider, unhappy with the bill → Boost
  • One endpoint across 250+ chains → Edge RPC
  • Indexing or backfilling → Edge RPC
  • Highest-quality data (no missed logs, no corrupt blocks) → Edge Fanout
  • Application data, not chain calls → Edge Data
  • SLA, residency, procurement → Edge Enterprise