Address Balances

Address Balances

Addresses that hold a balance of X amount for a given asset.

Contents

• Address Count with ≥ X% Supply (AdrBal1inXCnt)

• Address Count with Balance ≥ X (native units) (AdrBalNtvXCnt)

• Address Count with Balance ≥ $X (AdrBalUSDXCnt)

Address Count with ≥ X% Supply

Definition

The sum count of unique addresses holding at least one in Xth of the current supply of native units as of the end of that day. Only native units are considered (e.g., an address with less than one ten-billionth ETH but with ERC-20 tokens would not be considered).

Name	MetricID	Unit	Interval
Addr Cnt with ≥ 0.00000001% Supply	AdrBal1in10BCnt	Addresses	1 day
Addr Cnt with ≥ 0.0000001% Supply	AdrBal1in1BCnt	Addresses	1 day
Addr Cnt with ≥ 0.000001% Supply	AdrBal1in100MCnt	Addresses	1 day
Addr Cnt with ≥ 0.00001% Supply	AdrBal1in10MCnt	Addresses	1 day
Addr Cnt with ≥ 0.0001% Supply	AdrBal1in1MCnt	Addresses	1 day
Addr Cnt with ≥ 0.001% Supply	AdrBal1in100KCnt	Addresses	1 day
Addr Cnt with ≥ 0.01% Supply	AdrBal1in10KCnt	Addresses	1 day
Addr Cnt with ≥ 0.1% Supply	AdrBal1in1KCnt	Addresses	1 day

Details

• These metrics are a breakdown of the addresses with balance by relative ownership of the total current supply

• In this unadjusted version, the total current supply is used.

• The state of the ledger is the one at the last available block for that day.

• Only the native units balance is considered, L2 tokens (ERC-20, etc..) are not taken into account.

• The computation uses greater than or equal comparison: owning exactly 1 billionth of the current supply qualifies an address for AdrBal1in1BCnt

Asset-Specific Details

• For XRP, escrowed amounts are not taken into account for balances but are counted towards total current supply.

• This metric is not available for assets that have full privacy, like Monero, Grin.

• For assets that have opt-in privacy features, like ZCash, it only takes the non-private balances into account. The shielded balances are taken into account for the supply component of the metric.

Examples

If the total current supply of the token is 10,000,000,000 units (10 billion units):

• Addresses with less than 1 native unit (or 0.00000001% of supply) don't appear in any of these metrics

• Addresses with a balance of 1 native unit (or 0.00000001% of supply) are counted only in AdrBal1in10BCnt

• Addresses with a balance of 10 native units (or 0.0000001% of supply) are counted in AdrBal1in10BCnt and AdrBal1in1BCnt

• Addresses with 10,000,000 native units (0.1% of supply) are counted in all of these metrics

Release History

• All but AdrBal1in10KCnt and AdrBal1in1KCnt were released in the 4.0 release of NDP

• AdrBal1in10KCnt and AdrBal1in1KCnt were released in the 4.2 release of NDP

Interpretation

In contrast with Addresses, with balance, greater than X native units, count, this metric seeks to facilitate direct comparisons between blockchains, even if they have widely varying supply counts. This metric allows you to determine how many addresses own a given fraction of supply, rather than a given number of units of supply. Keep in mind that in blockchains where transacting is cheap or free, this metric can be gamed.

Coverage

• AdrBal1in10BCnt

• AdrBal1in1BCnt

• AdrBal1in100MCnt

• AdrBal1in10MCnt

• AdrBal1in1MCnt

• AdrBal1in100KCnt

• AdrBal1in10KCnt

• AdrBal1in1KCnt

Address Count with Balance ≥ X (native units)

Definition

The sum count of unique addresses holding at least X native units as of the end of that day. Only native units are considered (e.g., an address with less than X ETH but with more than X in ERC-20 tokens would not be considered).

Name	MetricID	Unit	Interval
Addr Cnt of Bal ≥ 0.001 (native units)	AdrBalNtv0.001Cnt	Addresses	1 day
Addr Cnt of Bal ≥ 0.01 (native units)	AdrBalNtv0.01Cnt	Addresses	1 day
Addr Cnt of Bal ≥ 0.1 (native units)	AdrBalNtv0.1Cnt	Addresses	1 day
Addr Cnt of Bal ≥ 1 (native units)	AdrBalNtv1Cnt	Addresses	1 day
Addr Cnt of Bal ≥ 10 (native units)	AdrBalNtv10Cnt	Addresses	1 day
Addr Cnt of Bal ≥ 100 (native units)	AdrBalNtv100Cnt	Addresses	1 day
Addr Cnt of Bal ≥ 1K (native units)	AdrBalNtv1KCnt	Addresses	1 day
Addr Cnt of Bal ≥ 10K (native units)	AdrBalNtv10KCnt	Addresses	1 day
Addr Cnt of Bal ≥ 100K (native units)	AdrBalNtv100KCnt	Addresses	1 day
Addr Cnt of Bal ≥ 1M (native units)	AdrBalNtv1MCnt	Addresses	1 day

Details

• These metrics provide a count of addresses with balance by equal or higher than a native unit threshold.

• The state of the ledger is the one at the last available block for that day.

• Only the native units balance is considered, L2 tokens (ERC-20, etc..) are not taken into account.

• The computation uses greater than or equal comparison: owning exactly 1 native unit qualifies an address for AdrBalNtv1Cnt.

Asset-Specific Details

• For XRP, escrowed amounts are not taken into account.

• This metric is not available for assets that have full privacy, like Monero, Grin.

• For assets that have opt-in privacy features, like ZCash, it only takes the non-private activities into account.

Release History

• Released in the 4.0 release of NDP

Interpretation

• This is a potent set of metrics which can elucidate the dispersion of ownership of the address space in a cryptocurrency. The trend can demonstrate whether or not a cryptocurrency is in a concentrative or distributive phase. It should be noted that supply is arbitrary, and for large-cap assets varies between tens of millions to hundreds of billions; so unit dispersion is often not directly comparable between chains. Put otherwise: it is cheaper to accumulate addresses with 100 XRP than 100 BTC since those are so different in fiat terms. This metric can also be gamed to a degree by adding dust to many thousands of addresses.

Coverage

• AdrBalNtv0.001Cnt

• AdrBalNtv0.01Cnt

• AdrBalNtv0.1Cnt

• AdrBalNtv1Cnt

• AdrBalNtv10Cnt

• AdrBalNtv100Cnt

• AdrBalNtv1KCnt

• AdrBalNtv10KCnt

• AdrBalNtv100KCnt

• AdrBalNtv1MCnt

Address Count with Balance ≥ $X

Definition

The sum count of unique addresses holding at least X dollar's worth of native units as of the end of that day. Only native units are considered (e.g., an address with less than X dollar's worth of ETH but with more than X dollar's worth of ERC-20 tokens would not be considered).

Name	MetricID	Unit	Interval
Address Cnt of Bal ≥ $1	AdrBalUSD1Cnt	Addresses	1 day
Address Cnt of Bal ≥ $10	AdrBalUSD10Cnt	Addresses	1 day
Address Cnt of Bal ≥ $100	AdrBalUSD100Cnt	Addresses	1 day
Address Cnt of Bal ≥ $1K	AdrBalUSD1KCnt	Addresses	1 day
Address Cnt of Bal ≥ $10K	AdrBalUSD10KCnt	Addresses	1 day
Address Cnt of Bal ≥ $100K	AdrBalUSD100KCnt	Addresses	1 day
Address Cnt of Bal ≥ $1M	AdrBalUSD1MCnt	Addresses	1 day
Address Cnt of Bal ≥ $10M	AdrBalUSD10MCnt	Addresses	1 day

Details

• These metrics are a breakdown of the addresses with balance count with USD balance thresholds.

• The state of the ledger is the one at the last available block for that day.

• The price used is the daily close price.

• Only the native units balance is considered, L2 tokens (ERC-20, etc..) are not taken into account.

• The computation uses greater than or equal comparison: owning exactly $1 qualifies an address for AdrBalUSD1Cnt.

Asset-Specific Details

• For XRP, escrowed amounts are not taken into account.

• This metric is not available for assets that have full privacy, like Monero, Grin.

• For assets that have opt-in privacy features, like ZCash, it only takes the non-private activities into account.

Release History

• Released in the 4.0 release of NDP

Interpretation

• This metric standardizes wealth cohorts across multiple blockchains for easy comparison, although differences in address creation must be taken into account. Some wallets in UTXO chains tend to fragment user balances into multiple addresses to preserve privacy. Note that this metric is sensitive to changes in unit price; common address sizes combined with price changes can lead to large numbers of addresses hitting a new threshold at the same time. This can lead to sharp discontinuities in the metric. For a purer measure of holder dispersion (albeit not as directly comparable), see addresses, with balance, greater than X native units, count.

Coverage

• AdrBalUSD1Cnt

• AdrBalUSD10Cnt

• AdrBalUSD100Cnt

• AdrBalUSD1KCnt

• AdrBalUSD10KCnt

• AdrBalUSD100KCnt

• AdrBalUSD1MCnt

• AdrBalUSD10MCnt

API Endpoints

Address Balances can be accessed using these endpoints:

• timeseries/asset-metrics

and by passing in the metric IDs 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=AdrBal1in10BCnt&assets=btc&pretty=true&api_key=<your_key>"

Python

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