experimental: local Block Builder API #116
Conversation
dmarzzz
changed the title
|
getting an error when running the lint fixer: |
|
Do you mind converting the image files to mermaid? ChatGPT can help with this, you can upload the file and ask it to convert and then you will need to do some manual editing |
dmarzzz
changed the title
Co-authored-by: Leonardo Arias <leo@flashbots.net>
|
|
||
| ## Overview | ||
|
|
||
| This document provides an in-depth specification for integrating a Builder API within the Optimism Protocol |
There was a problem hiding this comment.
small nit: nothing about this proposal enshrines PBS into the protocol but saying "within the Optimism Protocol" makes it sound like ePBS
There was a problem hiding this comment.
good point, will change to "Optimism Stack". I was a bit confused because /specs defines "the plain english specs for Optimism, a minimal optimistic rollup protocol" but this change is actually for the "Optimism Stack".
|
When thinking through Interop builder setting I realized that we should maybe also include the chainID in the request... tradeoff is its not useful at all in single chain world and increase request payload |
|
|
||
| ### Requesting a Block | ||
|
|
||
| The block request mechanism ***MUST*** be triggered when the Driver schedules a new Fork Choice Update on the |
There was a problem hiding this comment.
could you clarify what the Driver entity is here
| OPS->> BB: builder_getPayloadV1 | ||
| BB-->>OPS: BuilderPayloadV1 | ||
| OPS-->>OPS: SimulatePayload | ||
| OPS-->>OPS: ConfirmPaylaod |
There was a problem hiding this comment.
| OPS-->>OPS: ConfirmPaylaod | |
| OPS-->>OPS: ConfirmPayload |
|
|
||
| This structure represents the Block Builder's response to the request for payload. | ||
|
|
||
| - `executionPayload`: `ExecutionPayloadV2` |
There was a problem hiding this comment.
should this be updated to ExecutionPayloadV3?
| - `parentHash`: `Hash32` | ||
| - `pubKey`: `Address` | ||
| - `gasLimit`: `uint256` | ||
| - `parentBeaconBlockRoot`: `Hash32` |
There was a problem hiding this comment.
what is this used for? no need for timestamp?
| Note right of Builder: timespan for building blocks | ||
| OPS->> BB: builder_getPayloadV1 | ||
| BB-->>OPS: BuilderPayloadV1 | ||
| OPS-->>OPS: SimulatePayload |
There was a problem hiding this comment.
how is the payload simulated and confirmed? is it via rpc to the exec engine?
Description
This PR proposes a minimal standardized interface for block construction and transaction management between the Sequencer and a local Block Builder. Separating Block Building from the Sequencer's Execution Engine offers chain operators a way to modify block building rules without creating a large divergence from the upstream OP Stack Client, allowing different chains in the superchain to supply their own block building systems as a way to differentiate.
The goal of this proposal is to introduce a minimal and unopinionated Builder API to unlock innovation, not to define a market structure such as PBS for the superchain.