Add ENR fields to execution clients page - #838
Merged
Merged
Conversation
Surface the enr field already returned by admin_nodeInfo / admin_peers on the EL clients page, mirroring the CL page: the node identity section gets an ENR row plus a decoded "ENR fields" list, and each connected peer's details show its ENR and decoded fields when the client reports one. Only strings starting with "enr:" are decoded (some clients report an enode URL in that field), and like the CL page the data is only included when ShowSensitivePeerInfos is enabled.
pk910
approved these changes
Aug 19, 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.
Summary
Surfaces the
enrfield already returned byadmin_nodeInfo/admin_peerson the execution clients page, mirroring the ENR display on the consensus clients page:Details
utils.DecodeENR/utils.GetKeyValuesFromENRhelpers into a sorted key/value list, cached per unique ENR string.enr:are decoded — some clients report an enode URL in theenrfield for peers without a signed record.ShowSensitivePeerInfosis enabled (ENRs contain IPs), and the template only renders the rows when an ENR is actually present.Client support (verified on glamsterdam-devnet-8)
admin_nodeInfo)admin_peers)All clients expose their own ENR, so the node identity section populates everywhere; per-peer ENRs currently only show up on geth/erigon (and only for peers found via discovery). Clients without ENR data render unchanged.