Skip to content

feat(payload): allow publishing payloads built outside a payload job - #16

Closed
sebastianst wants to merge 1 commit into
optimismfrom
seb/publish-built-payload
Closed

sebastianst wants to merge 1 commit into
optimismfrom
seb/publish-built-payload

Conversation

@sebastianst

Copy link
Copy Markdown
Member

Adds PayloadBuilderHandle::publish_built_payload, which broadcasts a payload built outside a payload job to the payload service's subscribers as Events::BuiltPayload.

The node inserts the executed block of every Events::BuiltPayload into the engine tree (InsertExecutedBlock), which is what lets newPayload skip re-executing a block the node built itself. Only a resolved payload job could emit that event so far, so a payload built at the Engine API layer, e.g. an OP Stack derived payload built inside engine_forkchoiceUpdated, never reached the tree and newPayload executed it a second time.

🤖 Co-created with Claude Opus 5.5

Adds `PayloadBuilderHandle::publish_built_payload`, which broadcasts a payload to
the payload service's subscribers as `Events::BuiltPayload`. The node inserts the
executed block of every such event into the engine tree, so an Engine API
extension that builds a payload itself can hand it over the same way a resolved
payload job does, and `newPayload` of that block does not execute it again.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sebastianst

Copy link
Copy Markdown
Member Author

Not needed anymore since we chose ethereum-optimism/optimism#23454

@sebastianst
sebastianst deleted the seb/publish-built-payload branch October 21, 2026 08:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant