概述

POST /v1/rpc 是同步的 JSON-RPC 代理端点，将标准 Ethereum JSON-RPC 请求转发至 Robinhood Chain 并返回完整的响应结果。支持单请求和批量请求。

请求格式

POST /v1/rpc
Content-Type: application/json
X-User-ID: <your-api-key>

请求体遵循标准 JSON-RPC 2.0 规范：

{
  "jsonrpc": "2.0",
  "method": "<method-name>",
  "params": [],
  "id": 1
}

使用示例

查询链 ID

curl -X POST https://robinhood-ohio.flashblock.trade/v1/rpc \
  -H "Content-Type: application/json" \
  -H "X-User-ID: <your-api-key>" \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

响应:

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": "0x1237"
}

0x1237 = 4663 (Mainnet), 0xb626 = 46630 (Testnet)

查询最新区块号

curl -X POST https://robinhood-ohio.flashblock.trade/v1/rpc \
  -H "Content-Type: application/json" \
  -H "X-User-ID: <your-api-key>" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

响应:

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": "0x1a4f5e"
}

查询账户余额

curl -X POST https://robinhood-ohio.flashblock.trade/v1/rpc \
  -H "Content-Type: application/json" \
  -H "X-User-ID: <your-api-key>" \
  -d '{
    "jsonrpc": "2.0",
    "method": "eth_getBalance",
    "params": ["0xYourAddress", "latest"],
    "id": 1
  }'

同步发送交易

通过此端点也可以同步发送交易（等待链上确认后返回）：

curl -X POST https://robinhood-ohio.flashblock.trade/v1/rpc \
  -H "Content-Type: application/json" \
  -H "X-User-ID: <your-api-key>" \
  -d '{
    "jsonrpc": "2.0",
    "method": "eth_sendRawTransaction",
    "params": ["0xf86c0a8502540be400..."],
    "id": 1
  }'

如果您不需要等待响应，推荐使用 异步交易端点 /v1/tx 以获得更低的感知延迟。

批量请求

支持在单次请求中发送多个 JSON-RPC 调用，将它们放入 JSON 数组即可：

curl -X POST https://robinhood-ohio.flashblock.trade/v1/rpc \
  -H "Content-Type: application/json" \
  -H "X-User-ID: <your-api-key>" \
  -d '[
    {"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1},
    {"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":2},
    {"jsonrpc":"2.0","method":"eth_gasPrice","params":[],"id":3}
  ]'

响应:

[
  {"jsonrpc":"2.0","id":1,"result":"0x1237"},
  {"jsonrpc":"2.0","id":2,"result":"0x1a4f5e"},
  {"jsonrpc":"2.0","id":3,"result":"0x3b9aca00"}
]

批量请求计费说明

批量请求中的 每个元素 消耗 1 个配额单位。例如，一个包含 10 个请求的批量数组将一次性消耗 10 个配额。如果当前配额不足，整个批量请求将被拒绝并返回 429 rate_limited。

请求体限制

• 最大请求体大小: 1 MiB (1,048,576 字节)
• 空请求体或无效 JSON 将返回 400 invalid_request

注意事项

• 通过此端点发送的交易方法（eth_sendRawTransaction、eth_sendTransaction）将消耗交易配额而非查询配额，两类配额互相独立。
• 所有标准 Ethereum JSON-RPC 方法均受支持。
• 上游节点不可达时将返回 502 upstream_error，超时将返回 504 upstream_timeout。