status-im
/
eth2.0-specs
mirror of https://github.com/status-im/eth2.0-specs.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
eth2.0-specs/specs/eip4844/p2p-interface.md

12 KiB
Raw Blame History

EIP-4844 -- Networking

This document contains the consensus-layer networking specification for EIP-4844.

The specification of these changes continues in the same format as the network specifications of previous upgrades, and assumes them as pre-requisite.

Table of contents

Configuration

Name Value Description
MAX_REQUEST_BLOBS_SIDECARS 2**7 (= 128) Maximum number of blobs sidecars in a single request
MIN_EPOCHS_FOR_BLOBS_SIDECARS_REQUESTS 2**12 (= 4096 epochs, ~18 days) The minimum epoch range over which a node must serve blobs sidecars

Containers

BlobsSidecar

class BlobsSidecar(Container):
    beacon_block_root: Root
    beacon_block_slot: Slot
    blobs: List[Blob, MAX_BLOBS_PER_BLOCK]
    kzg_aggregated_proof: KZGProof

SignedBeaconBlockAndBlobsSidecar

class SignedBeaconBlockAndBlobsSidecar(Container):
    beacon_block: SignedBeaconBlock
    blobs_sidecar: BlobsSidecar

The gossip domain: gossipsub

Some gossip meshes are upgraded in the fork of EIP4844 to support upgraded types.

Topics and messages

Topics follow the same specification as in prior upgrades. The beacon_block topic is deprecated and replaced by the beacon_block_and_blobs_sidecar topic. All other topics remain stable.

The specification around the creation, validation, and dissemination of messages has not changed from the Capella document unless explicitly noted here.

The derivation of the message-id remains stable.

The new topics along with the type of the data field of a gossipsub message are given in this table:

Name Message Type
beacon_block_and_blobs_sidecar SignedBeaconBlockAndBlobsSidecar (new)

Global topics

EIP4844 introduces a new global topic for beacon block and blobs-sidecars.

beacon_block

This topic is deprecated and clients MUST NOT expose in their topic set to any peer. Implementers do not need to do anything beyond simply skip implementation, and it is explicitly called out as it is a departure from previous versioning of this topic.

Refer to the section below for details on how to transition the gossip.

beacon_block_and_blobs_sidecar

This topic is used to propagate new signed and coupled beacon blocks and blobs sidecars to all nodes on the networks.

In addition to the gossip validations for the beacon_block topic from prior specifications, the following validations MUST pass before forwarding the signed_beacon_block_and_blobs_sidecar on the network. Alias signed_beacon_block = signed_beacon_block_and_blobs_sidecar.beacon_block, block = signed_beacon_block.message, execution_payload = block.body.execution_payload.

  • [REJECT] The KZG commitments of the blobs are all correctly encoded compressed BLS G1 Points. -- i.e. all(bls.KeyValidate(commitment) for commitment in block.body.blob_kzg_commitments)
  • [REJECT] The KZG commitments correspond to the versioned hashes in the transactions list. -- i.e. verify_kzg_commitments_against_transactions(block.body.execution_payload.transactions, block.body.blob_kzg_commitments)

Alias sidecar = signed_beacon_block_and_blobs_sidecar.blobs_sidecar.

  • [IGNORE] the sidecar.beacon_block_slot is for the current slot (with a MAXIMUM_GOSSIP_CLOCK_DISPARITY allowance) -- i.e. sidecar.beacon_block_slot == block.slot.
  • [REJECT] the sidecar.blobs are all well formatted, i.e. the BLSFieldElement in valid range (x < BLS_MODULUS).
  • [REJECT] The KZG proof is a correctly encoded compressed BLS G1 Point -- i.e. bls.KeyValidate(blobs_sidecar.kzg_aggregated_proof)
  • [REJECT] The KZG commitments in the block are valid against the provided blobs sidecar. -- i.e. validate_blobs_sidecar(block.slot, hash_tree_root(block), block.body.blob_kzg_commitments, sidecar)

Transitioning the gossip

See gossip transition details found in the Altair document for details on how to handle transitioning gossip topics for this upgrade.

The Req/Resp domain

Messages

BeaconBlocksByRange v2

Protocol ID: /eth2/beacon_chain/req/beacon_blocks_by_range/2/

The EIP-4844 fork-digest is introduced to the context enum to specify EIP-4844 beacon block type.

Per context = compute_fork_digest(fork_version, genesis_validators_root):

fork_version Chunk SSZ type
GENESIS_FORK_VERSION phase0.SignedBeaconBlock
ALTAIR_FORK_VERSION altair.SignedBeaconBlock
BELLATRIX_FORK_VERSION bellatrix.SignedBeaconBlock
CAPELLA_FORK_VERSION capella.SignedBeaconBlock
EIP4844_FORK_VERSION eip4844.SignedBeaconBlock

BeaconBlocksByRoot v2

Protocol ID: /eth2/beacon_chain/req/beacon_blocks_by_root/2/

After EIP4844_FORK_EPOCH, BeaconBlocksByRootV2 is replaced by BeaconBlockAndBlobsSidecarByRootV1 clients MUST support requesting blocks by root for pre-fork-epoch blocks.

Per context = compute_fork_digest(fork_version, genesis_validators_root):

fork_version Chunk SSZ type
GENESIS_FORK_VERSION phase0.SignedBeaconBlock
ALTAIR_FORK_VERSION altair.SignedBeaconBlock
BELLATRIX_FORK_VERSION bellatrix.SignedBeaconBlock
CAPELLA_FORK_VERSION capella.SignedBeaconBlock

BeaconBlockAndBlobsSidecarByRoot v1

Protocol ID: /eth2/beacon_chain/req/beacon_block_and_blobs_sidecar_by_root/1/

Request Content:

(
  List[Root, MAX_REQUEST_BLOCKS]
)

Response Content:

(
  List[SignedBeaconBlockAndBlobsSidecar, MAX_REQUEST_BLOCKS]
)

Requests blocks by block root (= hash_tree_root(SignedBeaconBlockAndBlobsSidecar.beacon_block.message)). The response is a list of SignedBeaconBlockAndBlobsSidecar whose length is less than or equal to the number of requests. It may be less in the case that the responding peer is missing blocks and sidecars.

No more than MAX_REQUEST_BLOCKS may be requested at a time.

BeaconBlockAndBlobsSidecarByRoot is primarily used to recover recent blocks and sidecars (e.g. when receiving a block or attestation whose parent is unknown).

The response MUST consist of zero or more response_chunk. Each successful response_chunk MUST contain a single SignedBeaconBlockAndBlobsSidecar payload.

Clients MUST support requesting blocks and sidecars since the latest finalized epoch.

Clients MUST respond with at least one block and sidecar, if they have it. Clients MAY limit the number of blocks and sidecars in the response.

BlobsSidecarsByRange v1

Protocol ID: /eth2/beacon_chain/req/blobs_sidecars_by_range/1/

Request Content:

(
  start_slot: Slot
  count: uint64
)

Response Content:

(
  List[BlobsSidecar, MAX_REQUEST_BLOBS_SIDECARS]
)

Requests blobs sidecars in the slot range [start_slot, start_slot + count), leading up to the current head block as selected by fork choice.

The response is unsigned, i.e. BlobsSidecarsByRange, as the signature of the beacon block proposer may not be available beyond the initial distribution via gossip.

Before consuming the next response chunk, the response reader SHOULD verify the blobs sidecar is well-formatted and correct w.r.t. the expected KZG commitments through validate_blobs_sidecar.

BlobsSidecarsByRange is primarily used to sync blobs that may have been missed on gossip.

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.

Clients MUST keep a record of signed blobs sidecars seen on the epoch range [max(GENESIS_EPOCH, current_epoch - MIN_EPOCHS_FOR_BLOBS_SIDECARS_REQUESTS), current_epoch] where current_epoch is defined by the current wall-clock time, and clients MUST support serving requests of blocks on this range.

Peers that are unable to reply to block requests within the MIN_EPOCHS_FOR_BLOBS_SIDECARS_REQUESTS epoch range SHOULD respond with error code 3: ResourceUnavailable. Such peers that are unable to successfully reply to this range of requests MAY get descored or disconnected at any time.

Note: The above requirement implies that nodes that start from a recent weak subjectivity checkpoint MUST backfill the local blobs database to at least epoch current_epoch - MIN_EPOCHS_FOR_BLOBS_SIDECARS_REQUESTS to be fully compliant with BlobsSidecarsByRange requests.

Note: Although clients that bootstrap from a weak subjectivity checkpoint can begin participating in the networking immediately, other peers MAY 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.

The following blobs sidecars, where they exist, MUST be sent in consecutive order.

Clients MAY limit the number of blobs sidecars in the response.

The response MUST contain no more than count blobs sidecars.

Clients MUST respond with blobs sidecars from their view of the current fork choice -- that is, blobs sidecars as included by blocks from the single chain defined by the current head. Of note, blocks from slots before the finalization MUST lead to the finalized block reported in the Status handshake.

Clients MUST respond with blobs sidecars that are consistent from a single chain within the context of the request.

After the initial blobs sidecar, clients MAY stop in the process of responding if their fork choice changes the view of the chain in the context of the request.

Design decision rationale

Why are blobs relayed as a sidecar, separate from beacon blocks?

This "sidecar" design provides forward compatibility for further data increases by black-boxing is_data_available(): with full sharding is_data_available() can be replaced by data-availability-sampling (DAS) thus avoiding all blobs being downloaded by all beacon nodes on the network.

Such sharding design may introduce an updated BlobsSidecar to identify the shard, but does not affect the BeaconBlock structure.