- Launch of CM Network Data Pro v3.0
- Launch of CM Reference Rates v1.0
- Community upgrades
CM Network Data Pro v3.0
Version 3.0 of our institutional network data feed — CM Network Data Pro — is here! Launching May 3rd, v3.0 adds the following assets to a list that already includes BCH, BTC, ETH, LTC, XMR, and ZEC for up to 66 metrics:
- BNB (pre-mainnet)
- MKR (May 6)
- XLM (May 6)
- XTZ (May 6)
CM Reference Rates v1.0
Later in the month, on May 15th, we’re launching version 1.0 of our CM Reference Rates product. Some feature highlights:
- CM Reference Rates represent a fixed USD price of one unit of a crypto asset calculated by aggregating trades across approved and vetted trading venues
- The Rates are produced for 100 of the top crypto assets at midnight UTC, with other daily closes (New York, London, Tokyo) to follow
- The Rates are used to give an unbiased and auditable USD price for calculating net asset values (NAV) for portfolio valuation and accounting purposes or backtesting trading strategies or other research
- The Rate methodology adheres to international best practices such as the IOSCO Principles for Financial Benchmarks and includes a quantitative market selection score, a robust time-weighted and volume-weighted median calculation, and automated and human quality control checks
- The Rates are available through responsive REST API in JSON and CSV format or via CSV file
Finally, we’re pleased to announce our Community upgrade project!
Most will happen under the scenes as we transition our legacy Community infrastructure to our new Pro infrastructure. This means institutional-grade reliability and uptime for all our Community data, the release of our new ontology and naming scheme, as well as clear definitions for all metrics. We’ll have more Community upgrades in the months to follow as well so stay tuned.
As far as timing, the transition will happen within the next 3 months. Importantly, we’ll be deprecating our Community API and moving all Community data to our new API. This means that we’ll no longer be supporting the existing API and would urge existing users to transition to the upgraded API.
We’ll have more details as we get closer to the transition so stay tuned!