Wallet Balances

Wallet Balances

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

Contents

• Value in Wallets w/ Balance ≥ X% of Current Supply

• Value in Wallets w/ Balance ≥ X Native Units

• Value in Wallets w/ Balance ≥ $X USD

• Wallets w/ Balance > 0 Count

Value in Wallets w/ Bal ≥ X% of Current Supply

Definition

The sum of the supply being held by all wallets whose balance was at least X% of an asset's current supply at the end of the measurement interval. For example, if an asset's current supply is 100 tokens in total, SplyWalBal1in1B would provide the sum of the balances held by all wallets holding at least 0.0000001 units of the token. Wallets represent groups of addresses that we estimate are owned by the same entity. They provide a better proxy for user behavior since users often own more than one blockchain address.

Dictionary

Name	MetricID	Unit	Interval
Supply, in wallets with balance, greater than 1in1B	SplyWalBal1in1B	Native units	1 day
Supply, in wallets with balance, greater than 1in100M	SplyWalBal1in100M	Native units	1 day
Supply, in wallets with balance, greater than 1in10M	SplyWalBal1in10M	Native units	1 day
Supply, in wallets with balance, greater than 1in1M	SplyWalBal1in1M	Native units	1 day
Supply, in wallets with balance, greater than 1in100K	SplyWalBal1in100k	Native units	1 day
Supply, in wallets with balance, greater than 1in10K	SplyWalBal1in10k	Native units	1 day
Supply, in wallets with balance, greater than 1in1K	SplyWalBal1in1k	Native units	1 day

Availability for Assets

• SplyWalBal1in1B
• SplyWalBal1in100M
• SplyWalBal1in10M
• SplyWalBal1in1M
• SplyWalBal1in100K
• SplyWalBal1in10K
• SplyWalBal1in1K

Value in Wallets w/ Balance ≥ X Native Units

Definition

The sum of the supply being held by all wallets whose balance was at least X native units. For example, if an asset's current supply is 21M tokens in total, this metric would provide the sum of the balances held by all wallets with a balance greater or equal to X units. Wallets represent groups of addresses that we estimate are owned by the same entity. They provide a better proxy for user behavior since users often own more than one blockchain address.

Dictionary

Name	MetricID	Unit	Interval
Supply, in wallets with balance, greater than 0.001 native units	SplyWalBalNtv0.001	Native units	1 day
Supply, in wallets with balance, greater than 0.01 native units	SplyWalBalNtv0.01	Native units	1 day
Supply, in wallets with balance, greater than 0.1 native units	SplyWalBalNtv0.1	Native units	1 day
Supply, in wallets with balance, greater than 1 native units	SplyWalBalNtv1	Native units	1 day
Supply, in wallets with balance, greater than 10 native units	SplyWalBalNtv10	Native units	1 day
Supply, in wallets with balance, greater than 100 native units	SplyWalBalNtv100	Native units	1 day
Supply, in wallets with balance, greater than 1k native units	SplyWalBalNtv1k	Native units	1 day
Supply, in wallets with balance, greater than 10k native units	SplyWalBalNtv10k	Native units	1 day
Supply, in wallets with balance, greater than 100k native units	SplyWalBalNtv100k	Native units	1 day
Supply, in wallets with balance, greater than 1M native units	SplyWalBalNtv1M	Native units	1 day

Details

• Native units represent a cryptoasset's monetary unit. For example, the native unit of Bitcoin is BTC, or bitcoins_._

• In order to group addresses together, we employ a clustering methodology based on well-established industry standards.

Asset-Specific Details

• Only native units are taken into account. We do not account for token balances that may be held by the same entity. For example, this metric for ETH would not account for any ERC20 token balance that may be held by the very same address.

• 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.

Release History

• Released in version 5.1 of Network Data Pro

Availability for Assets

• SplyWalBalNtv0.001
• SplyWalBalNtv0.01
• SplyWalBalNtv0.1
• SplyWalBalNtv1
• SplyWalBalNtv10
• SplyWalBalNtv100
• SplyWalBalNtv1K
• SplyWalBalNtv10K
• SplyWalBalNtv100K
• SplyWalBalNtv1M

Value in Wallets w/ Balance ≥ $X USD

Definition

The sum of the supply being held by all wallets whose balance is equivalent to at least X dollar when priced using the Coin Metrics Reference Rate. Wallets represent groups of addresses that we estimate are owned by the same entity. They provide a better proxy for user behavior since users often own more than one blockchain address.

Dictionary

Name	MetricID	Unit	Interval
Supply, in wallets with balance, greater than $1	SplyWalBalUSD1	USD	1 day
Supply, in wallets with balance, greater than $10	SplyWalBalUSD10	USD	1 day
Supply, in wallets with balance, greater than $100	SplyWalBalUSD100	USD	1 day
Supply, in wallets with balance, greater than $1K	SplyWalBalUSD1K	USD	1 day
Supply, in wallets with balance, greater than $10K	SplyWalBalUSD10K	USD	1 day
Supply, in wallets with balance, greater than $100K	SplyWalBalUSD100K	USD	1 day
Supply, in wallets with balance, greater than $1M	SplyWalBalUSD1M	USD	1 day

Details

• In order to compute this metric, we multiply the balance of all wallets that we have identified in the blockchain by the price of the token. All wallets with a value greater or equal to the USD value of the threshold above are summed and depicted in units of USD.

• Wallets represent groups of addresses that we estimate are owned by the same entity. In order to group addresses together, we employ a clustering methodology based on well-established industry standards.

Asset-Specific Details

• Only native units are taken into account. We do not account for token balances that may be held by the same entity. For example, this metric for ETH would not account for any ERC20 USD balance that may be owned by the very same address.

• 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.

Release History

• Released in version 5.1 of Network Data Pro

Availability for Assets

• SplyWalBalUSD1
• SplyWalBalUSD10
• SplyWalBalUSD100
• SplyWalBalUSD1K
• SplyWalBalUSD10K
• SplyWalBalUSD100K
• SplyWalBalUSD1M
• SplyWalBalUSD10M

Wallets w/ Balance > 0 Count

Definition

The sum count of unique wallets with a balance greater than 0 that can be observed in the blockchain. Wallets represent groups of addresses that we estimate are owned by the same entity. They provide a better proxy for user behavior since users often own more than one blockchain address.

Dictionary

Name	MetricID	Unit	Interval
Wallets, with balance, count	WalBalCnt	Wallets	1 day

Details

• Wallets represent groups of addresses that we estimate are owned by the same entity. In order to group addresses together, we employ a clustering methodology based on well-established industry standards.

Asset-Specific Details

This metric is not available for assets that have full privacy, like Monero and Grin. For assets that have opt-in privacy features, like ZCash, it only takes the non-private activities into account.

Release History

• Released in version 5.1 of Network Data Pro

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

API Endpoints

Address Balances can be accessed using these endpoints:

• timeseries/asset-metrics

and by passing in the metric IDs SplyWalBal1in1B, etc. 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"]

frequencystringOptional

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.

Default: 1dExample: 1b

statusstring · enumOptional

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

Default: allAvailable 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_inclusivebooleanOptional

Inclusive or exclusive corresponding start_* parameters.

Default: true

end_inclusivebooleanOptional

Inclusive or exclusive corresponding end_* parameters.

Default: true

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).

timezonestringOptional

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.

Default: UTCExample: America/New_York

page_sizeinteger · int32 · min: 1 · max: 10000Optional

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.

Default: 100

paging_fromstring · enumOptional

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.

Default: endAvailable options:

sortstring · enumOptional

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.

Default: assetAvailable 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.

prettybooleanOptional

Human-readable formatting of JSON responses.

Default: false

formatstring · enumOptional

Format of the response.

Default: jsonAvailable options:

null_as_zerobooleanOptional

Nulls are represented as zeros in the response.

Default: false

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_errorsbooleanOptional

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

Default: false

ignore_unsupported_errorsbooleanOptional

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

Default: false

Responses

application/jsontext/csv

objectOptional

Time series of asset metrics.

application/json

application/json

application/json

get

HTTPcURLJavaScriptPython

GET /v4/timeseries/asset-metrics HTTP/1.1
Host: api.coinmetrics.io
Accept: */*

{
  "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"
}

Shell

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

Python

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