search

Consensys / teku

Open-source Ethereum consensus client written in Java
https://consensys.io/teku
Apache License 2.0
656 stars 278 forks source link

Enable --beacon-node-api-endpoint option for Teku users running in single process mode #6092

Open gethwethreth opened 2 years ago

gethwethreth commented 2 years ago

Currently, --beacon-node-api-endpoint is only allowed when running Teku in validator-client mode. Upcoming Teku release has an enhancement to --beacon-node-api-endpoint that will allow users to specify multiple end-points for fallback support. It will be helpful to enable --beacon-node-api-endpoint for users running Teku in single process mode (beacon node and validator as a single process) too.

This will allow validators to setup fallback (if the EL is down or syncing and not current) without having to split their single process setup.

Here is a link to the discord discussion about this topic/request

ajsutton commented 2 years ago

The key reason you'd use a fallback in this case btw, is to handle the case where the EL is syncing or offline. Obviously if the primary beacon node is down the VC running in the same process is going to be down as well, but it's likely to be more common that the EL isn't ready and the fallback would be useful in that case.