Skip to content

feat(builderapi): accept the builder hostname as request auth data - #192

Merged
pk910 merged 1 commit into
ethpandaops:mainfrom
nflaig:nflaig/builder-auth-data-hostname
Sep 18, 2026
Merged

pk910 merged 1 commit into
ethpandaops:mainfrom
nflaig:nflaig/builder-auth-data-hostname

Conversation

@nflaig

@nflaig nflaig commented Sep 17, 2026

Copy link
Copy Markdown
Contributor

builder-specs is changing the default BuilderRequestAuth.data from the UTF-8 bytes of the builder URL to the URL's hostname in ethereum/builder-specs#168, so that a trailing slash, an explicit default port or different casing on the proposer side no longer fails the builder's check.

Both ePBS handlers now accept the hostname derived from --builder-api-url: lowercased, with IPv6 literals in brackets in their compressed form using hexadecimal groups only. The URL bytes verbatim are still accepted, since validator clients on the devnets and the lodestar image in the e2e config sign those until they adopt the new default. That path can be dropped once they have.

@pk910
pk910 merged commit cca24f1 into ethpandaops:main Sep 18, 2026
3 checks passed
pull Bot pushed a commit to Hawthorne001/prysm that referenced this pull request Sep 22, 2026
…nLabs#17511)

**What type of PR is this?**

> Feature

**What does this PR do? Why is it needed?**

- ethereum/builder-specs#168

Implements this spec change.

**Which issue(s) does this PR fix?**

N/A

**Other notes for review**

Note that using the current version of buildoor would probably have some
trouble as buildoor is not yet updated (Nico already opened a
[PR](ethpandaops/buildoor#192) for this). So I'd
suggest to merge this PR **after** all open PRs are merged.

**Acknowledgements**

- [x] I have read
[CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md).
- [x] I have included a uniquely named [changelog fragment
file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd).
- [x] I have added a description with sufficient context for reviewers
to understand this PR.
- [ ] I have tested that my changes work as expected and I added a
testing plan to the PR description (if applicable).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants