> 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-landing-benchmark.md).

# 上链 Benchmark

2026 年 9 月 14 日，**Node1 从法兰克福发起的上链竞争胜率为 66%，从 Ohio 发起为 61%**，每个地区各测试 100 轮。

| 提交路径                       |  法兰克福发起 | Ohio 发起 |
| -------------------------- | ------: | ------: |
| Node1 Ohio 2B              |     38% |     43% |
| Node1 Ohio 2C              |     28% |     18% |
| **Node1 合计 — 两个入口**        | **66%** | **61%** |
| **Robinhood 排序器直连 — 三个入口** | **34%** | **39%** |

每个地区从同一台机器五路同时提交提前签名的零金额自转账，每轮各路交易哈希不同，发送方、nonce 和 gas 参数相同。连接提前预热，发送端持续忙轮询；上一 nonce 上链后再开始下一轮。

按成功上链的交易哈希判定胜出，不以 HTTP 响应速度判定。每区全部 100 轮均计入结果。应用层发送启动时间差最大为：**法兰克福 18.889 微秒，Ohio 0.700 微秒**。

两地为不同测试时段。Node1 内部可能多路转发，同 nonce 接纳规则也会影响结果。这是上链竞争胜率，不是延迟测量或跨地区性能保证。


---

# 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-landing-benchmark.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.