berachain
sends an unauthenticated transaction on startup
Beacon-Kit 1.1.3 sends an unauthenticated request to the execution client on startup (for chain-id; see packet capture below).
This prompts an error from the execution client and causes considerable confusion. I've had to say many time it's an expected error.
Would be great if it just didn't do it.
First request out of beacon-kit on launch: T 127.0.0.1:64224 -> 127.0.0.1:32000 [AP] #322 POST / HTTP/1.1..Host: localhost:32000..User-Agent: Go-http-client/1.1..Con tent-Length: 61..Content-Type: application/json..Accept-Encoding: gzip....{ "id":1,"jsonrpc":"2.0","method":"eth_chainId","params":null}
T 127.0.0.1:32000 -> 127.0.0.1:64224 [AP] #325 HTTP/1.1 401 Unauthorized..Content-Type: application/json..Date: Mon, 03 Ma r 2025 21:41:59 GMT..Server: Kestrel..Transfer-Encoding: chunked....54..{"j sonrpc":"2.0","error":{"code":-32600,"message":"Authentication error"},"id" :null}..0....
reth[930099]: 2025-08-08T04:10:16.530687Z ERROR Invalid JWT: Authorization header is missing or invalid