> For the complete documentation index, see [llms.txt](https://docs.blockrazor.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blockrazor.io/streams/node-stream/robinhood-chain/sequencer-feed.md).

# Robinhood Chain Node-required Sequencer Feed Integration Guide

Explore the services, advantages, benchmark, price, endpoint and integration methods of the BlockRazor Node-required Sequencer Feed.

<details>

<summary><strong>What is Sequencer Feed?</strong></summary>

The Sequencer Feed is a real-time data stream pushed by the Robinhood Chain Sequencer. Nodes subscribe to the Feed via WebSocket to quickly receive block data and keep track of the latest on-chain status.

For node operators, e.g. searchers, the transmission speed and stability of the Sequencer Feed directly impact the speed at which nodes catch up with blocks and update their state. When the official Feed endpoint experiences issues such as network latency, network jitter, or unstable connections, nodes may fail to receive the latest data in a timely manner, resulting in node height lag and data update delays.

</details>

<details>

<summary><strong>Why BlockRazor Sequencer Feed</strong></summary>

BlockRazor Sequencer Feed provides Robinhood Chain nodes with a more stable and efficient Sequencer Feed access service.

Compared to directly connecting to the official feed endpoint, BlockRazor Sequencer Feed reduces latency caused by network jitter and connection interruptions during feed synchronization by using the nearest access point and optimizing the transmission path.

Furthermore, the BlockRazor Sequencer Feed is compatible with the official standard access method. Nodes only need to replace the Feed URL to receive the latest data faster and more stably, reducing block tracking latency and keeping the on-chain state synchronized in real time.

</details>

<details>

<summary><strong>What is the difference between the Node-required Sequencer Feed and the Direct Sequencer Feed?</strong></summary>

<table><thead><tr><th width="127.98828125">Comparison</th><th width="255.9140625">Node-required Sequencer Feed</th><th>Direct Sequencer Feed</th></tr></thead><tbody><tr><td>Access Method</td><td>Must be received through a node</td><td>Clients can connect directly without running a nod</td></tr><tr><td>Block Delivery</td><td>Delivers blocks sequentially by block height without skipping any blocks</td><td>Prioritizes the latest block; intermediate blocks may be skipped during network congestion</td></tr><tr><td>Node State Dependency</td><td>Relies on the node’s low-latency synchronized state</td><td>Does not require a local node to maintain complete and continuous state synchronization</td></tr><tr><td>Deployment Cost</td><td>Requires node deployment, maintenance, and monitoring</td><td>Easy to integrate, with lower operational costs</td></tr><tr><td>Suitable Use Cases</td><td>Backrunning and order flow projects</td><td>Sniping and copy trading</td></tr></tbody></table>

</details>

### Benchmark

We established WSS connections with both the Robinhood Chain Sequencer Feed and the BlockRazor Sequencer Feed using the same test client, comparing the relative latency of receiving blocks from both. The Sequencer Feed that received the block first had a relative latency of 0ms, while the Sequencer Feed that received the block later had a relative latency equal to the difference in timestamps between the received blocks. Specific data is as follows:

We established WSS connections with both the Robinhood Chain Sequencer Feed and the BlockRazor Sequencer Feed using one test client deployed in each AWS US East (Ohio) Availability Zone (use2-az1, use2-az2, use2-az3) , comparing the relative latency of receiving blocks from both. The Sequencer Feed that received the block first had a relative latency of 0ms, while the Sequencer Feed that received the block later had a relative latency equal to the difference in timestamps between the received blocks.&#x20;

You can go to [GitHub - BlockRazorinc/robinhood-feed-speed](https://github.com/BlockRazorinc/robinhood-feed-speed) to get the benckmark tool.

Benchmark data is as follows:

{% tabs %}
{% tab title="use2-az1" %}
Snapshot Time: 2026/10/08 02:11:48\
Total Blocks Tested: 813

| Sequencer Feed                 |          P50 |          P90 |          P95 |          P99 |      Maximum |
| ------------------------------ | -----------: | -----------: | -----------: | -----------: | -----------: |
| **BlockRazor Node Required**   | **0.000 ms** | **0.000 ms** | **0.000 ms** | **0.000 ms** | **0.000 ms** |
| Robinhood Chain Sequencer Feed |    19.814 ms |    21.312 ms |    23.615 ms |    58.855 ms |   443.588 ms |

**BlockRazor Node Required Win Rate: 100.00%**
{% endtab %}

{% tab title="use2-az2" %}
Snapshot Time: 2026/10/08 02:11:45\
Total Blocks Tested: 989

| Sequencer Feed                 |          P50 |          P90 |          P95 |          P99 |      Maximum |
| ------------------------------ | -----------: | -----------: | -----------: | -----------: | -----------: |
| **BlockRazor Node Required**   | **0.000 ms** | **0.000 ms** | **0.000 ms** | **0.000 ms** | **0.000 ms** |
| Robinhood Chain Sequencer Feed |     3.965 ms |     4.889 ms |     5.771 ms |    29.968 ms |   468.612 ms |

**BlockRazor Node Required Win Rate: 100.00%**
{% endtab %}

{% tab title="use2-az3" %}
Snapshot Time: 2026/10/08 02:11:50\
Total Blocks Tested: 414

| Sequencer Feed                 |          P50 |          P90 |          P95 |          P99 |      Maximum |
| ------------------------------ | -----------: | -----------: | -----------: | -----------: | -----------: |
| **BlockRazor Node Required**   | **0.000 ms** | **0.000 ms** | **0.000 ms** | **0.000 ms** | **0.000 ms** |
| Robinhood Chain Sequencer Feed |    22.039 ms |    23.821 ms |    47.472 ms |    64.479 ms |   445.627 ms |

**BlockRazor Node Required Win Rate: 100.00%**
{% endtab %}
{% endtabs %}

In terms of latency distribution, BlockRazor not only arrives first on most blocks, but this lead is also highly consistent; in contrast, Robinhood Chain Sequencer Feed is more often in a lagging position and has more pronounced latency fluctuations.

In summary, BlockRazor Sequencer Feed demonstrates significant advantages in block transmission speed, first-to-delivery rate, and latency stability, providing a more reliable first-to-delivery window for latency-sensitive transactions.

### Price

The price is $80 per unit per day and $800 per unit per month. <a href="https://blockrazor.io/#/login?redirect=pricing&#x26;purchaseMode=personalized&#x26;chain=robinhood&#x26;serviceId=robinhood_feed_stream&#x26;billing=day" class="button primary small">Subscribe</a>

### Endpoint

{% tabs %}
{% tab title="ws" %}

<table><thead><tr><th width="152.515625">Region</th><th>Endpoint</th></tr></thead><tbody><tr><td>Ohio</td><td>ws://us.robinhood-feeder.blockrazor.io/ws/{authToken}</td></tr></tbody></table>
{% endtab %}

{% tab title="wss" %}

<table><thead><tr><th width="152.515625">Region</th><th>Endpoint</th></tr></thead><tbody><tr><td>Ohio</td><td>wss://us.robinhood-feeder.blockrazor.io/ws/{authToken}</td></tr><tr><td>Tokyo</td><td>wss://jp.robinhood-feeder.blockrazor.io/ws/{authToken}</td></tr></tbody></table>
{% endtab %}
{% endtabs %}

### Usage Instructions

{% stepper %}
{% step %} <a href="https://blockrazor.io/#/login?redirect=pricing&#x26;purchaseMode=personalized&#x26;chain=robinhood&#x26;serviceId=robinhood_feed_stream&#x26;billing=day" class="button primary small">Subscribe</a> **BlockRazor Sequencer Feed**
{% endstep %}

{% step %}
**Retrieve the auth from the portal and append it as the URI to the WS URL.**

ws\://us.robinhood-feeder.blockrazor.io/ws/{authToken}
{% endstep %}

{% step %}
**Stop the running Robinhood Chain node**

The specific command depends on the current deployment method, such as Docker, Docker Compose, or systemd. Before stopping, it is recommended to ensure that the node data directory is correctly mounted to avoid losing existing synchronized data after restarting.
{% endstep %}

{% step %}
**Add Feed URL**

The following configuration can be found in the node startup command:

```bash
--node.feed.input.url=wss://feed.mainnet.chain.robinhood.com
```

replace it with BlockRazor Sequencer Feed：

```bash
--node.feed.input.url=wss://feed.mainnet.chain.robinhood.com
--node.feed.input.url=ws://us.robinhood-feeder.blockrazor.io/ws/{authToken}
```

The complete mainnet startup example is as follows:

```bash
DATA_DIR="$HOME/rh/robinhood-nitro-data"

docker run --rm -it \
  -v "$DATA_DIR":/home/nitro/.arbitrum \
  -v "$HOME/rh/config":/home/nitro/config \
  -p 8547:8547 \
  -p 8548:8548 \
  offchainlabs/nitro-node:v3.11.2-3599aca \
    --chain.info-files=/home/nitro/config/robinhood-chain-info.json \
    --parent-chain.connection.url=<L1_EXECUTION_RPC_URL> \
    --parent-chain.blob-client.beacon-url=<L1_BEACON_URL> \
    --init.genesis-json-file=/home/nitro/config/robinhood-genesis.json \
    --node.feed.input.url=ws://<BLOCKRAZOR_FEED_URL> \
    --http.addr=0.0.0.0 \
    --http.port=8547 \
    --http.api=net,web3,eth
```

{% endstep %}

{% step %}
**Restart the node**

After saving the configuration and restarting the node, the node will receive Robinhood Sequencer data via the BlockRazor Sequencer Feed.

Check the node logs to confirm:

* BlockRazor Feed connection successful
* No persistent reconnection, timeout, or WebSocket error.
* The node continuously receives the latest Sequencer data.
* Node height is keeping up with Robinhood Chain
  {% endstep %}

{% step %}
**Verify node status**

Check synchronization status:

```bash
curl -d '{"id":0,"jsonrpc":"2.0","method":"eth_syncing","params":[]}' \
  -H "Content-Type: application/json" \
  http://localhost:8547
```

After full synchronization, eth\_syncing should return:

```bash
false
```

{% endstep %}
{% endstepper %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.blockrazor.io/streams/node-stream/robinhood-chain/sequencer-feed.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.