Robinhood Chain Sequencer Feed
This section introduces the services, advantages, benchmark, price and integration methods of the BlockRazor Robinhood Chain Sequencer Feed.
What is Sequencer Feed?
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.
Why BlockRazor Sequencer Feed
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.
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.
You can go to GitHub - BlockRazorinc/robinhood-feed-speed to get the benckmark tool.
Benchmark data is as follows:
快照時間：2026-08-12T10:18:57.825039121Z，测试測試區塊總數：252798
BlockRazor Sequencer Feed
80.27%
0.000 ms
0.000 ms
2.771 ms
6.116 ms
Robinhood Chain Sequencer Feed
19.73%
4.640 ms
9.604 ms
15.651 ms
19.749 ms
快照時間：2026-08-12T10:18:56.218075456Z，测试測試區塊總數：252451
BlockRazor Sequencer Feed
87.01%
0.000 ms
0.445 ms
1.659 ms
4.831 ms
Robinhood Chain Sequencer Feed
12.98%
5.302 ms
17.379 ms
23.194 ms
70.723 ms
快照時間：2026-08-12T10:18:17.587552975Z，测试測試區塊總數：251670
BlockRazor Sequencer Feed
76.48%
0.000 ms
1.640 ms
2.842 ms
6.336 ms
Robinhood Chain Sequencer Feed
23.52%
2.742 ms
11.219 ms
16.373 ms
32.839 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 $80 per unit per day and $800 per unit per month. Subscribe
Endpoint
Ohio
wss://us.robinhood-feeder.blockrazor.io/ws/{authToken}
Tokyo
wss://jp.robinhood-feeder.blockrazor.io/ws/{authToken}
Usage Instructions
Subscribe BlockRazor Sequencer Feed
Retrieve the auth from the portal and append it as the URI to the WSS URL.
wss://us.robinhood-feeder.blockrazor.io/ws/{authToken}
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.
Add Feed URL
The following configuration can be found in the node startup command:
replace it with BlockRazor Sequencer Feed：
The complete mainnet startup example is as follows:
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
Verify node status
Check synchronization status:
After full synchronization, eth_syncing should return:
Last updated
Was this helpful?