Skip to main content
Artemis maintains fundamental datasets (revenue and supply) across a broad universe of digital assets. This page describes how assets enter that coverage universe, what the assessment and onboarding process looks like, and why timelines vary by asset.

​
How assets enter coverage

Two inputs drive coverage decisions:
  1. Index universe monitoring. We run a monthly review of the index’s underlying universe, the S&P Cryptocurrency Broad Digital Asset (BDA) Index constituents, to identify assets that have newly entered and are not yet covered. Each rebalance is also reviewed in full.
  2. Client demand and industry trends. Assets that our institutional clients ask about, or that are becoming structurally significant, are added to the assessment queue even before they enter an index universe.
Onboarding begins once an asset is determined to be eligible for coverage. Timelines vary by asset, for the reasons described below.

​
What onboarding involves

Every new asset goes through the same four stages before its metrics are published:
1

Data accessibility assessment

We determine how the asset’s ledger can be read: public archive nodes, official APIs, or data feeds. For assets on blockchains Artemis already indexes, this step is fast. For new blockchains, especially those with novel architectures or restricted data access, we build ingestion infrastructure from scratch, which may be a large driver of onboarding time.
2

Methodology research

We research the asset’s tokenomics and value-accrual mechanisms: how fees are generated, what portion accrues to tokenholders (burns, buybacks, treasury accrual, distributions), and which addresses constitute protocol-owned holdings for supply purposes. Where needed, we engage directly with protocol teams and foundations to verify holdings and vesting schedules.
3

Implementation and validation

We build the data pipelines that compute the metrics, backfill history as far as the underlying data allows, and validate the output, cross-checking against independent sources and the protocol’s own disclosures before publishing.
4

Ongoing monitoring

Published metrics run under automated data-quality and freshness monitoring. Methodology improvements and data corrections can result in restatements of previously published history.

​
Coverage timing

Onboarding timelines vary with the asset’s architecture:
  • Assets on already-indexed chains (e.g. a new protocol on Ethereum or Solana) onboard fastest, since the ingestion layer already exists.
  • Assets on new blockchains require standing up new ingestion infrastructure. Chains with novel architectures or non-standard data access take the longest.
  • Assets with limited public data (e.g. private or permissioned ledgers) may require direct engagement with the operating entity before coverage is possible.
Because coverage begins when onboarding completes, the date an asset’s metrics first become available reflects this process. Where historical data is accessible, metrics are backfilled to the earliest reliable date rather than starting at the onboarding date.

​
Contact