You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/base-chain/api-reference/flashblocks-api/flashblocks-api-overview.mdx
+30-5Lines changed: 30 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,38 @@
1
1
---
2
-
title: 'Flashblocks API Overview'
3
-
sidebarTitle: 'Flashblocks API Overview'
4
-
description: 'Reference for Flashblocks-specific RPC methods, WebSocket subscriptions, and the infrastructure stream schema.'
2
+
title: 'Overview'
3
+
sidebarTitle: 'Overview'
4
+
description: 'Flashblocks-specific RPC methods, WebSocket subscriptions, and the infrastructure stream schema for Base pre-confirmations.'
5
5
---
6
6
7
-
This page covers what is unique to Flashblocks: Flashblocks-only RPC methods, real-time WebSocket subscriptions, and the raw infrastructure stream schema.
7
+
Flashblocks endpoints expose all standard Ethereum JSON-RPC methods plus a set of pre-confirmation-specific additions. These let you read state, simulate transactions, and stream events against sequencer-ordered data up to ~1.8 seconds before a block seals.
8
+
9
+
<Info>
10
+
All [standard Ethereum JSON-RPC methods](/base-chain/api-reference/rpc-overview) work identically on Flashblocks endpoints. Use the `"pending"` block tag to resolve against pre-confirmed state instead of the transaction pool. See the [Overview](/base-chain/api-reference/rpc-overview#what-is-the-flashblocks-tier) for endpoint URLs and a full explanation of the two tiers.
11
+
</Info>
12
+
13
+
## HTTP Methods
14
+
15
+
| Method | Description |
16
+
| :--- | :--- |
17
+
|[eth_simulateV1](/base-chain/api-reference/flashblocks-api/eth_simulateV1)| Simulate transaction bundles against pre-confirmed state |
18
+
|[base_transactionStatus](/base-chain/api-reference/flashblocks-api/base_transactionStatus)| Check if a transaction has been received by the node mempool |
19
+
20
+
## WebSocket Subscriptions
21
+
22
+
On a Flashblocks WSS endpoint, `eth_subscribe` with `newHeads` emits a new event approximately every 200ms per Flashblock instead of every 2 seconds. Three additional subscription types are also available that are exclusive to Flashblocks endpoints:
23
+
24
+
| Subscription | Description |
25
+
| :--- | :--- |
26
+
|[newFlashblockTransactions](/base-chain/api-reference/flashblocks-api/newFlashblockTransactions)| Stream individual transactions as they are pre-confirmed (~200ms each) |
27
+
|[pendingLogs](/base-chain/api-reference/flashblocks-api/pendingLogs)| Stream filtered event logs from pre-confirmed transactions |
28
+
|[newFlashblocks](/base-chain/api-reference/flashblocks-api/newFlashblocks)| Stream full Flashblock payload objects from the sequencer |
29
+
30
+
## Infrastructure Stream
31
+
32
+
The raw Flashblocks infrastructure stream is the upstream WebSocket feed consumed by Flashblocks-aware RPC nodes. It emits a new message approximately every 200ms as the sequencer pre-confirms transactions.
8
33
9
34
<Warning>
10
-
**Applications should not connect directly to the infrastructure stream.** These endpoints are for node infrastructure only. App developers should use the [WebSocket subscription methods](/base-chain/api-reference/flashblocks-api/newFlashblocks)via a Flashblocks-aware RPC provider instead.
35
+
**Applications should not connect directly to the infrastructure stream.** These endpoints are for node operators only. App developers should use the [WebSocket subscription methods](#websocket-subscriptions) above via a Flashblocks-aware RPC provider.
@@ -35,29 +35,18 @@ Flashblocks endpoints are fully EVM-equivalent; every standard `eth_` method wor
35
35
36
36
Calls like `eth_getBalance`, `eth_getStorageAt`, and `eth_call` run against real sequencer state up to 1.8 seconds before the block seals, with sub-second latency.
37
37
38
-
## Real-Time Event Streams (WebSocket)
39
-
40
-
On a **Flashblocks WSS** endpoint, `eth_subscribe` with `newHeads` emits a new event approximately every 200ms as each Flashblock is appended, rather than every 2 seconds.
41
-
42
-
Flashblocks endpoints also expose three additional subscription types not present on Standard endpoints:
43
-
44
-
| Subscription | Description |
45
-
| --- | --- |
46
-
|[`newFlashblockTransactions`](/base-chain/api-reference/flashblocks-api/newFlashblockTransactions)| Stream of individual transactions as they are pre-confirmed |
47
-
|[`pendingLogs`](/base-chain/api-reference/flashblocks-api/pendingLogs)| Filtered logs from pre-confirmed transactions |
48
-
|[`newFlashblocks`](/base-chain/api-reference/flashblocks-api/newFlashblocks)| Full Flashblock payload stream (block state objects) |
49
-
50
38
## API Reference
51
39
52
40
### Ethereum JSON-RPC API
53
41
54
-
Core Ethereum protocol methods for account queries, block and transaction data, gas estimation, and log filtering. All methods work on both Standard and Flashblocks endpoints.
42
+
Core Ethereum protocol methods for account queries, block and transaction data, gas estimation, and log filtering. All methods work on both Standard and Flashblocks endpoints.
55
43
56
44
<Info>
57
45
Methods marked ✓ support the `"pending"` block tag on Flashblocks endpoints.
0 commit comments