Trusted Volume
Last updated
Was this helpful?
Last updated
Was this helpful?
The sum of all volume from the spot markets of a set of trusted exchanges in units of U.S. dollars.
Our trusted volume metric is an aggregation of the reported volume from exchanges that we consider the most accurate and trustworthy. The full list of constituent exchanges included in our Trusted Volume can be found here
Trusted Spot Volume can be accessed using the timeseries/asset-metrics or timeseries/pair-metrics endpoints by passing volume_trusted_spot_usd_1d or volume_trusted_spot_usd_1h into the metrics parameter.
A sample of the daily trusted volumes data for Bitcoin is shown below:
btc
2020-09-21 00:00:00
44395555400
btc
2020-09-22 00:00:00
60004540100
btc
2020-09-23 00:00:00
45919134800
asset. The IDs of the asset.
time. The reference rate time in ISO 8601 date-time format.
volume_trusted_spot_usd_1d. The trusted volume value in units of U.S. dollars.
Release Version. Market Data Feed v2.2 - Jan 21, 2021 rollout (not a separate MDF version)
Fake trading volume is a persistent problem on crypto exchanges. With little regulatory oversight, it can be difficult to determine whether reported volume numbers are accurate or exaggerated. At Coin Metrics, we’ve taken a data driven approach to the problem and offer a trusted volume metric, derived from the Trusted Exchange Framework, to help identify legitimate trading volume. Our trusted volume metric is an aggregation of the reported volume from exchanges that we consider the most accurate and trustworthy. This is based on a combination of both quantitative and qualitative features. The current set of trusted volume metrics consider spot markets only and do not include futures or options markets.
Returns requested metrics for specified assets.<br/><br/> 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.<br/><br/> Supported output formats are json (default) and csv, use format query parameter to override it.<br/> To fetch the next page of results use next_page_url JSON response field or x-next-page-url CSV HTTP header if present.<br/><br/> If multiple metrics are requested in the same time the strict policy for partially available metrics among requested ones is applied: <ul>
/timeseries/asset-metrics
Comma separated list of assets.<br/> 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.<br/> Information on all available metrics can be found on page https://docs.coinmetrics.io/info/metrics.<br/> 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), 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.<br/> Use the /catalog-all/assets endpoint for the full list of supported frequencies per asset-metric pair.
1bWhich metric values do you want to see. Applicable only for "reviewable" metrics. You can find them in the /catalog/metrics endpoint.
all, flash, reviewed, revisedStart of the time interval.<br/> This field refers to the time field in the response.<br/> 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.<br/> Inclusive by default. Mutually exclusive with start_height and start_hash.<br/> UTC timezone by default. Z suffix is optional and timezone parameter has a priority over it.<br/> If start_time is omitted, response will include time series from the earliest time available.
End of the time interval.<br/> This field refers to the time field in the response.<br/> 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.<br/> Inclusive by default. Mutually exclusive with end_height and end_hash.<br/> UTC timezone by default. Z suffix is optional and timezone parameter has a priority over it.<br/> 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.<br/> 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.<br/> Inclusive by default. Mutually exclusive with end_time and end_hash.<br/> This parameter is disabled for Community users.
The start hash indicates the beginning block height for the set of data that are returned.<br/> 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.<br/> Inclusive by default. Mutually exclusive with end_time and end_height.
Inclusive or exclusive corresponding start_* parameters.
Inclusive or exclusive corresponding end_* parameters.
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).
Timezone name for start_time and end_time timestamps.<br/> This parameter does not modify the output times, which are always UTC.<br/> Format is defined by TZ database.
America/New_YorkNumber of items per single page of results.<br/> The value of this parameter is ignored if the endpoint supports the format parameter and its value is set to json_stream.
Where does the first page start, at the start of the interval or at the end.
start, endHow 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.<br/> Sorting by time is useful if you request metrics for a set of assets.
asset, height, timeHow 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.
Format of the response.
json, csvNulls are represented as zeros in the response.
Token for receiving the results from the next page of a query.<br/> Should not be used directly. To iterate through pages just use next_page_url response field.
Ignore HTTP 403 Forbidden errors
Ignore errors for unsupported assets, metrics or frequencies.
Returns metrics for specified asset pairs.<br/> Results are ordered by tuple (pair, time).<br/> To fetch the next page of results use next_page_url JSON response field.<br/>
/timeseries/pair-metrics
Comma separated list of asset pairs.<br/> Use the /catalog-all/pairs endpoint for the full list of supported asset pairs.
Comma separated metrics to request time series data for.<br/> Information on all available metrics can be found on page https://docs.coinmetrics.io/info/pair_metrics.<br/> Use the /catalog-all/pairs endpoint for the full list of supported metrics per pair.
["volume_trusted_spot_usd_1h","volume_trusted_spot_usd_1d"]Frequency of the pair metrics. Supported values are 1h, 1d.
Start of the time interval.<br/> This field refers to the time field in the response.<br/> 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.<br/> Inclusive by default.<br/> UTC timezone by default. Z suffix is optional and timezone parameter has a priority over it.<br/> If start_time is omitted, response will include time series from the earliest time available.
End of the time interval.<br/> This field refers to the time field in the response.<br/> 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.<br/> Inclusive by default.<br/> UTC timezone by default. Z suffix is optional and timezone parameter has a priority over it.<br/> If end_time is omitted, response will include time series up to the latest time available.
Inclusive or exclusive corresponding start_* parameters.
Inclusive or exclusive corresponding end_* parameters.
Timezone name for start_time and end_time timestamps.<br/> This parameter does not modify the output times, which are always UTC.<br/> Format is defined by TZ database.
America/New_YorkNumber of items per single page of results.<br/> The value of this parameter is ignored if the endpoint supports the format parameter and its value is set to json_stream.
Where does the first page start, at the start of the interval or at the end.
start, endHow results will be sorted. Metrics are sorted by (pair, time) by default. If you want to sort 1d metrics by (time, pair) you should choose time as value for the sort parameter.<br/> Sorting by time is useful if you request metrics for a set of asset pairs.
pair, timeHow many entries per pair result should contain. For example, this combination of parameters pair=btc-usd,eth-usd&metrics=volume_trusted_spot_usd_1h&limit_per_pair=1 returns the latest volume_trusted_spot_usd_1h values for btc-usd and eth-usd.
Human-readable formatting of JSON responses.
Format of the response.
json, csvToken for receiving the results from the next page of a query.<br/> Should not be used directly. To iterate through pages just use next_page_url response field.
