You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Tracking issue for EIP-4844 tasks
Config & Setup
State transition & processing
is_data_available
check to fork-choiceon_block
ethereum/consensus-specs#3185)c-kzg-4844
library. (in progress https://github.com/henridf/nim-kzg-4844)P2P
beacon_block_and_blobs_sidecar
new topic. eip4844 gossip #4444beacon_block_and_blobs_sidecar
validationBeaconBlocksByRange v2
BeaconBlocksByRoot v2
BeaconBlockAndBlobsSidecarByRoot v1
(in progress Addbeacon_block_and_blobs_sidecar_by_root
RPC #4475)BlobsSidecarsByRange v1
(Blobs sidecars by range #4464)Storage
MIN_EPOCHS_FOR_BLOBS_SIDECARS_REQUESTS
epochs. Prune blobs #5283Sync
Also, keep in mind following two notes from eip4844. BlobsSidecarsByRange:
Validator duties
Testing
The text was updated successfully, but these errors were encountered: