deprecate phase 0-only versions of beacon_blocks_by_{range,root}
This commit is contained in:
parent
189d61e386
commit
b5bcec8d34
|
@ -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/`
|
||||
|
|
Loading…
Reference in New Issue