> For the complete documentation index, see [llms.txt](https://node1.gitbook.io/node1-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://node1.gitbook.io/node1-docs/documentation/zh/robinhood/robinhood-landing/robinhood-batch.md).

# Batch Transactions

接入前请查看[节点地址、Account UUID 与额度](/node1-docs/documentation/zh/robinhood/robinhood-landing.md)。

使用 robinhood\_sendBatchTransaction，params 为包含 1～10 个已签名交易字符串的数组。整个 HTTP 请求体还须满足节点配置的大小限制（最高 256 KiB）。所有交易先完成校验，再开始转发。

```json
{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "robinhood_sendBatchTransaction",
  "params": [
    "0x<SIGNED_TRANSACTION_1>",
    "0x<SIGNED_TRANSACTION_2>"
  ]
}
```

## 额度与接收回执

普通付费账号的 raw、plain text 和 batch 共享[按交易笔数计算的额度](/node1-docs/documentation/zh/robinhood/robinhood-landing.md)：一个 10 笔 batch 消耗 10 笔额度。整批额度不足时返回 HTTP 429，不会只发送其中一部分。免费账号仍按独立的 batch 请求次数计数。

服务先保存本地批次接收记录，再完成限流和入队，随后返回 HTTP 202，不等待排序器回应，也不在 HTTP 请求中等待逐笔发送间隔。记录会异步上报数据库。

响应包含 `result.batch_id` 和按输入顺序排列的 `result.transactions`。每项的 `status: queued` 表示本地已接收；`tx_hash` 是交易哈希，`duplicate` 表示是否命中去重，`retry` 提供重试指示。请逐项检查，HTTP 202 不表示全部交易已成功；完整示例和失败情况见[响应与重试](/node1-docs/documentation/zh/robinhood/robinhood-landing/robinhood-responses.md)。

响应提示 `message` 为 `"Successfully forwarded"`。单笔 JSON-RPC 和纯文本响应将其放在顶层；batch 将其放在每个 `queued` 交易项中。该字段仅用于展示，服务仍在本地入队后返回 HTTP 202，不等待网络写出或排序器确认，也不表示交易已上链。客户端应依据状态、哈希及错误字段处理响应，不要根据提示文案判断上链成功。

## 发送调度

批内交易按输入顺序、以 5 ms 为目标间隔在后台调度，不等待上一笔确认后才启动下一笔；不同批次可能交错执行。Batch 不提供链上原子执行，也不保证网络到达、上链顺序或执行成功。本地整批额度检查通过，不代表后续所有转发路径都会成功。

[查看响应处理与重试规则 →](/node1-docs/documentation/zh/robinhood/robinhood-landing/robinhood-responses.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://node1.gitbook.io/node1-docs/documentation/zh/robinhood/robinhood-landing/robinhood-batch.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.