Description
The data column reconstruction deadline is currently set at 1/4 of a slot (3s on mainnet):
|
pub const RECONSTRUCTION_DEADLINE: (u64, u64) = (1, 4); |
This was chosen to align with the attestation deadline - reconstruct before validators need to attest so data is available in time.
With ePBS, the block and payload are separate. Regular attestations vote on the block at 1/4 slot, but payload + blob availability is attested to by the PTC at 3/4 slot (9s). Since reconstruction is specifically about making blob data available, it's arguably the payload attestation deadline that matters here, not the block attestation deadline.
A later deadline would give gossip more time to deliver remaining columns, potentially reducing unnecessary reconstructions. That said, the current deadline works fine and earlier reconstruction doesn't hurt correctness, so not sure this is worth changing.
Description
The data column reconstruction deadline is currently set at 1/4 of a slot (3s on mainnet):
lighthouse/beacon_node/beacon_processor/src/scheduler/work_reprocessing_queue.rs
Line 97 in effcd08
This was chosen to align with the attestation deadline - reconstruct before validators need to attest so data is available in time.
With ePBS, the block and payload are separate. Regular attestations vote on the block at 1/4 slot, but payload + blob availability is attested to by the PTC at 3/4 slot (9s). Since reconstruction is specifically about making blob data available, it's arguably the payload attestation deadline that matters here, not the block attestation deadline.
A later deadline would give gossip more time to deliver remaining columns, potentially reducing unnecessary reconstructions. That said, the current deadline works fine and earlier reconstruction doesn't hurt correctness, so not sure this is worth changing.