Robinhood Chain Sequencer Feed is live. Receive ordered blocks earlier with Node-required Ultra or Direct Ultra access.
Get Started
Sign in
Create Account
ETHEREUM INFRASTRUCTURE

The Low-latency Infra Ethereum Builders Trust

Low-latency pending signals, blocks, node synchronization, and transaction paths for Ethereum trading systems.

One path from pending signal to execution

Combine public pending data, confirmed blocks, synchronized local node state, and faster public transaction propagation.

Public Mempool

Receive publicly propagating Ethereum pending transactions over a regional gRPC stream for monitoring and strategy input.

gRPC delivery across three regions

NewBlocks

Consume the latest Ethereum block headers, confirmed transactions, and withdrawals through regional relays.

Blocks and confirmed transactions in one stream

CL/EL Client Sync

Connect Ethereum consensus and execution clients to BlockRazor relays for fresher local blocks and world state.

Purpose-built paths for both client layers

Broadcast Tx

Send a signed Ethereum transaction through regional gRPC relays for fast public propagation.

Regional gRPC transaction relays

Ethereum infrastructure, documented end to end

BlockRazor Docs cover separate signal, block, node, and submission paths across the same three relay regions.

Review Ethereum coverage in Docs
Regional relay locations3Frankfurt, Tokyo, and Virginia
Stream services3Mempool, Block, and Node
Node client layersCL + ELConsensus and execution
Submission pathsRPC + TxProtection or public speed

Built around the Ethereum trading loop

Use the signal, local-state, and submission layers independently or combine them in one latency-sensitive workflow.

Observe

Public Mempool and NewBlocks

Evaluate

Fresh CL and EL client state

Execute

Broadcast Tx or Ethereum RPC

Explore the trading bot workflow

Ethereum infrastructure FAQ

01Which Ethereum service should a trading bot start with?

Start with Public Mempool when the strategy depends on pending signals. Add NewBlocks for confirmed data, CL/EL Client Sync for fresher local state, and Broadcast Tx or Ethereum RPC for submission.

02How is CL/EL Client Sync different from NewBlocks?

NewBlocks pushes structured block data to an application. CL/EL Client Sync connects your own Ethereum clients to BlockRazor relays so the local node can update blocks and world state earlier.

03Does Ethereum Broadcast Tx provide MEV protection?

No. Broadcast Tx enters public propagation and prioritizes lower-latency sending. Use BlockRazor Ethereum RPC when a private, protected path is required.

04Where are the Ethereum regional relays?

Current documentation lists Frankfurt, Tokyo, and Virginia. Choose the relay closest to the application or node deployment and validate it with production traffic.

Build your Ethereum low-latency workflow

Talk to sales

Tell us about your partnership goals or subscription questions. Our business team can help with subscription plans, pricing, and ways to work together.

Start integration

Log in to get your auth token and start building. You can contact us on Discord during integration.