This repository was archived by the owner on Jan 16, 2026. It is now read-only.
feat(node/net): rewire unsafe block sender from engine to network#2378
Merged
feat(node/net): rewire unsafe block sender from engine to network#2378
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
a2a8605 to
a769675
Compare
theochap
added a commit
to ethereum-optimism/optimism
that referenced
this pull request
Dec 10, 2025
…-rs/kona#2378) ## Description Rewire the sequencer unsafe payload sender from the engine to the network. Previously, the sequencer was sending the unsafe blocks it received from the network `BuildTask` back to the network to call `InsertUnsafeTask`. Since the `BuildTask` inserts the newly built payloads to the engine state (like what the `InsertUnsafeTask` would do), this resulted in a no-op. Instead, the sequencer should send the payloads to the network to gossip them to the p2p mesh. ## Misc Close op-rs/kona#2244 Built on top of op-rs/kona#2376
theochap
added a commit
to ethereum-optimism/optimism
that referenced
this pull request
Jan 14, 2026
…-rs/kona#2378) ## Description Rewire the sequencer unsafe payload sender from the engine to the network. Previously, the sequencer was sending the unsafe blocks it received from the network `BuildTask` back to the network to call `InsertUnsafeTask`. Since the `BuildTask` inserts the newly built payloads to the engine state (like what the `InsertUnsafeTask` would do), this resulted in a no-op. Instead, the sequencer should send the payloads to the network to gossip them to the p2p mesh. ## Misc Close #2244 Built on top of #2376
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Rewire the sequencer unsafe payload sender from the engine to the network.
Previously, the sequencer was sending the unsafe blocks it received from the network
BuildTaskback to the network to callInsertUnsafeTask. Since theBuildTaskinserts the newly built payloads to the engine state (like what theInsertUnsafeTaskwould do), this resulted in a no-op.Instead, the sequencer should send the payloads to the network to gossip them to the p2p mesh.
Misc
Close #2244
Built on top of #2376