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

Merge pull request #3551 from tbenr/specify_rpc_by_root_elegibility 

Specify when clients can serve block and sidecars in byRoot RPC methods
This commit is contained in:
Hsiao-Wei Wang 2023-12-05 00:05:16 +09:00 committed by GitHub
parent 113c58f9bf d343b6f1d9
commit 06fe616558
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -252,6 +252,10 @@ 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 include a block in the response as soon as it passes the gossip validation rules.
Clients SHOULD NOT respond with blocks that fail the beacon chain state transition.
##### 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 +304,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 include a sidecar in the response as soon as it passes the gossip validation rules.
Clients SHOULD NOT respond with sidecars related to blocks that fail gossip validation rules.
Clients SHOULD NOT respond with sidecars related to blocks that fail the beacon chain state transition
##### 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/`

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

@ -856,6 +856,9 @@ 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 MAY include a block in the response as soon as it passes the gossip validation rules.
Clients SHOULD NOT respond with blocks that fail the beacon chain state transition.
`/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