From a29cbebc0e314892865667b23db8ff75f76a3983 Mon Sep 17 00:00:00 2001 From: Jacek Sieka Date: Wed, 20 May 2020 09:51:47 +0200 Subject: [PATCH] cover `step` parameter in stricter range request --- specs/phase0/p2p-interface.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specs/phase0/p2p-interface.md b/specs/phase0/p2p-interface.md index fc457c58a..787c94c34 100644 --- a/specs/phase0/p2p-interface.md +++ b/specs/phase0/p2p-interface.md @@ -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. -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.