> For the complete documentation index, see [llms.txt](https://gitbook-docs.coinmetrics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook-docs.coinmetrics.io/network-data/network-data-overview/supply/validator-supply.md).

# Staking Supply

## Contents

* [Supply Staked in Validators](#splystkedntc)
* [Active Staked Supply](#splyactstkedntv)
* [Total Staked Supply](#splytotstkedntv)
* [Average Supply Staked by Active Validators](#splystkedactmeanntv)

## Supply Staked by Stakers <a href="#splystkedntc" id="splystkedntc"></a>

### Definition

Supply staked in validators.

| Name                                    | MetricID     | Unit         | Interval      |
| --------------------------------------- | ------------ | ------------ | ------------- |
| Supply Staked by Stakers (native units) | SplyStkedNtv | Native Units | 1 day, 1 hour |
| Supply Staked by Stakers (USD)          | SplyStkedUSD | USD          | 1 day         |

### Details

* For Ethereum:
  * Sum of all balances from all eligible active validators (validators with 'active' or 'pending' status).
* For other assets:
  * Sum of all balances from all eligible stakers (delegators + validators)

### Release History

* Released September 2022.

## Active Staked Supply <a href="#splyactstkedntv" id="splyactstkedntv"></a>

### Definition

Supply from validators that were active that day.

<table><thead><tr><th>Name</th><th width="159">MetricID</th><th>Unit</th><th>Interval</th></tr></thead><tbody><tr><td>Sum of all balances from active stakers (native units)</td><td>SplyActStkedNtv</td><td>Native Units</td><td>1 day, 1 hour</td></tr><tr><td>Sum of all balances from active stakers (USD)</td><td>SplyActStkedUSD</td><td>USD</td><td>1 day</td></tr><tr><td>Sum of all balances from active delegators (native units)</td><td>SplyDelegatorActStkedNtv</td><td>Native units</td><td>1 day</td></tr><tr><td>Sum of all balances from active delegators (USD)</td><td>SplyDelegatorActStkedUSD</td><td>USD</td><td>1 day</td></tr><tr><td>Sum of all balances from active validators (native units)</td><td>SplyValidatorActStkedNtv</td><td>Native Units</td><td>1 day</td></tr><tr><td>Sum of all balances from active validators (USD)</td><td>SplyValidatorActStkedUSD</td><td>USD</td><td>1 day</td></tr></tbody></table>

### Details

* Sum of all balances from actively participating stakers.

### Release History

* Released September 2022.

## Total Staked Supply <a href="#splytotstkedntv" id="splytotstkedntv"></a>

### Definition

Sum of all balances held by all validators.

| Name                               | MetricID        | Unit         | Interval      |
| ---------------------------------- | --------------- | ------------ | ------------- |
| Total Staked Supply (native units) | SplyTotStkedNtv | Native Units | 1 day, 1 hour |
| Total Staked Supply (USD)          | SplyTotStkedUSD | USD          | 1 day         |

### Details

* Sum of all actual balances held by validators whose active epoch range intersects the current interval. Unlike `SplyStkedNtv` and `SplyActStkedNtv`, this metric uses each validator's actual balance rather than effective balance.

### Release History

* Released September 2022.

## Average Supply Staked by Active Validators <a href="#splystkedactmeanntv" id="splystkedactmeanntv"></a>

### Definition

The mean supply held across all active stakers.

| Name                                       | MetricID            | Unit         | Interval |
| ------------------------------------------ | ------------------- | ------------ | -------- |
| Average Supply Staked by Active Validators | SplyStkedActMeanNtv | Native units | 1 day    |

### Details

* Mean staked supply per active validator, computed as `SplyActStkedNtv / ValidatorActOngCnt`.
* Provides a per-validator view of average stake size, useful for tracking consolidation and effective balance trends.

### Availability for Assets

{% embed url="<https://coverage.coinmetrics.io/asset-metrics/SplyStkedActMeanNtv>" %}

## API Endpoints

Validator Supply metrics can be accessed using these endpoints:

* `timeseries/asset-metrics`

and by passing in the metric ID's `SplyStked*` in the `metrics` parameter.

{% openapi src="/files/kc3C7O6zTLYNBA0AcsZt" path="/timeseries/asset-metrics" method="get" %}
[openapi.yaml](https://2398817338-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MO23j33wWGzm0NrZseN%2Fuploads%2Fgit-blob-a236d0d04b3b155748ce07a17aca8108fce9b7c2%2Fopenapi.yaml?alt=media)
{% endopenapi %}

{% tabs %}
{% tab title="Shell" %}

```shell
curl --compressed "https://api.coinmetrics.io/v4/timeseries/asset-metrics?metrics=SplyStkedNtv&assets=eth_cl&frequency=1h&pretty=true&api_key=<your_key>"
```

{% endtab %}

{% tab title="Python" %}

```python
import requests
response = requests.get('https://api.coinmetrics.io/v4/timeseries/asset-metrics?metrics=SplyStkedNtv&assets=eth_cl&frequency=1h&pretty=true&api_key=<your_key>').json()
print(response)
```

{% endtab %}

{% tab title="Python Client" %}

```python
from coinmetrics.api_client import CoinMetricsClient

api_key = "<API_KEY>"
client = CoinMetricsClient(api_key)

print(
    client.get_asset_metrics(
        metrics="SplyStkedNtv", 
        assets="eth_cl",
    ).to_dataframe()
)
```

{% endtab %}
{% endtabs %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://gitbook-docs.coinmetrics.io/network-data/network-data-overview/supply/validator-supply.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.