antondlr

> However, execution clients can return jwt errors for other types of errors as well (e.g. incorrectly set vhosts on geth) which might be potentially confusing to debug. > The...

adding to this (important, essential even for production environments, imo) feature request; I'd prefer for the client to retry-loop, instead of fail, when its connection to the BN (or EE)...

I would like to re-surface this feature request now that mainnet setups are being rolled out. IMO this is essential for a robust, high-performance stack!

I added some small nitpicks, feel free to revert them! question; this does not expose over SSL currently, right? as that would create a new security hole while patching another...

it would also be nice to use the same template for `nginx_proxy.conf.template` and `siren-http{,s}.conf`, manipulating the template can be done from `docker-assets/docker-entrypoint.sh` (this is by no means a must!)

> Preventing the exfiltration of sensitive data (eg, keys) **from the container** can largely be achieved using egress rules. But **from the browser** is another another kettle of fish. I...

> [introduce logfile-color flag to enable/disable coloured logging to file](https://github.com/sigp/lighthouse/pull/6339/commits/d83eee097e70a178f25da5f1a344e245b214d5fa) oh _thank you_, as someone who has to parse logs I've got ... thoughts ... about ANSI control characters in...

> Doppelganger failure is exit code 137, which implies OOM. We should try: > > * [ ] Running a node on our infra (Holesky is fine) and observing log...

I've just tried a topup with Frame, waited ~ 5mins to sign the Tx. Siren picked it up nicely. This was using Chrome with the `Frame Companion` extension, and a...

Frame, Brave, `Frame Companion` set to metamask imitation Waited > 5 mins for signing a topup, and Siren did _not_ pick it It up same setup, `Frame Companion` set to...