Robinhood Chain Node-required Sequencer Feed(Ultra) Integration Guide

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

What is Node-required Sequencer Feed(Ultra)

Node-required Sequencer Feed (Ultra) is an ultra-low-latency data transmission solution built on the Standard version. It deeply optimizes network routing and underlying transmission mechanisms to further reduce the end-to-end latency of Sequencer Feed delivery.

Powered by BEF technology, the Ultra version delivers ordered block data to your local node with the lowest possible latency, enabling trading systems to access critical on-chain state earlier.

The solution is purpose-built for latency-sensitive applications, including advanced arbitrage, order flow analysis, and quantitative trading. In an environment where competition is measured in microseconds, earlier access to ordered block data provides more time for strategy computation and transaction execution. Microseconds define the edge.

What is the difference between the Node-required Sequencer Feed and the Direct Sequencer Feed?

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

Benchmark

We established WSS connections with both the Robinhood Chain Sequencer Feed and the BlockRazor Sequencer Feed using the same test client. The Robinhood Chain Sequencer Feed endpoint is wss://feed.mainnet.chain.robinhood.com, and the BlockRazor used the /ws/ultra endpoint.

One test client was deployed in each AWS US East (Ohio) Availability Zone (use2-az1, use2-az2, and use2-az3) to compare the relative block delivery latency of the two Sequencer Feeds. For each block, the Sequencer Feed that delivered the block first was assigned a relative latency of 0 ms. The relative latency of the other feed was calculated from the difference between their block arrival timestamps.

You can use the robinhood-feed-speed benchmark tool to reproduce the test.

Benchmark data is as follows:

use2-az1

Snapshot Time: 2026/10/08 02:22:30 Total Blocks Tested: 2,570

Sequencer Feed	P50	P90	P95	P99	Maximum
BlockRazor Node Required Ultra	0.000 ms	0.000 ms	0.000 ms	0.000 ms	0.000 ms
Robinhood Chain Sequencer Feed	22.271 ms	23.640 ms	26.388 ms	53.690 ms	471.721 ms

BlockRazor Node Required Ultra Win Rate: 100.00%

use2-az2

Snapshot Time: 2026/10/08 02:24:06 Total Blocks Tested: 2512

Sequencer Feed	P50	P90	P95	P99	Maximum
BlockRazor Node Required Ultra	0.000 ms	0.000 ms	0.000 ms	0.000 ms	0.000 ms
Robinhood Chain Sequencer Feed	8.448 ms	9.054 ms	9.234 ms	263.049 ms	462.267 ms

BlockRazor Node Required Ultra Win Rate: 100.00%

use2-az3

Snapshot Time: 2026/10/08 02:22:36 Total Blocks Tested: 2,583

Sequencer Feed	P50	P90	P95	P99	Maximum
BlockRazor Node Required Ultra	0.000 ms	0.000 ms	0.000 ms	0.000 ms	0.000 ms
Robinhood Chain Sequencer Feed	24.639 ms	25.396 ms	29.256 ms	60.855 ms	433.240 ms

BlockRazor Node Required Ultra Win Rate: 100.00%

Tokyo

Total samples: 3996

Sequencer Feed	P50	P90	P95	P99	Maximun
BlockRazor Sequencer Feed	0.000 ms	0.000 ms	0.000 ms	0.000 ms	68.232 ms
Robinhood Chain Sequencer Feed	71.365 ms	108.596 ms	116.049 ms	220.859 ms	1969.576 ms

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 $200 per unit per day and $2000 per unit per month. Subscribe

Endpoint

ws

Region	Endpoint
Ohio	ws://us.robinhood-feeder.blockrazor.io/ws/ultra/{authToken}

wss

Region	Endpoint
Ohio	wss://us.robinhood-feeder.blockrazor.io/ws/ultra/{authToken}
Tokyo	wss://jp.robinhood-feeder.blockrazor.io/ws/ultra/{authToken}

Usage Instructions

1

Subscribe BlockRazor Sequencer Feed

2

Retrieve the auth from the portal and append it as the URI to the WS URL.

ws://us.robinhood-feeder.blockrazor.io/ws/ultra/{authToken}

3

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.

4

Add Feed URL

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

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

replace it with BlockRazor Sequencer Feed：

--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:

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

5

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

6

Verify node status

Check synchronization status:

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:

false