95dd846a9b
Currently, we don't have a good answer to the question "are we synced yet" - the sync manager syncs based on the peers it's connected to, but just because some peer looks like it should be synced from doesn't mean we're out of sync. Instead, we use a very silly time-based heuristic - the problem with that is that the network can go into a rut where nobody produces blocks - better heuristics would be needed here, but in the meantime, a command line option can get us out of a tight spot - this PR places such an option in the client, in the unlikely event it should be needed (most likely in a testnet). |
||
|---|---|---|
| .. | ||
| 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