Decouple validator from beacon node via traits#677
Open
bomanaps wants to merge 3 commits into
Open
Conversation
Author
|
cc @ArtiomTr |
ArtiomTr
reviewed
May 7, 2026
ArtiomTr
reviewed
May 7, 2026
ArtiomTr
reviewed
May 7, 2026
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
2 participants
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.
Refactored the validator so it talks to the beacon node through a small set of trait objects (BeaconChainReader, BeaconDutyEndpoints, BeaconPublisher, BeaconEventStream) instead of poking pools, channels, and the controller directly. Behavior is identical every call still resolves to the same in-process function via the new LocalBeaconClient impl but the seam is now in place to drop in a remote HTTP client later without touching the validator again.