d028baea2a
On `ELECTRA_FORK_EPOCH`, PeerDAS is not yet activated, hence the current mechanism based on `BlobSidecar` is still in use. With EIP-7688, the generalized indices of `BeaconBlockBody` get reindexed, changing the length of the inclusion proof within the `BlobSidecar`. Because network Req/Resp operations allow responses across fork boundaries, this creates the need for a `ForkedBlobSidecar` in that layer, same as already done for `ForkedSignedBeaconBock` for similar reasons. Note: This PR is only needed if PeerDAS is adopted _after_ EIP-7688. If PeerDAS is adopted _before_ EIP-7688, a similar PR may be needed for forked columns. Coincidental `Forked` jank can only be fully avoided if both features activate at the same epoch, actual changes to blobs aside. Delaying EIP-7688 for sole purpose of epoch alignemnt is not worth it. |
||
|---|---|---|
| .. | ||
| 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