remove gossip failure rules
This commit is contained in:
parent
cf39eeda3d
commit
ba09761ec3
|
@ -304,7 +304,6 @@ 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 SHOULD include a sidecar in the response as soon as it passes the gossip validation rules.
|
||||
Clients MUST NOT respond with sidecars that fail 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)`.
|
||||
|
||||
|
|
|
@ -857,7 +857,6 @@ 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 MUST NOT respond with blocks that fail gossip validation rules.
|
||||
Clients SHOULD NOT respond with blocks that fail 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