feat(client): spawn LH ProposerPreferencesService with AnchorValidatorStore backend - #1144
Merged
mergify[bot] merged 1 commit intoJul 22, 2026
Merged
Conversation
petarjuki7
requested review from
jnhsigmap and
shane-moore
and removed request for
jnhsigmap
July 16, 2026 09:49
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## epbs #1144 +/- ##
=======================================
Coverage ? 67.85%
=======================================
Files ? 164
Lines ? 30720
Branches ? 0
=======================================
Hits ? 20844
Misses ? 9876
Partials ? 0
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
…rStore backend Construct Lighthouse's ProposerPreferencesService with AnchorValidatorStore and start it via start_update_service(), inside the existing is_gloas_scheduled() gate next to PayloadAttestationService. Completes the Anchor-side ProposerPreferences pipeline: LH's service drives sign_proposer_preferences (sigp#1063) per validator per epoch, dispatching both proposal_data and signing through Anchor's ValidatorStore impl. Part of sigp#1064.
petarjuki7
force-pushed
the
feat/proposer-preferences-service
branch
from
July 22, 2026 13:49
95254b7 to
d09f9d1
Compare
|
Queued — the merge queue status continues in this comment ↓. |
Merge Queue Status
This pull request spent 41 minutes 5 seconds in the queue, including 39 minutes 1 second running CI. Required conditions to merge
|
7 tasks
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
3 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.
Part of #1064 (ePBS Proposer Preferences duty milestone, SIP-94 §5).
Wires Lighthouse's
ProposerPreferencesService(withAnchorValidatorStoreas the backend) into client startup, inside the existingis_gloas_scheduled()gate next toPayloadAttestationService. Completes the Anchor-side pipeline: LH's service drivessign_proposer_preferences(#1063) per validator per epoch, dispatching bothproposal_dataand the signing through Anchor'sValidatorStoreimpl.No new tests: the client crate has none and no sibling spawned service is tested — the behavior is LH's; Anchor's role is wiring (compile + startup).
Stacked on #1125 (#1063) — those commits drop out of this diff once it merges.
End-to-end SIP-94 §5 behavior additionally needs the upstream LH fix that schedules newly-added
(dependent_root, proposal_slot, validator)tuples (the current key is(epoch, dependent_root)only); tracked in the issue.