4570f6e4ec
Validator clients such as Vouch can be configured to work with multiple beacon nodes simultaneously. In this configuration, the validator client will try to broadcast the gossip messages through each of the connected beacon nodes which may lead to a situation where some of the nodes see a message arriving from the network before it arrives through the REST API. This should not be considered an error and the beacon node should still broadcast the message as the intented purpose of the Vouch strategy is to ensure that the message will reach as many peers as possible. |
||
|---|---|---|
| .. | ||
| README.md | ||
| action_tracker.nim | ||
| keystore_management.nim | ||
| slashing_protection.nim | ||
| slashing_protection_common.nim | ||
| slashing_protection_v1.nim | ||
| slashing_protection_v2.nim | ||
| validator_duties.nim | ||
| validator_pool.nim | ||
README.md
Validators
This folder holds all modules related to a Beacon Chain Validator besides the binaries they interact directly with (nimbus_validator_cliant and nimbus_signing_process):
- Validator keystore
- Validator slashing protection
- Validator duties
- Validator pool