status-im/eth2.0-specs
2
0
Fork 0
mirror of https://github.com/status-im/eth2.0-specs.git synced 2025-02-02 22:03:37 +00:00
Code Issues Projects Releases Wiki Activity

simplify and add a new rule

Browse Source
This commit is contained in:
Enrico Del Fante 2023-11-30 16:11:33 +01:00
parent bdac932ebb
commit c661e20e60
No known key found for this signature in database
GPG Key ID: F435EFF90817FBA5
2 changed files with 5 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -255,11 +255,6 @@ 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.
*[New in Deneb:EIP4844]*
Clients SHOULD NOT include blocks for which one of the following conditions is met:
- `state_transition(block)` fails.
- the kzg proof of an available blob is invalid with respect to `blob_kzg_commitments` in the `block` (i.e. `verify_blob_kzg_proof_batch` fails on one or more known blobs).
##### BlobSidecarsByRoot v1
**Protocol ID:** `/eth2/beacon_chain/req/blob_sidecars_by_root/1/`
@ -309,9 +304,9 @@ 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 SHOULD NOT include sidecars related to blocks for which one of the following conditions is met:
- `state_transition(block)` fails.
- the kzg proof of an available blob is invalid with respect to `blob_kzg_commitments` in the `block` (i.e. `verify_blob_kzg_proof_batch` fails on one or more known blobs).
Clients MUST NOT respond with sidecars that fails gossip validation rules.
Clients MUST 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)`.
##### BlobSidecarsByRange v1

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

@ -857,8 +857,8 @@ 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 failed gossip validation rules.
Clients MUST NOT respond with blocks that failed `fork_choice.on_block`.
Clients MUST NOT respond with blocks that fail gossip validation rules.
Clients SHOULD NOT include blocks that fail `state_transition(block)`.
`/eth2/beacon_chain/req/beacon_blocks_by_root/1/` is deprecated. Clients MAY respond with an empty list during the deprecation transition period.