Validator Supply

Contents

• Flows to Lido Contract

• Supply in CL Contract

• Supply in Lido Contract

Flows to Lido Contract

Definition

Daily sent to the Lido staking contract.

Name	MetricID	Unit	Interval
Flows to Lido Contract	FlowToLidoCont	Native Units	1 day

Details

• Daily amount of ETH sent to the Lido staking contract (0xae7ab96520de3a18e5e111b5eaab095312d7fe84), sourced from Coin Metrics ATLAS™ blockchain search engine.

Release History

• Released September 2022.

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

Supply in CL Contract

Definition

Total supply sent to the Consensus Layer (CL) Contract.

Name	MetricID	Unit	Interval
Supply in CL Contract	SplyCLCont	Native Units	1 day

Details

• The total supply of ETH sent to the Consensus Layer (CL) smart contract (0x00000000219ab540356cBB839Cbe05303d7705Fa), sourced from Coin Metrics ATLAS™ blockchain search engine.

Release History

• Released September 2022.

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

Supply in Lido Contract

Definition

Total sent to the Lido staking contract.

Name	MetricID	Unit	Interval
Supply in Lido Contract	SplyLidoCont	Native Units	1 day

Details

• Total ETH sent to the Lido staking contract (0xae7ab96520de3a18e5e111b5eaab095312d7fe84) over the daily interval, sourced from Coin Metrics ATLAS™ blockchain search engine.

Release History

• Released September 2022.

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

API Endpoints

Validator Supply metrics can be accessed using these endpoints:

• timeseries/asset-metrics

and by passing in the metric ID's SplyLido* and FlowToLidoCont in the metrics parameter.

Asset metrics

Returns requested metrics for specified assets. Results for block by block metrics (1b frequency) are ordered by tuple (asset, height, block_hash), all other metrics are ordered by tuple (asset, time). You can change the sorting using sort query parameter. Supported output formats are json (default) and csv, use format query parameter to override it. To fetch the next page of results use next_page_url JSON response field or x-next-page-url CSV HTTP header if present. If multiple metrics are requested in the same time the strict policy for partially available metrics among requested ones is applied:

GEThttps://api.coinmetrics.io/v4/timeseries/asset-metrics

Authorization

api_key

Query parameters

Response

200400401403414

Time series of metrics for an asset.

Body

application/jsontext/csv

data*any

next_page_tokenNextPageToken (string)

Token of the next page results for a given request.

next_page_urlNextPageUrl (string)

URL of the next page results for a given request.

Response

200400401403

{
  "next_page_token": "text",
  "next_page_url": "text"
}

Shell

curl --compressed "https://api.coinmetrics.io/v4/timeseries/asset-metrics?metrics=FlowToLidoCont&assets=eth&pretty=true&api_key=<your_key>"

Python

import requests
response = requests.get('https://api.coinmetrics.io/v4/timeseries/asset-metrics?metrics=FlowToLidoCont&assets=eth&pretty=true&api_key=<your_key>').json()
print(response)

Python Client

from coinmetrics.api_client import CoinMetricsClient

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

print(
    client.get_asset_metrics(
        metrics="FlowToLidoCont", 
        assets="eth",
    ).to_dataframe()
)