goldsky-io/goldsky-agent

edge

Configure and troubleshoot Goldsky Edge, Goldsky's managed EVM RPC endpoint service.

Ver código-fonte

Como usar

  1. Copie o comando e verifique o pacote antes de instalar no seu ambiente de agente.
  2. Consulte no original as ferramentas, credenciais e ambientes necessários.
  3. Descreva os dados de entrada e a entrega esperada; confira a saída com as fontes.
npx skills add https://github.com/goldsky-io/goldsky-agent --skill edge

Antes de começar

  • A instalação não inclui assinatura de modelo, franquia API ou acesso aos seus arquivos.
  • Estrelas e instalações indicam atividade, não um teste independente de qualidade ou segurança.
Documento original do Skill

Renderizado do repositório de origem, preservando títulos, exemplos, código, tabelas, links e imagens.

Goldsky Edge (RPC Endpoints)

Goldsky Edge is a managed, high-performance RPC endpoint service for EVM blockchains, built on eRPC — an open-source fault-tolerant EVM RPC proxy. It provides globally-distributed, low-latency RPC access with intelligent routing, caching, failover, and built-in observability.

What Edge Does

Edge sits between your application and blockchain RPC providers. It adds:

  • Performance: Global edge infrastructure across 8+ regions, sub-100ms latency, tip-of-chain CDN caching
  • Resiliency: Automatic failover across multiple providers for 99.9% uptime, hedged parallel requests
  • Data Integrity: Cross-validates responses from multiple nodes, tracks block heights, enforces consensus checks
  • Cost Control: Request deduplication, intelligent routing, configurable rate limiting
  • Indexing Optimizations: Auto-splits large eth_getLogs requests, routes historical queries to archive nodes

Quickstart

Endpoint Format

https://edge.goldsky.com/standard/evm/{chainId}?secret=YOUR_SECRET

Replace {chainId} with the chain ID (e.g., 1 for Ethereum, 8453 for Base, 42161 for Arbitrum).

Authentication

Three options:

  • Header (recommended): X-ERPC-Secret-Token: YOUR_SECRET — keeps the secret out of URLs, which are commonly logged by proxies, CDNs, and server access logs.
  • Query parameter: ?secret=YOUR_SECRET — convenient for quick tests, but the secret leaks into any log that records the full URL. Prefer the header for production traffic. The examples below use the query param for brevity.
  • x402 (pay-per-request): Clients without a secret receive an HTTP 402 response with an x402 v2 challenge (PAYMENT-REQUIRED header). The challenge lists two ways to pay. Circle Gateway (deposit once on Ethereum, Base, Arbitrum, Optimism, Polygon, Avalanche, Unichain, Sonic, World Chain, Sei, HyperEVM or Arc) asks for a $0.005 top-up (5000 atomic USDC) that credits a prepaid balance for the paying wallet; each call then costs $0.000005 (5 atomic USDC, the standard $5 per million rate) and is deducted from that balance without a settlement per call. A standard `exact` USDC payment settled through the Coinbase CDP facilitator (Base, Polygon, Arbitrum, World Chain, Monad) needs no Gateway deposit and signs against the USDC token's own EIP-712 domain, tops up the same prepaid balance on settlement — Edge lists these CDP entries before the Gateway entries, so a standard v2 client (@x402/fetch, not the legacy x402-fetch package) pays through CDP by default with no extra configuration; Circle's GatewayClient still selects by extra.name === "GatewayWalletBatched", so it keeps using Gateway. Both options fund the same balance and share the same per-call price. The same balance pays for Feeds requests. Responses carry x-goldsky-x402-funding and x-goldsky-x402-balance. See https://docs.goldsky.com/edge-rpc/capabilities/x402 for the client setup for either option and https://www.x402.org/ for the protocol spec.

Example (curl)

bash
curl -s "https://edge.goldsky.com/standard/evm/1?secret=YOUR_SECRET" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

Example (viem)

typescript
import { createPublicClient, http } from "viem";
import { mainnet } from "viem/chains";

const client = createPublicClient({
  chain: mainnet,
  transport: http("https://edge.goldsky.com/standard/evm/1?secret=YOUR_SECRET"),
});

Example (ethers.js)

typescript
import { JsonRpcProvider } from "ethers";

const provider = new JsonRpcProvider(
  "https://edge.goldsky.com/standard/evm/1?secret=YOUR_SECRET"
);

Managing Edge Endpoints in the Webapp

Edge endpoints are created and managed in the Goldsky webapp at /dashboard/rpc-edge.

Creating an Endpoint

  1. Navigate to the Edge RPC page (/dashboard/rpc-edge)
  2. Click "Create endpoint"
  3. Enter a name (lowercase letters, numbers, hyphens; must start with a letter; 3-50 chars)
  4. Optionally select a rate limit budget
  5. An API key is generated automatically (format: gs_edge_...)

Endpoint Management

  • View metrics: See request counts, error rates, and response times on the endpoint detail page
  • View logs: Searchable, filterable logs for debugging
  • Reveal API key: View your secret key (click to copy)
  • Rate limiting: Update the rate limit budget for an endpoint
  • Pause/Resume: Toggle an endpoint on or off
  • Delete: Remove an endpoint permanently

Plan Limits

  • Free (Starter): 1 endpoint, subject to free-tier request limits
  • Scale: Multiple endpoints, pay-as-you-go
  • Enterprise: Unlimited endpoints

Rate Limiting

Rate limits are configured per secret in the Goldsky Dashboard. Pick one of the following named tiers (source: https://docs.goldsky.com/edge-rpc/platform/security#rate-limiting):

Budget IDTotal RPSPer-IP RPSUse case
None (Unlimited)UnlimitedUnlimitedNo rate limiting
edge-tier-6krpm-total-unlimited-per-ip~100UnlimitedLow volume
edge-tier-60krpm-total-unlimited-per-ip~1,000UnlimitedMedium volume
edge-tier-180krpm-total-unlimited-per-ip~3,000UnlimitedHigh volume
edge-tier-360krpm-total-unlimited-per-ip~6,000UnlimitedVery high volume
edge-tier-600krpm-total-unlimited-per-ip~10,000UnlimitedEnterprise volume
edge-tier-6krpm-total-500rpm-per-ip~100~8Low volume + per-IP protection
edge-tier-60krpm-total-500rpm-per-ip~1,000~8Medium volume + per-IP protection
edge-tier-180krpm-total-500rpm-per-ip~3,000~8High volume + per-IP protection
edge-tier-360krpm-total-500rpm-per-ip~6,000~8Very high volume + per-IP protection
edge-tier-600krpm-total-500rpm-per-ip~10,000~8Enterprise volume + per-IP protection
edge-tier-unlimited-total-100rpm-per-ipUnlimited~1.7Strict per-IP only
edge-tier-unlimited-total-500rpm-per-ipUnlimited~8Moderate per-IP only
  • Total RPS = max requests/sec across all IPs using this secret
  • Per-IP RPS = max requests/sec from a single client IP

Rate limit budgets internally define rules with:

  • method — which RPC method(s) the limit applies to (supports wildcards)
  • maxCount — maximum number of requests
  • period — time window (e.g. per second, per minute)

Supported Networks

Live registry (authoritative — always check this before recommending a chain): GET https://edge.goldsky.com/

Returns JSON with a standard array of every network Edge serves. Each entry has:

  • id — e.g. evm:1 (prefix + chain ID)
  • alias — human name (e.g. mainnet, base, polygon)
  • blockTimeMs — average block time
  • state — OK when operational
bash
# List all supported chain IDs
curl -s https://edge.goldsky.com/ | jq '.standard[].id'

# Find a specific chain
curl -s https://edge.goldsky.com/ | jq '.standard[] | select(.id=="evm:8453")'

Highlights include Ethereum, Arbitrum One, Base, Optimism, Polygon zkEVM, BSC, Avalanche, Berachain, HyperEVM, Monad, Sei, Sonic, Unichain, zkSync, plus their testnets — but the registry above is the source of truth and includes many more.

For the human-readable docs page: https://docs.goldsky.com/chains/supported-networks

Special Capabilities

Flashblocks

Faster block confirmations on OP Stack chains (Base, Optimism, Unichain and their testnets). Enable by adding:

  • Query parameter: use-upstream=flashblocks*
  • Or header: X-ERPC-Use-Upstream: flashblocks*

HyperEVM System Transactions

Two distinct node pools for HyperEVM:

  • use-upstream=systx* — Archive nodes with system transactions (for indexing)
  • use-upstream=standard* — Realtime nodes without system transactions (for frontend dApps)

Pricing

  • $5 per million requests — all RPC methods priced equally (no surcharges for eth_getLogs or trace methods)
  • Up to 500M requests/month at $5/million
  • 500M+: Volume discounts available (contact sales)

Monitoring

Each endpoint has a built-in Grafana dashboard showing:

  • Total RPC requests and requests per second
  • Network and method usage breakdowns
  • Response time percentiles (P50/P90/P99)
  • Error rates and detailed error logs
  • Rate-limited request tracking
  • Multiplexed and hedged request metrics

Error Codes

Edge normalizes errors from upstream providers:

CodeMeaning
-32005Rate limit exceeded
-32012Range too large (eth_getLogs)
-32014Missing data
-32015Node timeout
-32016Unauthorized

Plus standard JSON-RPC errors (-32700, -32600, -32601, -32602, -32603) and EVM-specific errors (-32000, -32003, 3).

Supported RPC Methods

Full coverage of standard EVM JSON-RPC methods across five namespaces (60+ methods). Each method has its own docs page at https://docs.goldsky.com/edge-rpc/evm/methods/{method_name} — use it to confirm params, return shape, and any Edge-specific behavior before constructing a call.

Method index: https://docs.goldsky.com/edge-rpc/evm/methods

eth_* — core chain queries and transactions

eth_accounts, eth_blobBaseFee, eth_blockNumber, eth_call, eth_chainId, eth_createAccessList, eth_estimateGas, eth_feeHistory, eth_gasPrice, eth_getBalance, eth_getBlockByHash, eth_getBlockByNumber, eth_getBlockReceipts, eth_getBlockTransactionCountByHash, eth_getBlockTransactionCountByNumber, eth_getCode, eth_getFilterChanges, eth_getFilterLogs, eth_getLogs, eth_getProof, eth_getStorageAt, eth_getTransactionByBlockHashAndIndex, eth_getTransactionByBlockNumberAndIndex, eth_getTransactionByHash, eth_getTransactionCount, eth_getTransactionReceipt, eth_getUncleByBlockHashAndIndex, eth_getUncleByBlockNumberAndIndex, eth_getUncleCountByBlockHash, eth_getUncleCountByBlockNumber, eth_maxPriorityFeePerGas, eth_newBlockFilter, eth_newFilter, eth_newPendingTransactionFilter, eth_pendingTransactions, eth_sendRawTransaction, eth_subscribe, eth_syncing, eth_uninstallFilter, eth_unsubscribe

debug_* — raw block/receipt data and EVM tracing

debug_getRawBlock, debug_getRawHeader, debug_getRawReceipts, debug_getRawTransaction, debug_traceBlockByHash, debug_traceBlockByNumber, debug_traceCall, debug_traceTransaction

trace_* — OpenEthereum-style tracing

trace_block, trace_call, trace_callMany, trace_filter, trace_get, trace_rawTransaction, trace_replayBlockTransactions, trace_replayTransaction, trace_transaction

net_* — network metadata

net_listening, net_peerCount, net_version

web3_* — client metadata

web3_clientVersion, web3_sha3

Request shape

All methods use the standard JSON-RPC 2.0 envelope. Example for eth_getLogs:

bash
curl -s "https://edge.goldsky.com/standard/evm/1?secret=YOUR_SECRET" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "eth_getLogs",
    "params": [{
      "fromBlock": "0x1000000",
      "toBlock": "0x1000064",
      "address": "0xdAC17F958D2ee523a2206206994597C13D831ec7"
    }]
  }'

Before using trace methods (debug_trace*, trace_*), check the per-method page — not every chain supports every tracer, and some methods have chain-specific quirks documented there.


eRPC (Open-Source)

Edge is built on eRPC, an open-source fault-tolerant EVM RPC proxy. For capabilities beyond what Goldsky Edge exposes (self-hosting, custom cache drivers, custom selection policies, multi-provider failover, etc.), users may want to run eRPC directly.

For full eRPC reference (features, config, APIs), fetch the LLM-optimized docs bundle: https://docs.erpc.cloud/llms.txt

Edge or Boost?

They share the edge.goldsky.com host and get confused constantly:

  • Edge (this skill) is Goldsky's own managed RPC. The user buys it instead of a provider. Many chains, configurable rate-limit budgets, hedging, failover, x402.
  • Boost (/boost) is a free CDN in front of the provider the user already has. Cacheable reads come from Goldsky's indexed data; everything else forwards to their endpoint unchanged. Only genesis-covered chains, HTTP only, Goldsky-managed rate limits.

"I want to spend less with Alchemy" is Boost. "I want to stop using Alchemy" is Edge. A user can also point Boost's upstream at an Edge endpoint.

A third product shares the host: Feeds (/feeds), the REST API under https://edge.goldsky.com/data (wallet transfers and balances, tokens, Polymarket activity, positions and balances, block headers and chain head). It was formerly called Edge Data or Data APIs; the URLs and keys did not change. It is not JSON-RPC and does not take an Edge secret. It takes a Feeds API key, or x402 at Feeds prices. The block at a timestamp, or a wallet's Polymarket positions, is one Feeds request; use /feeds there rather than a loop of RPC calls.

Goldsky Documentation Links

  • Edge Introduction: https://docs.goldsky.com/edge-rpc/introduction
  • Edge Quickstart: https://docs.goldsky.com/edge-rpc/quickstart
  • Why Edge: https://docs.goldsky.com/edge-rpc/why-edge
  • Security & Rate Limiting: https://docs.goldsky.com/edge-rpc/platform/security
  • Monitoring: https://docs.goldsky.com/edge-rpc/platform/monitoring
  • Flashblocks: https://docs.goldsky.com/edge-rpc/capabilities/flashblocks
  • HyperEVM System Tx: https://docs.goldsky.com/edge-rpc/capabilities/hyperevm-system-transactions
  • Error Codes: https://docs.goldsky.com/edge-rpc/evm/error-codes
  • RPC Methods Index: https://docs.goldsky.com/edge-rpc/evm/methods
  • Pricing: https://docs.goldsky.com/pricing/summary
  • Supported Networks: https://docs.goldsky.com/chains/supported-networks
do mesmo repositório

Mais Skills

Todos os Skills
goldsky-io
Comunidade

auth-setup

Set up Goldsky CLI authentication and project configuration. Use this skill when the user needs to: install the goldsky CLI (what's the official install command?), run goldsky login (including when the browser opens but 'authentication failed'), run goldsky project list and see 'not logged in' or 'unauthorized', switch between Goldsky projects, check which project they're currently authenticated to, or fix 'unauthorized' errors when running goldsky turbo commands. Also use for 'walk me through s

Instalações / 1h
4
GitHub Stars
12
Atualizado
2 de nov.
goldsky-io
Comunidade

boost

Configure and troubleshoot Goldsky Boost, the free RPC caching CDN in front of a provider the user already pays for. Use for cutting RPC bills without migrating, connecting Alchemy/QuickNode/Infura upstreams, goldsky boost, edge.goldsky.com/boost, verification, cache hit rates, ethgetLogs forwarding, and x-cache / x-edge-billable / x-edge-source headers. Boost keeps the existing provider and forwards uncached requests. To replace a provider with Goldsky's managed RPC, use /edge. Pipeline, Subgra

Instalações / 1h
4
GitHub Stars
12
Atualizado
2 de nov.
goldsky-io
Comunidade

datasets

Use this skill when the user needs to look up or verify Goldsky blockchain dataset names, chain prefixes, dataset types, or versions. Triggers on questions like 'what\\'s the dataset name for X?', 'what prefix does Goldsky use for chain Y?', 'what version should I use for Z?', or 'what datasets are available for Solana/Stellar/Arbitrum/etc?'. Also use for chain-specific dataset questions (e.g., polygon vs matic prefix, stellarnet balance datasets, solana token transfer dataset names), and to ans

Instalações / 1h
4
GitHub Stars
12
Atualizado
2 de nov.
goldsky-io
Comunidade

feeds

Query Goldsky Feeds over HTTP: one wallet's balances and transfers; metadata and current USD price of up to 100 EVM tokens; Polymarket activity (a wallet's trades), positions, PnL and balances; block headers by number, hash or timestamp; and a chain's head block. Feeds absorbed Edge Data / Data APIs, with the same URLs and keys. Use for wallet holdings, portfolio value, transfer history, deposit checks, token prices or metadata, a wallet's Polymarket trades or positions, which block was at a tim

Instalações / 1h
4
GitHub Stars
12
Atualizado
2 de nov.