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

cover `step` parameter in stricter range request

This commit is contained in:
Jacek Sieka 2020-05-20 09:51:47 +02:00 committed by protolambda
parent 607e23949c
commit a29cbebc0e
No known key found for this signature in database
GPG Key ID: EC89FDBB2B4C7623
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -544,7 +544,7 @@ Clients MUST keep a record of signed blocks seen since the since the start of th
Clients MUST respond with at least the first block that exists in the range, if they have it. Clients MUST respond with at least the first block that exists in the range, if they have it.
The following blocks MUST be ordered consecutively, with each `parent_root` matching the `hash_tree_root` of the previous block. The following blocks, where they exist, MUST be send in consecutive order without gaps, as selected by `step`. In particular, when `step == 1`, each `parent_root` MUST match the `hash_tree_root` of the preceding block.
Clients MAY limit the number of blocks in the response. Clients MAY limit the number of blocks in the response.