Robinhood Chain Sequencer Feed Benchmark: BlockRazor vs. Official Feed

Competition on Robinhood Chain does not begin only when a transaction is submitted. It begins when a system first receives the latest onchain state. For searchers, trading bots, and automated trading systems, receiving a block earlier means updating local state, identifying opportunities, and constructing transactions sooner.

BlockRazor deployed benchmark clients in three AWS US East (Ohio) Availability Zones and connected each client to both BlockRazor Robinhood Chain Sequencer Feed Ultra and the official Robinhood Chain Sequencer Feed. For matching blocks, the test compared which feed reached the same client first. In the updated benchmark, BlockRazor maintained 0.000 ms relative latency from P50 through P99 in all three zones. The official feed recorded P50 relative latency of 27.310–97.404 ms and P99 relative latency of 85.805–953.111 ms.

The results show that BlockRazor consistently delivered matching blocks earlier while providing a more stable delivery window under tail-latency conditions.

What Is Robinhood Chain Sequencer Feed?

Robinhood Chain Sequencer Feed is a real-time block data stream pushed by the sequencer. Nitro nodes subscribe to the feed through WebSocket, receive new blocks, and continuously update their local view of the chain.

Unlike an RPC client that actively queries historical or latest data, Sequencer Feed pushes new blocks directly to subscribed nodes. It is an important data input for tracking the latest Robinhood Chain state. Feed speed and stability affect how quickly a node catches up with blocks and updates its state. Network jitter, connection interruptions, or high tail latency can temporarily leave a node behind the latest height, causing systems that depend on the node to make decisions from older state.

The difference may be negligible for ordinary data queries, but it is important to searchers, trading bots, and automated trading systems: receive the block earlier → update node state earlier → identify onchain opportunities earlier → simulate and construct transactions earlier → preserve more time for transaction submission.

A low-latency feed cannot guarantee transaction success or strategy profitability. However, when strategy, fee, and execution conditions are comparable, earlier state gives a trading system a larger reaction window, improves its competitiveness in latency races, and increases its opportunity to capture potential revenue.

Benchmark Methodology

Test regions and subjects

We deployed a benchmark client in each of three AWS US East (Ohio) Availability Zones:

• use2-az1
• use2-az2
• use2-az3

Each client established two WSS connections and received data from:

• BlockRazor Robinhood Chain Sequencer Feed Ultra (/ws/ultra)
• Robinhood Chain official Sequencer Feed (wss://feed.mainnet.chain.robinhood.com)

Receiving both feeds on the same server gave the compared feeds the same client environment and local network conditions, reducing the effect of deployment differences. Testing three Availability Zones also showed whether the direction of the result remained consistent across different network paths within the same region.

The updated dataset contains 4,232 matching samples in use2-az1, 4,305 in use2-az2, and 4,714 in use2-az3. The test can be reproduced with BlockRazor's open-source robinhood-feed-speed benchmark tool.

Test procedure

1. Connect to BlockRazor Feed and the official feed simultaneously from the same test server in each Availability Zone.
2. Receive and parse the block data pushed by both feeds.
3. Match identical blocks received from the two feeds.
4. Record the arrival timestamp of each matching block from each feed.
5. Assign a relative latency of 0 ms to the feed that arrives first.
6. Assign the later feed a relative latency equal to the difference between the two arrival timestamps.
7. Calculate P50, P90, P95, P99, and maximum relative latency for each feed.

This benchmark measures the relative arrival time for identical blocks delivered by two feeds to the same client. A value of 0 ms therefore means that a feed arrived first for the corresponding sample. It does not mean that the end-to-end latency from the sequencer to the client was zero.

Benchmark Results

P99 relative latency remained at 0 ms in all three Availability Zones

BlockRazor maintained 0.000 ms relative latency through P99 in all three Availability Zones. In use2-az1 and use2-az2, its maximum relative latency also remained at 0.000 ms; in use2-az3, the maximum was 9.580 ms. The consistent result across all three zones shows that the delivery advantage was not confined to a single AZ or network path.

Earlier state updates and a more stable reaction window

The official feed recorded median relative latency of 28.026 ms in use2-az1, 97.404 ms in use2-az2, and 27.310 ms in use2-az3. The difference became larger in the tail: its P99 reached 85.805 ms, 953.111 ms, and 111.686 ms, respectively. The largest gap appeared in use2-az2, where the official feed's maximum relative latency reached 1,616.810 ms.

For node operators, lower tail latency can reduce temporary state lag caused by feed jitter and help local state follow the sequencer more closely. For searchers, trading bots, and automated trading systems, earlier state enables earlier detection, opportunity evaluation, simulation, and transaction construction, preserving more time for submission.

Transaction success still depends on strategy validity, submission speed, fee configuration, competitors, and onchain execution. When other conditions are comparable, however, an earlier and more stable Sequencer Feed shortens the total reaction time from state update to transaction submission, improves the probability of winning competitive execution, and substantially increases the opportunity to capture potential revenue.

Getting Started

BlockRazor Sequencer Feed Ultra is compatible with the standard feed interface used by Robinhood Nitro nodes. Operators can connect over WSS by updating --node.feed.input.url in the startup configuration.

If your team operates a Robinhood Chain node, searcher, trading bot, or other real-time trading system, review the BlockRazor Sequencer Feed Ultra benchmark and integration guide and benchmark it from your own production environment. If you encounter any issues during integration, please contact us.