Nico Flaig

> Vouch uses a submitter strategy to know where to send data. If this is configured by the user to send to all nodes (the `multinode` strategy) then all beacon...

A fix https://github.com/ChainSafe/lodestar/pull/6668 has been included in our latest release [v1.18.0](https://github.com/ChainSafe/lodestar/releases/tag/v1.18.0), feel free to reopen if you can still observe this issue. > Vouch uses a submitter strategy to know...

~~Could be related to the memory leak we are observing on some nodes? As far as I remember this warning only happens with connected validators~~ Seems unrelated

Possibly related listeners warning ``` (node:7) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 101 message listeners added to [Worker]. Use emitter.setMaxListeners() to increase limit at genericNodeError (node:internal/errors:984:15) at wrappedFn (node:internal/errors:538:14) at...

This issue should be fixed by - https://github.com/libp2p/js-libp2p/pull/2417 Just need to update all libp2p libs to latest

related https://github.com/ChainSafe/lodestar/pull/5161#discussion_r1124678745

As suggested in the standup we could embed a API reference page (similar to CLI reference), I used [redoc](https://github.com/Redocly/redoc) previously to do this and the results were pretty good, see...

Looks good on my mainnet node as well, holesky also not too bad, closing this for now. Thanks @eth2353 for the metrics :pray:

Thanks for bringing this up! > one imagines that once a validator has been withdrawn it is no longer eligible for block proposals That is correct and we are filtering...

Thanks for reporting this! I thought this was already covered by https://github.com/ChainSafe/lodestar/pull/5714 and https://github.com/ChainSafe/lodestar/pull/5405 but it looks like we only ignore if we publish a blinded block. Should be easy...