Skip to content

fix: Flashbot specs namings and links #399

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

fix: Flashbot specs namings and links #399

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
263c91e
Update flashblocks.md
julio4 Aug 22, 2025
ee97d68
Update flashblocks.md
julio4 Aug 22, 2025
ff9c135
Rename ExecutionPayloadStaticV1 to ExecutionPayloadBaseV1
julio4 Aug 22, 2025
307bdd2
Rename FlashblocksMetadata to Metadata
julio4 Aug 22, 2025
e002ea2
Update flashblocks.md
julio4 Aug 26, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 10 additions & 10 deletions specs/flashblocks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@
- [Data structures](#data-structures)
- [**`FlashblocksPayloadV1`**](#flashblockspayloadv1)
- [**`ExecutionPayloadFlashblockResultV1`**](#executionpayloadflashblockresultv1)
- [**`ExecutionPayloadStaticV1`**](#executionpayloadstaticv1)
- [**`ExecutionPayloadBaseV1`**](#executionpayloadbasev1)
- [**`Metadata`**](#metadata)
- [**`AccountMetadata`**](#accountmetadata)
- [**`StorageSlot`**](#storageslot)
Expand Down Expand Up @@ -114,13 +114,13 @@ The core data structure sent from the Block Builder to Rollup Boost and then ext

```python
class FlashblocksPayloadV1():
version: Bytes4
version: Bytes4
payload_id: Bytes8
parent_flash_hash: Optional[Bytes32]
index: uint64
static: Optional[ExecutionPayloadStaticV1]
parent_flash_hash: Optional[Bytes32]
base: Optional[ExecutionPayloadBaseV1]
diff: ExecutionPayloadFlashblockResultV1
metadata: FlashblocksMetadata
metadata: Metadata
```

**Field descriptions:**
Expand Down Expand Up @@ -166,12 +166,12 @@ class ExecutionPayloadFlashblockResultV1():

All fields in this structure represent the cumulative state of the entire block up to and including the current flashblock, not just the changes from this specific flashblock.

### **`ExecutionPayloadStaticV1`**
### **`ExecutionPayloadBaseV1`**

Container representing immutable fundamental block properties established at initial block creation, unchanged throughout construction.

```python
class ExecutionPayloadStaticV1():
class ExecutionPayloadBaseV1():
parent_beacon_block_root: Bytes32
parent_hash: Bytes32
fee_recipient: ExecutionAddress
Expand Down Expand Up @@ -200,7 +200,7 @@ class ExecutionPayloadStaticV1():
Container encapsulating all metadata for a flashblock, including account state changes and transaction results.

```python
class FlashblockMetadata():
class Metadata():
accounts: List[AccountMetadata]
transactions: List[TransactionMetadata]
```
Expand Down Expand Up @@ -367,7 +367,7 @@ The lifecycle of a Flashblock begins with the Sequencer initiating block creatio

It's important to emphasize that during this process, the External Block Builder sends only the incremental changes in each Flashblock, not the full block state each time. Each `FlashblocksPayloadV1` contains just the delta from the previous state (new transactions, updated state roots, etc.), allowing for efficient bandwidth usage and faster propagation.

Only the first Flashblock (with `index` 0) includes the `static` field containing immutable block data, while subsequent Flashblocks omit this field since this information remains constant throughout the block's construction. Each Flashblock includes a `parent_flash_hash` that references the SSZ hash of the previous Flashblock in the sequence, creating a hash-linked chain within the block.
Only the first Flashblock (with `index` 0) includes the `base` field containing immutable block data, while subsequent Flashblocks omit this field since this information remains constant throughout the block's construction. Each Flashblock includes a `parent_flash_hash` that references the SSZ hash of the previous Flashblock in the sequence, creating a hash-linked chain within the block.

The combined information received across all flashblocks is sufficient to fully reconstruct the complete block without any additional data.

Expand Down Expand Up @@ -1026,4 +1026,4 @@ For RPC Operators, Flashblocks will require a modified RPC node that subscribes

# Implementation

A feature complete implementation of all components described in this document can be found in the [rollup-boost](https://github.com/flashbots/rollup-boost), [op-rbuilder](https://github.com/flashbots/rbuilder/tree/develop/crates/op-rbuilder), [flashblocks-websocket-proxy](https://github.com/base/flashblocks-websocket-proxy), and [reth-flashblocks](https://github.com/danyalprout/reth-flashblocks).
A feature complete implementation of all components described in this document can be found in the [rollup-boost](https://github.com/flashbots/rollup-boost), [op-rbuilder](https://github.com/flashbots/op-rbuilder/) and [node-reth](https://github.com/base/node-reth).
Loading