Skip to content

Clarify setting blob_data_available in PayloadAttestations #4769

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
bharath-123 wants to merge 3 commits into from
Closed

Clarify setting blob_data_available in PayloadAttestations #4769

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9d525db
spec out how to set blob_data_available
bharath-123 Dec 2, 2025
015711e
fix lint
bharath-123 Dec 2, 2025
b14335e
address justin's comment
bharath-123 Dec 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions specs/gloas/validator.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -198,6 +198,7 @@ The validator creates `payload_attestation_message` as follows:
- If a previously seen `SignedExecutionPayloadEnvelope` references the block
with root `data.beacon_block_root`, set `data.payload_present` to `True`;
otherwise, set `data.payload_present` to `False`.
- Set `data.blob_data_available` to `is_data_available(data.beacon_block_root)`.
- Set `payload_attestation_message.validator_index = validator_index` where
`validator_index` is the validator chosen to submit. The private key mapping
to `state.validators[validator_index].pubkey` is used to sign the payload
Expand Down