github/consensus-specs
1
1
Fork 0
mirror of https://github.com/ethereum/consensus-specs.git synced 2026-02-01 21:45:15 -05:00
Code Issues Packages Projects Releases Wiki Activity

Clarify behavior for empty blobs sidecar

Browse Source
This commit is contained in:
terence tsao
2022-12-23 14:02:33 +08:00
parent 4f77493b0f
commit 5a75704e37
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
specs/eip4844/p2p-interface.md
View File

@@ -226,6 +226,8 @@ The request MUST be encoded as an SSZ-container.
The response MUST consist of zero or more `response_chunk`.
Each _successful_ `response_chunk` MUST contain a single `BlobsSidecar` payload.
In cases where a slot contains empty blob, no `blobs_sidecar` is returned.
Clients MUST keep a record of signed blobs sidecars seen on the epoch range
`[max(current_epoch - MIN_EPOCHS_FOR_BLOBS_SIDECARS_REQUESTS, EIP4844_FORK_EPOCH), current_epoch]`
where `current_epoch` is defined by the current wall-clock time,
@@ -247,6 +249,8 @@ disconnect and/or temporarily ban such an un-synced or semi-synced client.
Clients MUST respond with at least the first blobs sidecar that exists in the range, if they have it,
and no more than `MAX_REQUEST_BLOBS_SIDECARS` sidecars.
Clients MUST not respond with empty blobs sidecars.
The following blobs sidecars, where they exist, MUST be sent in consecutive order.
Clients MAY limit the number of blobs sidecars in the response.