The Low-latency Infra Base Builders Trust

Subscribe to BlockRazor FlashBlock Stream over gRPC or WebSocket from the nearest supported region. FlashBlock is a sub-block update typically pushed about every 200ms before the completed Base block, so applications can react earlier than if they wait for the roughly two-second final block.

Use FlashBlock Stream for pre-confirmation signals, Block Stream for completed blocks and confirmed transactions, and regional Transaction Sending for eth_sendRawTransaction. Measure the full signal-to-submission path from the same production region because the fastest component alone does not determine end-to-end latency.

Send the signed transaction through the nearest BlockRazor Base endpoint using gRPC or HTTPS and keep the client connection warm where possible. Test regional latency, retries, and tail behavior with the production workload; lower transport latency can improve arrival time but cannot guarantee ordering or inclusion.

Use Block Stream when the application needs completed blocks and confirmed transactions. Use FlashBlock Stream when earlier pre-confirmation awareness is more important than waiting for the final block.

FlashBlock Stream supports gRPC and WebSocket. Block Stream uses gRPC. Transaction Sending supports gRPC and HTTPS for eth_sendRawTransaction.

Current documentation lists Frankfurt, Tokyo, and Virginia. Applications should select the nearest regional endpoint and validate latency with their own production workload.