github/consensus-specs
1
1
Fork 0
mirror of https://github.com/ethereum/consensus-specs.git synced 2026-02-01 12:05:04 -05:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #3014 from tersec/deprecate-phase0-beacon-blocks-req-resp

Browse Source 
deprecate phase 0-only versions of beacon_blocks_by_{range,root}
This commit is contained in:
Hsiao-Wei Wang
2022-11-29 22:09:13 +08:00
committed by GitHub
parent b65f1c21bf b5bcec8d34
commit b62c9e8779
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -745,6 +745,8 @@ For example, if slot 4 were empty in the previous example, the returned array wo
`step` is deprecated and must be set to 1. Clients may respond with a single block if a larger step is returned during the deprecation transition period.
`/eth2/beacon_chain/req/beacon_blocks_by_range/1/` is deprecated. Clients MAY respond with an empty list during the deprecation transition period.
`BeaconBlocksByRange` is primarily used to sync historical blocks.
The request MUST be encoded as an SSZ-container.
@@ -831,6 +833,8 @@ Clients MUST support requesting blocks since the latest finalized epoch.
Clients MUST respond with at least one block, if they have it.
Clients MAY limit the number of blocks in the response.
`/eth2/beacon_chain/req/beacon_blocks_by_root/1/` is deprecated. Clients MAY respond with an empty list during the deprecation transition period.
#### Ping
**Protocol ID:** `/eth2/beacon_chain/req/ping/1/`