Apply suggestions from code review
This commit is contained in:
parent
ba09761ec3
commit
d343b6f1d9
|
@ -254,6 +254,7 @@ 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
|
||||
|
||||
|
@ -305,7 +306,7 @@ 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 include sidecars related to blocks that fail `state_transition(block)`.
|
||||
Clients SHOULD NOT respond with sidecars related to blocks that fail the beacon chain state transition
|
||||
|
||||
##### BlobSidecarsByRange v1
|
||||
|
||||
|
|
|
@ -857,7 +857,7 @@ Clients MUST respond with at least one block, if they have it.
|
|||
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 beacon chain state transition.
|
||||
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.
|
||||
|
||||
|
|
Loading…
Reference in New Issue