Current Supply
Last updated
Was this helpful?
Last updated
Was this helpful?
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.
Current Supply (native units)
SplyCur
Native units
All time
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.
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
Released in the 1.0 release of NDP
The ratio of supply held by addresses with at least one ten-thousandth of the current supply of native units to the current supply.
NDF (Network Distribution Factor)
NDF
Dimensionless
1 day
Released in the version 4.9 of Network Data Pro
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.
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.
SER (Supply Equality Ratio)
SER
Dimensionless
1 day
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.
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.
The sum of all native units held by the top X% addresses by balance at the end of that time 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 Version: NDP-EOD 4.8 (Nov, 2020)
The sum of all native units held by the richest 100 addresses at the end of that time interval.
Value in Top 100 Addrs (native units)
SplyAdrTop100
Native Units
1 day
Release Version: NDP-EOD 4.8 (Nov, 2020)
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.
Current Supply, Execution Layer (native units)
SplyCurEL
Native Units
1 day
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.
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.
Supply Equality Ratio (SER). It is analogous to the ; 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).
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:
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.
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.
["AdrActCnt","BlkHgt"]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.
1dExample: 1bWhich metric values do you want to see. Applicable only for "reviewable" metrics. You can find them in the /catalog/metrics endpoint.
allAvailable options: 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 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.
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.
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.
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.
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.
Inclusive or exclusive corresponding start_* parameters.
trueInclusive or exclusive corresponding end_* parameters.
trueSpecifies 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).
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.
UTCExample: America/New_YorkNumber 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.
100Where 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.
endAvailable options: 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.
assetAvailable options: 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.
Human-readable formatting of JSON responses.
falseFormat of the response.
jsonAvailable options: Nulls are represented as zeros in the response.
falseToken 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" errors for the items you currently don't have access to.
falseIgnore "unsupported" errors for not currently supported by Coin Metrics items.
falseTime series of asset metrics.
