a5151bc546
This PR renames the existing `validator_duties` to `beacon_validators` and in doing so, names validators running inside the beacon node process "beacon validators" while those running the VC can be referred to as "client validators" to disambiguate the two. The existing `validator_duties` instead takes on a new responsibility: as a home for logic shared between beacon and client validators - ie code that provides consistency in implementation and behavior between the two modes of operation. Not only does this simplify reasoning about where to put code -it also reduces the number of dependencies the validator client has from ~5000 to ~3000 modules (!) according to `nim genDepend` significantly reducing compile times. |
||
---|---|---|
.. | ||
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