Deposits

Exchange Deposits

Definition

The sum of assets sent to an exchange that interval.

Name

MetricID

Unit

Interval

Bitfinex Deposits (native units)

FlowInBFXNtv

Native units

1 block, 1 day

Bitfinex Deposits (USD)

FlowInBFXUSD

USD

1 block, 1 day

BitMEX Deposits (native units)

FlowInBMXNtv

Native units

1 block, 1 day

BitMEX Deposits (USD)

FlowInBMXUSD

USD

1 block, 1 day

Binance Deposits (native units)

FlowInBNBNtv

Native units

1 block, 1 day

Binance Deposits (USD)

FlowInBNBUSD

USD

1 block, 1 day

Bitstamp Deposits (native units)

FlowInBSPNtv

Native units

1 block, 1 day

Bitstamp Deposits (USD)

FlowInBSPUSD

USD

1 block, 1 day

Bittrex Deposits (native units)

FlowInBTCNtv

Native units

1 block, 1 day

Bittrex Deposit (USD)

FlowInBTXUSD

USD

1 block, 1 day

Bybit Deposit (native units)

FlowInBITNtv

Native units

1 day

Bybit Deposit (USD)

FlowInBITUSD

USD

1 day

Coinbase Deposit (native units)

FlowInCBSNtv

Native units

1 day

Coinbase Deposit (USD)

FlowInCBSUSD

USD

1 day

Crypto.com Deposit (native units)

FlowInCRONtv

Native units

1 day

Crypto.com Deposit (USD)

FlowInCROUSD

USD

1 day

Deribit Deposit (native units)

FlowInDERNtv

Native units

1 day

Deribit Deposit (USD)

FlowInDERUSD

USD

1 day

Gate.io Deposit (native units)

FlowInGIONtv

Native units

1 day

Gate.io Deposit (USD)

FlowInGIOUSD

USD

1 day

Gemini Deposits (native units)

FlowInGEMNtv

Native units

1 block, 1 day

Gemini Deposits (USD)

FlowInGEMUSD

USD

1 block, 1 day

HitBTC Deposits (native units)

FlowInHBTNtv

Native units

1 day

HitBTC Deposits (USD)

FlowInHBTUSD

USD

1 day

Huobi Deposits (native units)

FlowInHUONtv

Native units

1 block, 1 day

Huobi Deposits (USD)

FlowInHUOUSD

USD

1 block, 1 day

Korbit Deposits (native units)

FlowInKORNtv

Native units

1 day

Korbit Deposits (USD)

FlowInKORUSD

USD

1 day

Kraken Deposits (native units)

FlowInKRKNtv

Native units

1 block, 1 day

Kraken Deposits (USD)

FlowInKRKUSD

USD

1 block, 1 day

Kucoin Deposits (native units)

FlowInKCNNtv

Native units

1 day

Kucoin Deposits (USD)

FlowInKCNUSD

USD

1 day

MEXC Deposits (native units)

FlowInMXCNtv

Native units

1 day

MEXC Deposits (USD)

FlowInMXCUSD

USD

1 day

NBX Deposits (native units)

FlowInNBXNtv

Native units

1 day

NBX Deposits (USD)

FlowInNBXUSD

USD

1 day

OKX Deposits (native units)

FlowInOKXNtv

Native units

1 day

OKX Deposits (USD)

FlowInOKXUSD

USD

1 day

Poloniex Deposits (native units)

FlowInPOLNtv

Native units

1 block, 1 day

Poloniex Deposits (USD)

FlowInPOLUSD

USD

1 block, 1 day

SwissBorg Deposits (native units)

FlowInSBGNtv

Native units

1 day

SwissBorg Deposits (USD)

FlowInSBGUSD

USD

1 day

Details

Native units are considered as sent to an exchange if they are sent to an address we identify as being owned by an exchange.
USD flows are computed as FlowIn{Exchange}Ntv * PriceUSD

Chart

Asset-Specific Details

This metric might not be available for all assets. Either the exchange doesn’t support this asset, or we deemed that our coverage of the exchange was not complete enough to release the metric for it.
For Bitcoin, this metric excludes the effect of change outputs:
- If a transaction sends 90 BTC to exchange A but also withdraws 50 BTC from it, the flow is +40 BTC, not +90 BTC and -50 BTC.

Examples

During times of market stress or uncertainty, we see an uptick in BTC/funds being moved to exchanges. During the Luna collapse in spring 2021, we can see a rise in BTC being sent to both Bitfinex and Binance which is a precursor for more downside pressure as often times users are converting their funds into fiat or stable coins.

Release History

Released in the 4.0 release of NDP

Interpretation

This metric looks at the flow of funds being sent to Bitfinex and can give us a sense of market sentiment.

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

Exchange Depoosit Count

Definition

The sum count of transfers to any address belonging to an exchange in that interval. If the sender address also belongs to Binfinex, the transfer is not counted.

Name

MetricID

Unit

Interval

Bitfinex Deposit Cnt

FlowTfrInBFXCnt

Native units

1 block, 1 day

BitMEX Deposit Cnt

FlowTfrInBMXCnt

Native units

1 block, 1 day

Binance Deposit Cnt

FlowTfrInBNBCnt

Native units

1 block, 1 day

Bitstamp Deposit Cnt

FlowTfrInBSPCnt

Native units

1 block, 1 day

Bittrex Deposit Cnt

FlowTfrInBTXCnt

Native units

1 block, 1 day

Bybit Deposit Cnt

FlowTfrInBITCnt

Native units

1 day

Coinbase Deposit Cnt

FlowTfrInCBSCnt

Native units

1 day

Crypto.com Deposit Cnt

FlowTfrInCROCnt

Native units

1 day

Deribit Deposit Cnt

FlowTfrInDERCnt

Native units

1 day

Gate.io Deposit Cnt

FlowTfrInGIOCnt

Native units

1 day

Gemini Deposit Cnt

FlowTfrInGEMCnt

Native units

1 block, 1 day

HitBTC Deposit Cnt

FlowTfrInHBTCnt

Native Units

1 day

Huobi Deposit Cnt

FlowTfrInHUOCnt

Native units

1 block, 1 day

Korbit Deposit Cnt

FlowTfrInKORCnt

Native units

1 day

Kraken Deposit Cnt

FlowTfrInKRKCnt

Native units

1 block, 1 day

Kucoin Deposit Cnt

FlowTfrInKCNCnt

Native units

1 day

MEXC Deposit Cnt

FlowTfrInMXCCnt

Native units

1 day

NBX Deposit Cnt

FlowTfrInNBXCnt

Native units

1 day

OKX Deposit Cnt

FlowTfrInOKXCnt

Native units

1 day

Poloniex Deposit Cnt

FlowTfrInPOLCnt

Native units

1 block, 1 day

SwissBorg Deposit Cnt

FlowTfrInSBGCnt

Native units

1 day

Details

Coinbase (i.e., miner reward) transactions are not counted.

Asset-Specific Details

For UTXO-based protocols, this metric does not count change outputs:
- If the input addresses belong to Bitfinex, then the outputs belonging to Bitfinex are not counted as transfers to Bitfinex
For account-based protocols, if both sender and recipient belong to Bitfinex, then the transfer is not counted.

Release History

Version 4.2 of CM Network Data Pro Daily Macro (End of Day)

Availability for Assets

Coin Metrics CoverageCoin Metrics Coverage

API Endpoints

Exhange Deposits metrics can be accessed using these endpoints:

timeseries/asset-metrics

and by passing in the metric ID's FlowIn* and FlowTfrIn* 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: allPossible values:

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: endPossible values:

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: assetPossible values:

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: jsonPossible values:

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

200

Time series of metrics for an asset.

400

Asset not found.

application/json

401

Requested resource requires authorization.

application/json

403

Requested resource is not available with supplied credentials.

application/json

414

Provided URI is too long. It must not be greater than 10000 symbols.

get

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

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

import requests
response = requests.get('https://api.coinmetrics.io/v4/timeseries/asset-metrics?metrics=FlowInBFXNtv&assets=btc&pretty=true&api_key=<your_key>').json()
print(response)

from coinmetrics.api_client import CoinMetricsClient

api_key = "<API_KEY>"
client = CoinMetricsClient(api_key)

print(
    client.get_asset_metrics(
        metrics="FlowInBFXNtv", 
        assets="btc",
    ).to_dataframe()
)

PreviousExchange NextExchange Supply

Last updated 4 months ago

Was this helpful?

Contents

Exchange Deposits

Definition

Details

Chart

Asset-Specific Details

Examples

Release History

Interpretation

Availability for Assets

Exchange Depoosit Count

Definition

Details

Asset-Specific Details

Release History

Availability for Assets

API Endpoints

Asset metrics