Clarify setting blob_data_available in PayloadAttestations
The validator spec to construct a PayloadAttestation didn't specify how to set blob_data_available to true.
We can set blob_data_available to true if is_data_available(data.beacon_block_root) is true. i.e if the validator which is part of the PTC has received the columns it has to sample.
Why have the field at all then? The block can't be canonical if is_data_available(data.beacon_block_root) is False.
Why have the field at all then? The block can't be canonical if
is_data_available(data.beacon_block_root)isFalse.
No, block can be imported without EL payload nor the sidecars. fork choice has been changed https://github.com/ethereum/consensus-specs/blob/master/specs/gloas/fork-choice.md#modified-on_block