rephrase
This commit is contained in:
parent
e2ca4b3519
commit
d749a49665
|
@ -306,7 +306,7 @@ 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 validation.
|
||||
Clients MUST NOT respond with sidecars related to blocks that failed `fork_choice.on_block`.
|
||||
Clients MAY continue serving blocks\sidecars after failed `fork_choice.on_block` only if the failure reason is due to `is_data_available` failing for missing blobs. (i.e. some sidecars are missing but the available ones have been fully verified against the fully validated block)."
|
||||
Clients MAY continue serving blocks\sidecars after failed `fork_choice.on_block` if and only if the failure reason is due to missing blobs. (i.e. some sidecars are missing but the available ones have been fully verified against the fully validated block).
|
||||
|
||||
##### BlobSidecarsByRange v1
|
||||
|
||||
|
|
Loading…
Reference in New Issue