Repository navigation
Add Gloas builder configuration management - #442
Merged
Merged
Conversation
This was referenced Oct 22, 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
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.
Adds per-validator Gloas / ePBS builder settings through the Keymanager API, with persisted overrides, bulk editing, client status reporting, and reload retries. Saved overrides stay separate from resolved client defaults, and existing fee-recipient restrictions remain enforced.
Validation: 67 tests pass, including 14 new regression tests; one existing notification test is skipped. Build, lint, formatting, and TypeScript checks pass. The production Docker image builds on ARM64, and production imports and cancellation pass on Node 24.21.0. An isolated server test saved and read back a valid 1.05 MB bulk configuration over both WebSocket and polling transports.
Live compatibility with validator, beacon, and signer clients remains unverified. Deployment requires clients implementing the Gloas builder configuration routes and signing semantics described in
docs/gloas-builder-config.md.