Description:
I propose adding the ability to specify multiple beacon node endpoints (comma-separated) for validator clients. Instead of waiting for a failover when one beacon node fails, the validator client should send all tasks (e.g., attestation, block proposals, published blocks, duties) to all specified nodes simultaneously, similar to:
Additionally it allows nimbus and lighthouse to choose best MEV payload from all specified beacon nodes, making getHeader requests.
Use Case:
By using all beacon nodes at once, validator clients can avoid downtime or interruptions caused by waiting for failover. Even if one node becomes unavailable, the tasks are still processed by the remaining nodes, providing maximum reliability.
Benefits:
No Failover Delays: Tasks are sent to all nodes immediately, avoiding wait times for failover.
Increased Redundancy: Multiple nodes work in parallel, in HA manner
Description: I propose adding the ability to specify multiple beacon node endpoints (comma-separated) for validator clients. Instead of waiting for a failover when one beacon node fails, the validator client should send all tasks (e.g., attestation, block proposals, published blocks, duties) to all specified nodes simultaneously, similar to:
--proposer-nodes
flagAdditionally it allows nimbus and lighthouse to choose best MEV payload from all specified beacon nodes, making
getHeader
requests.Use Case: By using all beacon nodes at once, validator clients can avoid downtime or interruptions caused by waiting for failover. Even if one node becomes unavailable, the tasks are still processed by the remaining nodes, providing maximum reliability.
Benefits:
Thank you for considering this request.