From 5a75704e37304f02e611dcc9b9cee3607a76f2a2 Mon Sep 17 00:00:00 2001 From: terence tsao Date: Fri, 23 Dec 2022 14:02:33 +0800 Subject: [PATCH] Clarify behavior for empty blobs sidecar --- specs/eip4844/p2p-interface.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/specs/eip4844/p2p-interface.md b/specs/eip4844/p2p-interface.md index 420a6da05..2ab39ea09 100644 --- a/specs/eip4844/p2p-interface.md +++ b/specs/eip4844/p2p-interface.md @@ -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.