Jim McDonald

### Describe the bug Starting prysm with `--p2p-max-peers=64` I'm seeing larger numbers of peers on many nodes, e.g. ``` curl -s http://localhost:8080/metrics | egrep '^connected_libp2p_peers{' connected_libp2p_peers{agent="lighthouse"} 26 connected_libp2p_peers{agent="lodestar"} 5 connected_libp2p_peers{agent="nimbus"}...

This option allows selection of either CONSOLE (the default, and the current behaviour) or JSON for log output, allowing for easier parsing of output for structued log backends.

Add Attestant endpoints for sepolia and hoodi.

Standardizing the spec endpoint

8

The `/eth/v1/config/spec` endpoint should in theory return the same information from each beacon node client, however in practice it does not. The recent issue with holesky has highlighted the benefit...

Block headers returning incorrect public key.

5

**Describe the bug** The spec at https://ethereum.github.io/builder-specs/#/Builder/getHeader states that the `pubkey` field in the `message` struct is the public key of the builder, however the public key of the relay...