Contracts
Contents
Contracts Cnt with Bal > 0
Definition
The sum count of unique contracts that exist in the ledger and that hold a balance (i.e., own a non-zero amount) of native units at the end of the interval. A contract is a special address that contains and can execute code.
Contracts Cnt with Bal >0
ContBalCnt
Contracts
1 day
Details
Contracts with no balance in native units are not counted.
Asset-Specific Details
This metric is only available for ETH and ETC.
Release History
Version 4.2 of CM Network Data Pro Daily Macro (End of Day)
Availability for Assets
Contracts Cnt
Definition
The sum count of unique contracts that exist in the ledger at the end of the interval. A contract is a special address that contains and can execute code.
Contracts Cnt
ContCnt
Contracts
1 day
Details
Contracts with no balance in native units are counted.
Asset-Specific Details
This metric is only available for ETH and ETC.
Release History
Version 4.2 of CM Network Data Pro Daily Macro (End of Day)
Availability for Assets
ERC-20 Contracts Cnt
Definition
The sum count of unique ERC-20 contracts that exist on the ledger at the end of the interval. A contract is a special address that contains and can execute code. Contracts that contain all of the following are considered to be ERC-20 contracts: the balanceOf function, the transfer function, and the Transfer event hash.
ERC-20 Contracts Cnt
ContERC20Cnt
Contracts
1 day
Details
Contracts with no balance in native units are counted.
Full compliance with the ERC-20 standard is not required as only few ERC-20 tokens attain it. We therefore look for the bare minimum methods and events necessary for wallet integration of the token: balanceOf and transfer functions as well as the Transfer event. If a contract’s code has all of the following markers, it is considered to be ERC-20:
Signature of the balanceOf function: 6370a082311461
Signature of the transfer function: 63a9059cbb1461
Hash of the transfer event ddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef
Asset-Specific Details
This metric is only available for ETH and ETC.
Release History
Version 4.3 of CM Network Data Pro Daily Macro (End of Day)
Availability for Assets
Definition
The sum count of unique contracts that exist in the ledger at the end of the interval. A contract is a special address that contains and can execute code.
Contracts Cnt
ContCnt
Contracts
1 day
Details
Contracts with no balance in native units are counted.
Asset-Specific Details
This metric is only available for ETH and ETC.
Release History
Version 4.2 of CM Network Data Pro Daily Macro (End of Day)
Availability for Assets
ERC-721 Contracts Cnt
Definition
The sum count of unique contracts implementing the ERC-721 standard that exist in the ledger at the end of the interval. A contract is a special address that contains and can execute code. ERC-165 is used to determine a contract’s compliance with ERC-721.
ERC-721 Contracts Cnt
ContERC721Cnt
Contracts
1 day
Details
Contracts with no balance in native units are counted.
ERC-721 contracts are detected if they implement the ERC-165-compatible interface defined in the ERC-721 specification using the procedure specified in the ERC-165 specification.
Asset-Specific Details
This metric is only available for ETH and ETC.
Release History
Version 4.3 of CM Network Data Pro Daily Macro (End of Day)
Availability for Assets
ERC-1155 Contracts Cnt
Definition
The sum count of unique smart contracts implementing the ERC-1155 standard present in the blockchain at the end of the interval. A smart contract exists in a blockchain network as a special address that contains and can execute code. The ERC-1155 standard is an emerging standard for the issuance of both fungible and non-fungible tokens on Ethereum. As of this metric's release date, the standard has attained considerable traction in the ecosystem of Non-Fungible Tokens.
ERC-1155 Contracts Cnt
ContERC1155Cnt
Contracts
1 day
Details
This metric is calculated by monitoring the blockchain for contracts that comply with the ERC-1155 standard_,_ as defined by the EIP-1155 Standard Specification.
Like ERC-721 contracts, the activity of ERC-1155s is detected with the help of a secondary standard, ERC-165, which provides an interface for both 751 as well as 1155-compliant events.
Asset-Specific Details
As this metric is tailored to the Ethereum ecosystem, it is only available for ETH .
Release History
Released in Network Data Pro (NDP) version 5.1
Availability for Assets
API Endpoints
Contracts metrics can be accessed using these endpoints:
timeseries/asset-metrics
and by passing in the metric ID's Cont*
in the metrics
parameter.
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.
1b
Which metric values do you want to see. Applicable only for "reviewable" metrics. You can find them in the /catalog/metrics
endpoint.
all
, flash
, reviewed
, revised
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.
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. This parameter does not modify the output times, which are always UTC
. Format is defined by TZ database.
America/New_York
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
.
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
.
start
, end
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.
asset
, height
, time
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.
Format of the response.
json
, csv
Nulls are represented as zeros in the response.
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" errors for the items you currently don't have access to.
Ignore "unsupported" errors for not currently supported by Coin Metrics items.
Last updated
Was this helpful?