Skip to content

Conversation

@0xKitsune
Copy link
Collaborator

Previously, the flashblocks implementation featured a FlashblocksReceiverService responsible for consuming the builder WebSocket stream, and a FlashblocksService that combined payload assembly, Engine API handling, and outbound broadcasting to builders.

This PR introduces a FlashblocksPubSubManager to encapsulate subscription and publishing logic, decoupling it from Engine API responsibilities. A dedicated FlashblocksProvider now manages the in-memory FlashblockBuilder state and handles Engine API payload serving. This design creates a clear separation of concerns, improves maintainability, and makes the system easier to reason about.

Tests and metrics are still being added but opening this draft for an initial round of review.

@0xKitsune 0xKitsune marked this pull request as ready for review July 10, 2025 17:59
Copy link
Contributor

@Dzejkop Dzejkop left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

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.

4 participants