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

Specify RPC byRoot blocks-sidecars elegibility

This commit is contained in:
Enrico Del Fante 2023-11-16 17:29:16 +01:00
parent 8fa1f8ed0a
commit e664d407ca
No known key found for this signature in database
GPG Key ID: F435EFF90817FBA5
2 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
specs/deneb/p2p-interface.md
View File

@ -252,6 +252,9 @@ Per `context = compute_fork_digest(fork_version, genesis_validators_root)`:
No more than `MAX_REQUEST_BLOCKS_DENEB` may be requested at a time. No more than `MAX_REQUEST_BLOCKS_DENEB` may be requested at a time.
*[Modified in Deneb:EIP4844]*
Clients SHOULD consider including a block in the response as soon as it it passes the gossip validation rules.
##### BlobSidecarsByRoot v1 ##### BlobSidecarsByRoot v1
**Protocol ID:** `/eth2/beacon_chain/req/blob_sidecars_by_root/1/` **Protocol ID:** `/eth2/beacon_chain/req/blob_sidecars_by_root/1/`
@ -300,6 +303,10 @@ Clients MUST support requesting sidecars since `minimum_request_epoch`, where `m
Clients MUST respond with at least one sidecar, if they have it. Clients MUST respond with at least one sidecar, if they have it.
Clients MAY limit the number of blocks and sidecars in the response. Clients MAY limit the number of blocks and sidecars in the response.
Clients SHOULD consider including a sidecar in the response as soon as it passes the gossip validation rules.
Clients MUST NOT respond with sidecars that failed gossip vaildation.
Clients MUST NOT respond with sidecars related to blocks that failed `fork_choice.on_block`.
##### BlobSidecarsByRange v1 ##### BlobSidecarsByRange v1
**Protocol ID:** `/eth2/beacon_chain/req/blob_sidecars_by_range/1/` **Protocol ID:** `/eth2/beacon_chain/req/blob_sidecars_by_range/1/`

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

@ -856,6 +856,10 @@ Clients MUST support requesting blocks since the latest finalized epoch.
Clients MUST respond with at least one block, if they have it. Clients MUST respond with at least one block, if they have it.
Clients MAY limit the number of blocks in the response. Clients MAY limit the number of blocks in the response.
Clients CAN consider including a block in the response as soon as it it passes the gossip validation rules.
Clients MUST NOT respond with blocks that failed gossip vaildation rules.
Clients MUST NOT respond with blocks that failed `fork_choice.on_block`.
`/eth2/beacon_chain/req/beacon_blocks_by_root/1/` is deprecated. Clients MAY respond with an empty list during the deprecation transition period. `/eth2/beacon_chain/req/beacon_blocks_by_root/1/` is deprecated. Clients MAY respond with an empty list during the deprecation transition period.
##### Ping ##### Ping