0e6a7cd39a
* deprecate `BeaconBlocksByRange.step` The `step` parameter has not seen much implementation in real life clients which instead opt to request variations on a few epochs at a time (instead of interleaving single blocks, entire epochs are interleaved). At the same time, supporting `step` on the server side brings several complications: more complex bounds checking logic, more complex loading of blocks from linear storage (which presumably stores all blocks and not just certain increments). This PR suggests that we deprecate the whole idea. Backwards compatibility is kept by simply responding with a single block when `step > 0` - this is allowed by the spec and should thus be handled gracefully by requesting clients already, should there exist any that use larger step counts. Removing `step` now allows simplifying the EL-CL protocol for serving execution data from the EL to avoid double storage. * Update specs/phase0/p2p-interface.md Co-authored-by: Danny Ryan <dannyjryan@gmail.com> Co-authored-by: Danny Ryan <dannyjryan@gmail.com> |
||
|---|---|---|
| .. | ||
| beacon-chain.md | ||
| deposit-contract.md | ||
| fork-choice.md | ||
| p2p-interface.md | ||
| validator.md | ||
| weak-subjectivity.md | ||