Description
Sometimes to maximise the chance of timely inclusion a node operator may want to have their validator client submit duties (attestations and proposals) to all connected beacon nodes, for redundancy. (This should be safe since only one validator client is operating so all submitted attestations should be the same and compatible, even if they are seen by different parts of the network initially.)
Version
All versions so far (up to 4.3.0).
Present Behaviour
Currently Lighthouse does not support broadcasting to all connected beacon nodes, and instead seems to only submit to the first/best node it knows about.
This seems to be the behaviour despite the existence of the --disable-run-on-all option.
Expected Behaviour
When provided with an appropriate option (e.g. --broadcast-duties), submit duties to all connected beacon nodes.
Description
Sometimes to maximise the chance of timely inclusion a node operator may want to have their validator client submit duties (attestations and proposals) to all connected beacon nodes, for redundancy. (This should be safe since only one validator client is operating so all submitted attestations should be the same and compatible, even if they are seen by different parts of the network initially.)
Version
All versions so far (up to 4.3.0).
Present Behaviour
Currently Lighthouse does not support broadcasting to all connected beacon nodes, and instead seems to only submit to the first/best node it knows about.
This seems to be the behaviour despite the existence of the
--disable-run-on-alloption.Expected Behaviour
When provided with an appropriate option (e.g.
--broadcast-duties), submit duties to all connected beacon nodes.