Skip to main content

Documentation Index

Fetch the complete documentation index at: https://base-a060aa97-roethke-update-v0-8-0.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

Subscribe via eth_subscribe to receive the current pending block state as each Flashblock is built. Each message is the complete accumulated block — a standard Ethereum block object containing all transactions pre-confirmed so far.
Only available on Flashblocks WebSocket endpoints: wss://mainnet-preconf.base.org and wss://sepolia-preconf.base.org.
Requires base/base minimum client version v0.3.1.
Multiple notifications are emitted per block height. Each Flashblock (~200ms) triggers a new notification for the same block with more transactions added. This is accumulating state, not a diff — every message replaces the previous one. Your handler should treat each notification as the latest known state of the in-progress block.

Parameters

subscriptionType
string
required
Must be "newFlashblocks".

Returns

The initial eth_subscribe response returns a hex-encoded subscription ID. After that, the node pushes one notification per Flashblock (~200ms). Each notification’s result is a standard Ethereum block object identical in shape to eth_getBlockByNumber with hydrated=true, but representing the pending (not yet sealed) block. Key differences from a sealed block:
  • transactions is a full array of transaction objects (always hydrated — hashes are never returned)
  • hash, stateRoot, receiptsRoot, transactionsRoot reflect the partial block state at time of emission and will differ from the final sealed block values
  • The same block number will appear in multiple notifications as new Flashblocks accumulate
result
object
Standard Ethereum block object. Fields match eth_getBlockByNumber with hydrated=true.

Example

{"jsonrpc": "2.0", "id": 1, "method": "eth_subscribe", "params": ["newFlashblocks"]}