Attestation efficiency

Retrieve normalized attestation inclusion effectiveness for one or more validators. Provide a comma-separated list of validator indices or 0x-prefixed BLS pubkeys (up to the server-enforced limit; default 100). The score is computed for the most recently completed epoch and defined as: score = 1 + (1 − percentage/100) = 2 − percentage/100. A score of 1.0 indicates perfect effectiveness (100% inclusion); scores approach 2.0 as effectiveness worsens (0% inclusion).

GET /api/v1/validator/{indexOrPubkey}/attestationefficiency

Attestation efficiency

cURL

curl --request GET \
  --url 'https://beaconcha.in/api/v1/validator/{indexOrPubkey}/attestationefficiency?apikey='

200

Example

{
  "status": "OK",
  "data": [
    {
      "validatorindex": 21,
      "attestation_efficiency": 1.0175
    }
  ]
}

Authorizations

ApiKeyAuthQueryApiKeyAuthHeader

apikey · string · query · required

Path Parameters

indexOrPubkey · string · required

Comma-separated validator indices and/or public keys (maximum 100 items by default). Comma-separated list (no spaces) of validator identifiers. Each identifier must be either:

• A validator index as a base-10 integer (for example, 652648)
• A BLS public key as a 96-hex-character string with or without the 0x prefix (case-insensitive)

Resolution and limits:

• The server resolves public keys to validator indices before querying data.
• The total number of identifiers must not exceed the server-enforced limit (default 100).
• Identifiers that cannot be parsed or resolved result in HTTP 400.

Example:

"1,2,3"

Response

200

application/json

Matching validators were retrieved successfully. The data array contains one entry per validator with the normalized attestation effectiveness score.

Standard success envelope used by all API endpoints.

status · enum<string>

HTTP-independent status of the API operation. For successful responses this is always "OK".

Available options: OK

data · object[]

Response payload specific to the endpoint.

Show child attributes