dfd7b9bc61
The proposed change ensures that VC validators are registered with the builder specified by the `--payload-builder-url` argument even if the beacon node has no attached validators. It also prevent such validators from being unintentionally registered with builders configured for specific attached validators by the keymanager api. Per the current specs, the VC have no way to specify which builders the BN should use on a per-node basis, so for the time being we have to resort to using the BN fallback default builder URL for VC validators. |
||
|---|---|---|
| .. | ||
| README.md | ||
| action_tracker.nim | ||
| activity_metrics.nim | ||
| beacon_validators.nim | ||
| keystore_management.nim | ||
| message_router.nim | ||
| message_router_mev.nim | ||
| slashing_protection.nim | ||
| slashing_protection_common.nim | ||
| slashing_protection_v2.nim | ||
| validator_duties.nim | ||
| validator_monitor.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