Skip to content

Commit

Permalink
Fix markdown, use multiple lines for change-control, and add step >= …
Browse files Browse the repository at this point in the history
…1 case
  • Loading branch information
protolambda committed May 20, 2020
1 parent 59a4314 commit 522e34e
Showing 1 changed file with 4 additions and 1 deletion.
5 changes: 4 additions & 1 deletion specs/phase0/p2p-interface.md
Original file line number Diff line number Diff line change
Expand Up @@ -532,7 +532,10 @@ Response Content:
)
```

Requests beacon blocks in the slot range `[start_slot, start_slot + count * step)`, leading up to the current head block as selected by fork choice. `step` defines the slot increment between blocks. For example, requesting blocks starting at `start_slot` 2 with a step value of 2 would return the blocks at slots [2, 4, 6, …]. In cases where a slot is empty for a given slot number, no block is returned. For example, if slot 4 were empty in the previous example, the returned array would contain [2, 6, …].
Requests beacon blocks in the slot range `[start_slot, start_slot + count * step)`, leading up to the current head block as selected by fork choice.
`step` defines the slot increment between blocks. For example, requesting blocks starting at `start_slot` 2 with a step value of 2 would return the blocks at slots [2, 4, 6, …].
In cases where a slot is empty for a given slot number, no block is returned. For example, if slot 4 were empty in the previous example, the returned array would contain [2, 6, …].
A request MUST NOT have a 0 slot increment, i.e. `step >= 1`.

`BeaconBlocksByRange` is primarily used to sync historical blocks.

Expand Down

0 comments on commit 522e34e

Please sign in to comment.