feat: FlashblocksPubSubManager
#369
Open
Conversation
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Previously, the flashblocks implementation featured a
FlashblocksReceiverServiceresponsible for consuming the builder WebSocket stream, and aFlashblocksServicethat combined payload assembly, Engine API handling, and outbound broadcasting to builders.This PR introduces a
FlashblocksPubSubManagerto encapsulate subscription and publishing logic, decoupling it from Engine API responsibilities. A dedicatedFlashblocksProvidernow manages the in-memoryFlashblockBuilderstate 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.