Introduction

Overview

BeaconScore is a transparent, comprehensive metric that measures how well your validators perform their duties. It combines attestations, block proposals, and sync committee participation into a single score.

API Endpoints: This guide covers /api/v2/ethereum/validators/performance-aggregate for summary metrics and /api/v2/ethereum/validators/performance-list for per-epoch breakdowns.

BeaconScore is designed to normalize for luck—validators with fewer block proposals aren’t unfairly penalized. This makes it ideal for comparing performance across different validators, nodes, or client configurations. Note that some residual luck factors outside a validator’s control can still influence the score, especially over short evaluation windows.

Why Monitor Performance?

Identify Issues Early

Spot underperforming validators before they significantly impact your rewards.

Compare Configurations

Evaluate different client software, hardware setups, or network configurations.

Client Reporting

Provide transparent performance metrics to your staking customers.

Optimize Operations

Track improvements over time and validate infrastructure changes.

BeaconScore Components

BeaconScore integrates three components weighted by their contribution to validator rewards:

Component	Weight	Description
Attestations	84.4%	Head, source, and target votes each epoch (~6.4 min)
Block Proposals	12.5%	CL rewards from proposed blocks (luck-normalized; see residual factors)
Sync Committees	3.1%	Participation when elected to sync committee

Learn more about how each component is calculated in BeaconScore.

Benchmark Values

BeaconScore	Rating	Action
≥ 99.5%	Excellent	Optimal performance
99.0% - 99.5%	Good	Within acceptable range
98.0% - 99.0%	Fair	Minor issues, monitor closely
< 98.0%	Poor	Investigate immediately

Quick Start: Check Your Performance

Get the aggregated BeaconScore for your validators over the last 30 days:

curl --request POST \
  --url https://beaconcha.in/api/v2/ethereum/validators/performance-aggregate \
  --header 'Authorization: Bearer <YOUR_API_KEY>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "chain": "mainnet",
  "validator": {
    "dashboard_id": 123
  },
  "range": {
    "evaluation_window": "30d"
  }
}
'

Response

{
  "data": {
    "beaconscore": {
      "total": 0.9945,
      "attestation": 0.9952,
      "proposal": 0.9876,
      "sync_committee": 0.9991
    },
    "duties": {
      "attestation": {
        "included": 7983797,
        "assigned": 7985250,
        "missed": 1453
      },
      "proposal": {
        "successful": 229,
        "assigned": 231,
        "missed": 2
      },
      "sync_committee": {
        "successful": 134833,
        "assigned": 135818,
        "missed": 985
      }
    }
  },
  "range": {
    "epoch": { "start": 407453, "end": 414202 }
  }
}

Per-Epoch Performance History

For detailed analysis, query performance for specific epochs:

curl --request POST \
  --url https://beaconcha.in/api/v2/ethereum/validators/performance-list \
  --header 'Authorization: Bearer <YOUR_API_KEY>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "chain": "mainnet",
  "validator": {
    "validator_identifiers": [1, 2, 3]
  },
  "epoch": 413950,
  "page_size": 100
}
'

The epoch parameter is required for the performance-list endpoint. Use this to investigate specific time periods or track performance over time.

Choose an Evaluation Window

Use the same window for every value in a comparison. Available windows are 24h, 7d, 30d, 90d, and all_time. See the Performance Aggregate API reference. On Scale and Enterprise plans you can also pass a custom timestamp, epoch, or slot range instead of a named window. Custom ranges are served at whole-UTC-day granularity, and the response range echoes the actual covered range.

Best Practices

Use 30-Day Windows

Short windows are noisy due to luck. Use 30d or longer for meaningful comparisons.

Group by Infrastructure

Create dashboard groups for each node, client, or geographic location.

Set Alerts

Configure notifications for performance drops.

Regular Reviews

Schedule weekly or monthly performance reviews to catch gradual degradation.

Deep Dive Guides

Analyze Missed Rewards

Per-epoch breakdown of rewards lost due to missed duties. Diagnose issues by duty type (attestations, proposals, sync).

APY & ROI Metrics

Aggregated return metrics with EL/CL breakdown. Includes missed reward impact on overall APY.

Embed BeaconScore

Integrate BeaconScore into your product with attribution guidelines.

BeaconScore Calculation — Deep dive into the formula
Dashboard as Private Sets — Organize validators into groups
Notifications — Set up performance alerts

API references: Performance Aggregated and Performance List.

V2 API Docs

V1 API Docs

Introduction

Overview

Why Monitor Performance?

Identify Issues Early

Compare Configurations

Client Reporting

Optimize Operations

BeaconScore Components

Benchmark Values

Quick Start: Check Your Performance

Response

Per-Epoch Performance History

Choose an Evaluation Window

Best Practices

Use 30-Day Windows

Group by Infrastructure

Set Alerts

Regular Reviews

Deep Dive Guides

Analyze Missed Rewards

APY & ROI Metrics

Embed BeaconScore

​Overview

​Why Monitor Performance?

Identify Issues Early

Compare Configurations

Client Reporting

Optimize Operations

​BeaconScore Components

​Benchmark Values

​Quick Start: Check Your Performance

​Response

​Per-Epoch Performance History

​Choose an Evaluation Window

​Best Practices

Use 30-Day Windows

Group by Infrastructure

Set Alerts

Regular Reviews

​Deep Dive Guides

Analyze Missed Rewards

APY & ROI Metrics

Embed BeaconScore

​Related Resources

Overview

Why Monitor Performance?

BeaconScore Components

Benchmark Values

Quick Start: Check Your Performance

Response

Per-Epoch Performance History

Choose an Evaluation Window

Best Practices

Deep Dive Guides

Related Resources