POST /eth/v1/validator/liveness/{epoch}

Indicates if a validator has been observed on the network.

Asks the beacon node to report whether any validators have been seen to be active during a specific epoch. The validator's messages on the network, in the beacon chain, via its API, or from any other source could be the beacon node's way of determining when it is live. A beacon node MAY support an older epoch, but it MUST support the present and previous epochs. It is crucial to remember that the values the beacon node returns are best-effort and predicated on an arbitrary interpretation of the network, not canonical. A validator may appear to be down while it is actually online, as indicated by a beacon node that was recently restarted or experienced a network split.

Example Request and Result for /v1/validator/liveness/{epoch}

In this section, we provide an illustrative example of a request made to retrieve details contents using the /v1/validator/liveness/{epoch} endpoint. Additionally, we present the resulting response containing information about if a validator has been observed on the network.

Parameters

Fields	Type	Description
epoch*	string	The epoch for which liveness is being queried

The example in this section uses a non-existing project id.

Make sure you replace it with your Ethereum Holesky Beacon endpoint when issuing the API calls.

Don't have a project id? Here's a straightforward guide on how to obtain one!

Indicates if a validator has been observed on the network.

POST https://eth-holesky-beacon.blastapi.io/<project-id>/eth/v1/validator/register_validator

Path Parameters

Name	Type	Description
epoch*	string	1

200: OK Expand for a detailed response example

{
  "data": [
    {
      "index": "1",
      "is_live": true
    }
  ]
}

Curl Request example

curl -X 'POST' \
  'https://eth-holesky-beacon.blastapi.io/e<project-id>/eth/v1/validator/liveness/1' \
  -H 'accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '[
  "1"
]'