49729e1ef3
When a block is introduced to the system both via REST and gossip at the same time, we will call `storeBlock` from two locations leading to a dupliace check race condition as we wait for the EL. This issue may manifest in particular when using an external block builder that itself publishes the block onto the gossip network. * refactor enqueue flow * simplify calling `addBlock` * complete request manager verifier future for blobless blocks * re-verify parent conditions before adding block among other things, it might have gone stale or finalized between one call and the other |
||
|---|---|---|
| .. | ||
| README.md | ||
| action_tracker.nim | ||
| activity_metrics.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