Overview
Use this guide to benchmark a selected staking entity against the network average and then drill down into sub-entities. You can view the currently supported public entity list at beaconcha.in/entities.API Endpoints: This guide uses
/api/v2/ethereum/entities, /api/v2/ethereum/performance-aggregate, /api/v2/ethereum/entity/sub-entities, and /api/v2/ethereum/validators/metadata.Why Benchmark vs Network?
Baseline Performance Check
Compare one entity against network-wide average performance over the same window.
Sub-Entity Diagnosis
Identify which operators are helping or hurting the parent entity score.
Incident Validation
Verify whether drops are entity-specific or market-wide.
Stakeholder Reporting
Produce clear entity-vs-network deltas for internal and external reporting.
| Metric | Best For | Luck Impact |
|---|---|---|
| BeaconScore | Relative performance | No |
| APY / ROI | Absolute returns | Yes |
For how BeaconScore is calculated and why it can differ from weighted alternatives, see BeaconScore vs. 3rd Party Metrics.
1. Get the Entity Score
Fetch entities and select your target row: Benchmarking with BeaconScore isolates validator operational quality by normalizing for proposal luck.beaconscore.
2. Get the Network Baseline
Request the same evaluation window for network aggregate:data.beaconscore.total as the network benchmark.
Keep the same
chain and evaluation_window for both entity and network requests to avoid skewed comparisons.3. Compare Entity vs Network
Compute:delta = entity_beaconscore - network_beaconscore
Reference thresholds:
- Green:
delta >= +0.0025 - Yellow:
-0.0025 < delta < +0.0025 - Red:
delta <= -0.0025
4. Drill Into Sub-Entities
Compare operator-level performance within the selected entity:beaconscore, net_share, validator_count.
5. Discover Entity Associations (Optional)
If you start from validator identifiers, map them first:entity and sub_entity.
Example: Python Script
Best Practices
Use 30d or 90d
Prefer longer windows for stable benchmarking and trend analysis.
Track Delta History
Store
entity - network deltas over time to detect persistent underperformance.Inspect Sub-Entity Mix
Re-check sub-entity rankings when parent performance changes materially.
Map Unknown Validators
Use validator metadata to classify validators before benchmarking.
Data Freshness
- Entity and sub-entity overview data is precomputed and updated hourly.
- Validator-to-entity assignments are updated once per day.

