You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a Ethereum validator I would like to be able to use a Lighthouse validator client with redundant beacon nodes, without subscribing to all subnets.
Version
2.5.1
Present Behaviour
A Lighthouse VC can currently connect to several BNs for redundancy. However, it does not keep all of these BNs informed about its duties, only the currently preferred one. It is therefore required to configure the fallback beacon node with the --subscribe-all-subnets and --import-all-attestations flags, leading to an increased resource consumption.
Expected Behaviour
The VC should send update messages to all connected beacon nodes, so that all of them behave as if they were the only BN connected to the VC.
The text was updated successfully, but these errors were encountered:
Description
As a Ethereum validator I would like to be able to use a Lighthouse validator client with redundant beacon nodes, without subscribing to all subnets.
Version
2.5.1
Present Behaviour
A Lighthouse VC can currently connect to several BNs for redundancy. However, it does not keep all of these BNs informed about its duties, only the currently preferred one. It is therefore required to configure the fallback beacon node with the
--subscribe-all-subnets
and--import-all-attestations
flags, leading to an increased resource consumption.Expected Behaviour
The VC should send update messages to all connected beacon nodes, so that all of them behave as if they were the only BN connected to the VC.
The text was updated successfully, but these errors were encountered: