edge

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Goldsky Edge (RPC Endpoints)

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.
Goldsky Edge是面向EVM区块链的托管式高性能RPC端点服务,基于eRPC(一款开源的容错EVM RPC代理)构建。它提供全球分布式、低延迟的RPC访问,具备智能路由、缓存、故障转移和内置可观测性功能。

What Edge Does

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
Edge位于您的应用与区块链RPC服务商之间,新增以下功能:
  • 性能:覆盖8+区域的全球边缘基础设施,延迟低于100毫秒,链上最新数据CDN缓存
  • 高可用性:跨多服务商自动故障转移,实现99.9%的正常运行时间,并行对冲请求
  • 数据完整性:跨多个节点验证响应,跟踪区块高度,执行一致性检查
  • 成本控制:请求去重、智能路由、可配置请求限流
  • 索引优化:自动拆分大型
    eth_getLogs
    请求,将历史查询路由至归档节点

Quickstart

Quickstart

Endpoint Format

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).
https://edge.goldsky.com/standard/evm/{chainId}?secret=YOUR_SECRET
{chainId}
替换为对应链ID(例如:Ethereum对应
1
,Base对应
8453
,Arbitrum对应
42161
)。

Authentication

Authentication

Three options:
  • Query parameter:
    ?secret=YOUR_SECRET
  • Header:
    X-ERPC-Secret-Token: YOUR_SECRET
  • x402 (pay-per-request): Clients without a secret receive an HTTP 402 response with payment requirements. An x402-compatible client signs a USDC payment and retries; Edge settles via a facilitator before forwarding the request upstream. Payment is settled on Base (chain
    8453
    ) in USDC. Pricing is
    $0.000005
    per request (same as the standard
    $5 per million
    rate). See https://www.x402.org/ for the protocol spec.
三种认证方式:
  • 查询参数
    ?secret=YOUR_SECRET
  • 请求头
    X-ERPC-Secret-Token: YOUR_SECRET
  • x402(按请求付费):无密钥的客户端会收到包含支付要求的HTTP 402响应。兼容x402的客户端需签署USDC支付请求并重试;Edge会通过中介完成结算后再将请求转发至上游。支付将在Base链(链ID
    8453
    )以USDC结算。定价为每请求
    $0.000005
    (与标准的
    每百万请求5美元
    费率一致)。协议规范详见https://www.x402.org/。

Example (curl)

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}'
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)

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"),
});
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)

Example (ethers.js)

typescript
import { JsonRpcProvider } from "ethers";

const provider = new JsonRpcProvider(
  "https://edge.goldsky.com/standard/evm/1?secret=YOUR_SECRET"
);
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

Managing Edge Endpoints in the Webapp

Edge endpoints are created and managed in the Goldsky webapp at
/dashboard/rpc-edge
.
Edge端点需在Goldsky网页应用的
/dashboard/rpc-edge
路径下创建和管理。

Creating an Endpoint

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_...
    )
  1. 导航至Edge RPC页面(
    /dashboard/rpc-edge
  2. 点击「Create endpoint」
  3. 输入名称(仅允许小写字母、数字、连字符;必须以字母开头;长度3-50字符)
  4. 可选:选择请求限流额度
  5. 系统将自动生成API密钥(格式:
    gs_edge_...

Endpoint Management

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
  • 查看指标:在端点详情页查看请求数量、错误率和响应时间
  • 查看日志:可搜索、可筛选的日志用于调试
  • 显示API密钥:查看您的密钥(点击可复制)
  • 请求限流:更新端点的请求限流额度
  • 暂停/恢复:切换端点的启用状态
  • 删除:永久删除端点

Plan Limits

Plan Limits

  • Free (Starter): 1 endpoint, subject to free-tier request limits
  • Scale: Multiple endpoints, pay-as-you-go
  • Enterprise: Unlimited endpoints
  • 免费版(Starter):1个端点,受免费层请求限制约束
  • Scale版:多个端点,按需付费
  • 企业版:无限制端点数量

Rate Limiting

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-ip
Unlimited~1.7Strict per-IP only
edge-tier-unlimited-total-500rpm-per-ip
Unlimited~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)
请求限流需在Goldsky控制台按密钥配置。可选择以下预设套餐(来源:https://docs.goldsky.com/edge-rpc/platform/security#rate-limiting):
Budget IDTotal RPSPer-IP RPS使用场景
None (Unlimited)
无限制无限制不启用请求限流
edge-tier-6krpm-total-unlimited-per-ip
~100无限制低流量场景
edge-tier-60krpm-total-unlimited-per-ip
~1,000无限制中流量场景
edge-tier-180krpm-total-unlimited-per-ip
~3,000无限制高流量场景
edge-tier-360krpm-total-unlimited-per-ip
~6,000无限制超高流量场景
edge-tier-600krpm-total-unlimited-per-ip
~10,000无限制企业级流量场景
edge-tier-6krpm-total-500rpm-per-ip
~100~8低流量场景+单IP保护
edge-tier-60krpm-total-500rpm-per-ip
~1,000~8中流量场景+单IP保护
edge-tier-180krpm-total-500rpm-per-ip
~3,000~8高流量场景+单IP保护
edge-tier-360krpm-total-500rpm-per-ip
~6,000~8超高流量场景+单IP保护
edge-tier-600krpm-total-500rpm-per-ip
~10,000~8企业级流量场景+单IP保护
edge-tier-unlimited-total-100rpm-per-ip
无限制~1.7仅启用严格单IP限流
edge-tier-unlimited-total-500rpm-per-ip
无限制~8仅启用中等单IP限流
  • Total RPS = 使用该密钥的所有IP的最大每秒请求数
  • Per-IP RPS = 单个客户端IP的最大每秒请求数
请求限流套餐内部定义了以下规则:
  • method — 限流规则适用的RPC方法(支持通配符)
  • maxCount — 最大请求数量
  • period — 时间窗口(例如每秒、每分钟)

Supported Networks

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
undefined
实时注册表(权威数据源 — 推荐链前请务必查看):
GET https://edge.goldsky.com/
返回的JSON包含
standard
数组,列出Edge支持的所有网络。每个条目包含:
  • id
    — 例如
    evm:1
    (前缀+链ID)
  • alias
    — 人性化名称(例如
    mainnet
    base
    polygon
  • blockTimeMs
    — 平均出块时间
  • state
    — 正常运行时显示
    OK
bash
undefined

List all supported chain IDs

列出所有支持的链ID

curl -s https://edge.goldsky.com/ | jq '.standard[].id'
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
curl -s https://edge.goldsky.com/ | jq '.standard[] | select(.id=="evm:8453")'

主要支持的网络包括Ethereum、Arbitrum One、Base、Optimism、Polygon zkEVM、BSC、Avalanche、Berachain、HyperEVM、Monad、Sei、Sonic、Unichain、zkSync及其测试网 — 但以上述注册表为权威数据源,其中包含更多网络。

人性化文档页面:https://docs.goldsky.com/chains/supported-networks

Special Capabilities

Special Capabilities

Flashblocks

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*
在OP Stack链(Base、Optimism、Unichain及其测试网)上实现更快的区块确认。启用方式:
  • 查询参数:
    use-upstream=flashblocks*
  • 或请求头:
    X-ERPC-Use-Upstream: flashblocks*

HyperEVM System Transactions

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)
HyperEVM有两个独立的节点池:
  • use-upstream=systx*
    — 包含系统交易的归档节点(用于索引)
  • use-upstream=standard*
    — 不含系统交易的实时节点(用于前端dApp)

Pricing

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)
  • 每百万请求5美元 — 所有RPC方法定价一致(
    eth_getLogs
    或追踪类方法无额外费用)
  • 每月请求量≤5亿:按每百万5美元计费
  • 每月请求量>5亿:可享受批量折扣(联系销售)

Monitoring

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
每个端点都内置Grafana仪表盘,展示以下内容:
  • RPC总请求数和每秒请求数
  • 网络和方法使用情况细分
  • 响应时间百分位数(P50/P90/P99)
  • 错误率和详细错误日志
  • 被限流的请求追踪
  • 多路复用和对冲请求指标

Error Codes

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).
Edge会标准化上游服务商返回的错误:
代码含义
-32005请求限流超出
-32012范围过大(eth_getLogs)
-32014数据缺失
-32015节点超时
-32016未授权
此外还包含标准JSON-RPC错误(-32700、-32600、-32601、-32602、-32603)和EVM特定错误(-32000、-32003、3)。

Supported RPC Methods

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.
全面支持5个命名空间下的标准EVM JSON-RPC方法(60+种)。每种方法都有对应的文档页面:
https://docs.goldsky.com/edge-rpc/evm/methods/{method_name}
— 构建请求前,请查看该页面确认参数、返回格式及Edge特有的行为。

eth_*
— core chain queries and transactions

eth_*
— 核心链查询与交易

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
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_*
— 原始区块/收据数据与EVM追踪

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

trace_*
— OpenEthereum-style tracing

trace_*
— OpenEthereum风格追踪

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

net_*
— network metadata

net_*
— 网络元数据

net_listening
,
net_peerCount
,
net_version
net_listening
,
net_peerCount
,
net_version

web3_*
— client metadata

web3_*
— 客户端元数据

web3_clientVersion
,
web3_sha3
web3_clientVersion
,
web3_sha3

Request shape

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.

所有方法均使用标准JSON-RPC 2.0格式。
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"
    }]
  }'
使用追踪方法(
debug_trace*
,
trace_*
)前,请查看对应方法页面 — 并非所有链都支持所有追踪器,部分方法存在链特定的特性说明。

eRPC (Open-Source)

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基于eRPC构建,这是一款开源的容错EVM RPC代理。若用户需要Goldsky Edge未提供的功能(自托管、自定义缓存驱动、自定义选择策略、多服务商故障转移等),可直接运行eRPC。
完整的eRPC参考文档(功能、配置、API)可获取LLM优化版文档包:https://docs.erpc.cloud/llms.txt

Goldsky Documentation Links

Goldsky Documentation Links