Current Supply

Contents

• Total Base Fees Burnt

• NDF (Network Distribution Factor)

• SER (Supply Equality Ratio)

• Value in Top X% of Addrs (native units)

• Value in Top 100 Addrs (native units)

• Current Supply, Execution Layer (native units)

Current Supply (native units)

Definition

The sum of all native units ever created and currently visible on the ledger (i.e., issued) as of that day. For account-based protocols, only accounts with positive balances are counted.

Name	MetricID	Unit	Interval
Current Supply (native units)	SplyCur	Native units	All time

Details

• This metric might be also be characterized as “total issued supply” as it captures the sum of all native units visible in the ledger up until the metric calculation point

• For UTXO chains, current supply is the sum of all unspent output values.

• For account chains, current supply is the sum of all account balances.

Chart

Source: CM Network Data Charts

Asset-Specific Details

• For ZEC, it includes the shielded pools value

• For Ripple, escrows are counted towards total current supply.

• For privacy coins like Monero or Grin, total current supply is computed by summing up mining rewards.

• For Solana, includes inflation from staking rewards and deflation from burnt coins

Release History

• Released in the 1.0 release of NDP

See Also

• Shielded Supply

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

NDF (Network Distribution Factor)

Definition

The ratio of supply held by addresses with at least one ten-thousandth of the current supply of native units to the current supply.

Name	MetricID	Unit	Interval
NDF (Network Distribution Factor)	NDF	Dimensionless	1 day

Release History

• Released in the version 4.9 of Network Data Pro

Interpretation

NDF is one way to assess Supply Dispersion. This ratio encompasses a broader economic group, perhaps equivalent to a combination of the middle and lower classes. It is calculated by assessing the aggregate supply in addresses holding more than 0.01% of a cryptoasset’s supply and dividing that figure by the total supply.

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

SER (Supply Equality Ratio)

Definition

The ratio of supply held by addresses with less than one ten-millionth of the current supply of native units to the supply held by the top one percent of addresses.

Name	MetricID	Unit	Interval
SER (Supply Equality Ratio)	SER	Dimensionless	1 day

Charts

Of the assets shown above, Bitcoin has the highest SER, followed by Ether and Litecoin. The sustained increase in Bitcoin’s SER shows that, in spite of large institutions entering the space, Bitcoin is still very much a grassroots movement.

Interpretation

Supply Equality Ratio (SER). It is analogous to the 20:20 Ratio; a traditional wealth inequality metric that compares the average income of the richest 20% of a society to the poorest 20%. Instead of income, the SER looks at supply held by different accounts within a network. It compares the poorest accounts (the sum held by all accounts with a balance less than 0.00001% of the supply) against the richest accounts (the sum held by all the top 1% addresses).

A high SER signifies high distribution of supply.

While SER provides a novel look into supply distribution that is not possible with most traditional assets, an important caveat is that a single individual can own many cryptoasset addresses. As such, an individual might hold many addresses and supply distribution does not directly map to an individual’s holdings. Also, assets custodied by large financial institutions increases SER’s denominator and puts overall downward pressure on the ratio.

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

Value in Top X% of Addrs (native units)

Definition

The sum of all native units held by the top X% addresses by balance at the end of that time interval.

Name	MetricID	Unit	Interval
Value in Top 1% of Addrs (native units)	SplyAdrTop1Pct	Native units	1 day
Value in Top 10% of Addrs (native units)	SplyAdrTop10Pct	Native units	1 day

Release History

• Release Version: NDP-EOD 4.8 (Nov, 2020)

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

Coin Metrics CoverageCoin Metrics Coverage

Value in Top 100 Addrs (native units)

Definition

The sum of all native units held by the richest 100 addresses at the end of that time interval.

Name	MetricID	Unit	Interval
Value in Top 100 Addrs (native units)	SplyAdrTop100	Native Units	1 day

Release History

• Release Version: NDP-EOD 4.8 (Nov, 2020)

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

Current Supply, Execution Layer (native units)

Definition

The sum of all native units ever created and visible on the execution layer ledger (i.e., issued) at the end of that interval. Developed for Ethereum total Supply Calculation.

Name	MetricID	Unit	Interval
Current Supply, Execution Layer (native units)	SplyCurEL	Native Units	1 day

Details

• This metric is specific to Ethereum and only available for eth.

• This supply value is one part of the input into the SplyCur calculation for Ethereum.

API Endpoints

Current Supply metrics can be accessed using these endpoints:

• timeseries/asset-metrics

and by passing in the metric ID's SplyCur in the metrics parameter.

Asset metrics

get

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:

Authorizations

Query parameters

assetsstring[]required

Comma separated list of assets. Use the /catalog-all/assets endpoint for the full list of supported assets or specify asterisk (*) in order to get metrics for all supported assets.

metricsstring[]required

Comma separated metrics to request time series data for. Information on all available metrics can be found on page https://coverage.coinmetrics.io/asset-metrics-v2. Use the /catalog-all/metrics or /catalog-all/assets endpoint for the full list of supported metrics per asset.

Example: ["AdrActCnt","BlkHgt"]

frequencystring · default: "1d"optional

Frequency of the metrics. Supported values are 1b (block by block), 1s (one second), 1m (one minute), 5m (five minutes), 10m (ten minutes), 1h (one hour), 1d (one day), 1d-ny-close (one day at New York close time). Please refer to the /catalog/metrics endpoint for the full list. Use the /catalog-all/assets endpoint for the full list of supported frequencies per asset-metric pair.

Example: 1b

statusstring · enum · default: "all"optional

Which metric values do you want to see. Applicable only for "reviewable" metrics. You can find them in the /catalog/metrics endpoint.

Available options:

start_timestringoptional

Start of the time interval. This field refers to the time field in the response. Multiple formats of ISO 8601 are supported: 2006-01-20T00:00:00Z, 2006-01-20T00:00:00.000Z, 2006-01-20T00:00:00.123456Z, 2006-01-20T00:00:00.123456789Z, 2006-01-20, 20060120. Inclusive by default. Mutually exclusive with start_height and start_hash. UTC timezone by default. Z suffix is optional and timezone parameter has a priority over it. If start_time is omitted, response will include time series from the earliest time available.

end_timestringoptional

End of the time interval. This field refers to the time field in the response. Multiple formats of ISO 8601 are supported: 2006-01-20T00:00:00Z, 2006-01-20T00:00:00.000Z, 2006-01-20T00:00:00.123456Z, 2006-01-20T00:00:00.123456789Z, 2006-01-20, 20060120. Inclusive by default. Mutually exclusive with end_height and end_hash. UTC timezone by default. Z suffix is optional and timezone parameter has a priority over it. If end_time is omitted, response will include time series up to the latest time available.

start_heightinteger · int64optional

The start height indicates the beginning block height for the set of data that are returned. Inclusive by default. Mutually exclusive with start_time and start_hash.

end_heightinteger · int64optional

The end height indicates the ending block height for the set of data that are returned. Inclusive by default. Mutually exclusive with end_time and end_hash. This parameter is disabled for Community users.

start_hashstringoptional

The start hash indicates the beginning block height for the set of data that are returned. Inclusive by default. Mutually exclusive with start_time and start_height.

end_hashstringoptional

The end hash indicates the ending block height for the set of data that are returned. Inclusive by default. Mutually exclusive with end_time and end_height.

start_inclusiveboolean · default: trueoptional

Inclusive or exclusive corresponding start_* parameters.

end_inclusiveboolean · default: trueoptional

Inclusive or exclusive corresponding end_* parameters.

min_confirmationsinteger · int32 · max: 99optional

Specifies how many blocks behind the chain tip block by block metrics (1b frequency) are based on. Default for btc is 2 and 99 for eth. For example, a min_confirmations of 0 means metrics are being calculated for the block at the tip of the chain (the latest block received by our node) whereas a min_confirmations of 6 means that metrics are being applied to the block that is 6 blocks behind the chain tip (i.e., the 7th block if the chain tip is block 1).

timezonestring · default: "UTC"optional

Timezone name for start_time and end_time timestamps. This parameter does not modify the output times, which are always UTC. Format is defined by TZ database.

Example: America/New_York

page_sizeinteger · int32 · min: 1 · max: 10000 · default: 100optional

Number of items per single page of results. The value of this parameter is ignored if the endpoint supports the format parameter and its value is set to json_stream.

paging_fromstring · enum · default: "end"optional

Where does the first page start, at the start of the interval or at the end. The value of this parameter is ignored if the endpoint supports the format parameter and its value is set to json_stream.

Available options:

sortstring · enum · default: "asset"optional

How results will be sorted. Metrics with 1b frequency are sorted by (asset, height, block_hash) tuples by default. Metrics with other frequencies are sorted by (asset, time) by default. If you want to sort 1d metrics by (time, asset) you should choose time as value for the sort parameter. Sorting by time is useful if you request metrics for a set of assets.

Available options:

limit_per_assetinteger · int32optional

How many entries per asset result should contain. For example, this combination of parameters assets=btc,eth&metrics=ReferenceRate&limit_per_asset=1 returns the latest ReferenceRate values for btc and eth.

prettyboolean · default: falseoptional

Human-readable formatting of JSON responses.

formatstring · enum · default: "json"optional

Format of the response.

Available options:

null_as_zeroboolean · default: falseoptional

Nulls are represented as zeros in the response.

next_page_tokenstringoptional

Token for receiving the results from the next page of a query. Should not be used directly. To iterate through pages just use next_page_url response field.

ignore_forbidden_errorsboolean · default: falseoptional

Ignore "forbidden" errors for the items you currently don't have access to.

ignore_unsupported_errorsboolean · default: falseoptional

Ignore "unsupported" errors for not currently supported by Coin Metrics items.

Responses

application/jsontext/csv

application/json

application/json

application/json

cURL

JavaScript

Python

HTTP

cURL

curl -L \
  --url 'https://api.coinmetrics.io/v4/timeseries/asset-metrics?assets=text&metrics=AdrActCnt'

200

400

401

403

414

200

application/json

text/csv

application/json

Example of a message with daily metrics.

Example of a message with block by block metrics.

Example of a message with 1s metrics.

Example of a message with daily metrics.

{
  "data": [
    {
      "asset": "btc",
      "time": "2020-02-29T00:00:00.000000000Z",
      "PriceUSD": "8582.09029964933",
      "SplyBMXNtv": "283220.10827406",
      "SplyBMXNtv-status": "reviewed",
      "SplyBMXNtv-status-time": "2020-03-01T09:59:13.847251000Z"
    },
    {
      "asset": "btc",
      "time": "2020-03-01T00:00:00.000000000Z",
      "PriceUSD": "8541.77389392169",
      "SplyBMXNtv": "284691.32323907",
      "SplyBMXNtv-status": "reviewed",
      "SplyBMXNtv-status-time": "2020-03-02T14:00:02.622168000Z"
    }
  ],
  "next_page_token": "0.MjAyMC0wNi0wN1QwMDowMDowMFo,MjAyMC0wNi0wN1QwMDowMDowMFo",
  "next_page_url": "https://api.coinmetrics.io/v4/timeseries/asset-metrics?api_key=<your_key>&pretty=true&assets=btc&metrics=SplyBMXNtv,PriceUSD&page_size=2&next_page_token=0.MjAyMC0wNi0wN1QwMDowMDowMFo,MjAyMC0wNi0wN1QwMDowMDowMFo"
}

Time series of metrics for an asset.

Shell

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

Python

import requests
response = requests.get('https://api.coinmetrics.io/v4/timeseries/asset-metrics?metrics=SplyCur&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="SplyCur", 
        assets="eth",
    ).to_dataframe()
)