Skip to content

Derive default auth data from the builder hostname #642

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nflaig merged 2 commits into from
Sep 18, 2026
Merged

Derive default auth data from the builder hostname #642

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2406d1e
Derive default auth data from the builder hostname
nflaig Sep 16, 2026
6fd48e2
restore dictionary.dic
nflaig Sep 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions types/gloas/request_auth.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,8 +11,9 @@ Gloas:
Opaque authentication data unique to the builder, agreed upon out of band. The meaning of
the up to `MAX_BUILDER_AUTH_DATA_SIZE` (4096) bytes is left to the two parties; the builder checks the
exact bytes when it verifies. When no value has been agreed out of band, implementations
SHOULD default to the UTF-8 bytes of the builder's own advertised URL, exactly as
advertised, so proposers with no prior relationship can construct an identical `data`
SHOULD default to the builder's hostname derived from its URL, see
[default auth data](https://github.com/ethereum/builder-specs/blob/main/specs/gloas/validator.md#default-auth-data),
so proposers with no prior relationship can construct an identical `data`
deterministically. A zero-length `data` is invalid.
example: "0x1234567890abcdef"
pattern: "^0x(?:[a-fA-F0-9]{2}){1,4096}$"
Expand Down
Loading