Changelog
🤝 Get HelpFeedbackPricingEnterpriseDeveloper Dashboard
Back to All
added

CoinGecko Asset Issuance Standardisation Initiative Updates

July 26th, 2024

As part of our commitment to improving data quality and enhancing the consistency of asset information, we are rolling out an asset standardization initiative at CoinGecko.

What is asset standardization?
Standardization involves refining how we classify and display assets. By systematically organizing asset listings into more precise categories - such as native, bridged, or wrapped tokens each following specific naming conventions, we aim to eliminate confusion and enhance data reliability.

What changes should I expect?
The most notable change is that non-native token contracts previously grouped under native asset listings will now be assigned their own distinct pages.

For example, a bridged version of USDT that might have been aggregated under the original, native USDT page, will now be featured on a dedicated page specifically for that bridged variant.

Additionally, there may be varying levels of changes in various aggregated data points of the standardized assets, including trading volume, supply, market cap rankings, etc., due to misplaced contracts being transitioned away from the original page to accurately reflect their true metrics.

Focus for Q3 2024
Our efforts this quarter will concentrate on three major assets:

**For full list of FAQs and updated infomation, please refer here


Tips and FAQs for API users

1. How does this affect my current API setup?

The following CoinGecko API endpoints will be impacted, with full details tracked in this spreadsheet. We encourage you to make the necessary adjustments and enable edit notifications on the Google Sheets, to receive real-time updates when non-native token contracts have been successfully standardized.

Simple

  • /simple/price
  • /simple/token_price/{id}

Coins

  • /coins/markets
  • /coins/{id}
  • /coins/{id}/tickers
  • /coins/{id}/history
  • /coins/{id}/market_chart
  • /coins/{id}/market_chart/range
  • /coins/{id}/ohlc
  • /coins/{id}/ohlc/range
  • /coins/{id}/circulating_supply_chart
  • /coins/{id}/circulating_supply_chart/range
  • /coins/{id}/total_supply_chart
  • /coins/{id}/total_supply_chart/range

Contract

  • /coins/{id}/contract/{contract_address}
  • /coins/{id}/contract/{contract_address}/market_chart
  • /coins/{id}/contract/{contract_address}/market_chart/range

Exchange

  • /exchanges/{id}/tickers
  • /exchanges/{id}/volume_chart
  • /exchanges/{id}/volume_chart/range

2. Do I have to make changes to my API?

No changes are necessary if you do not need data for non-native token contracts that will be separated away from the native tokens.


3. What will happen to the coins that are separated into a new coin page?

Historical data for new non-native or bridged assets will only be available from the date of asset page creation (i.e. stnadardized). To access historical data prior to the asset standardization, we recommend retrieving data from the original native assets.


4. How do I identify the list of coins that will be separated?

For a finalised list of token contracts and API IDs that have been separated from its native asset page and listed individually, please refer to this Google Sheets

You may also identify the list of bridged coins via API: you may also use /categories/list endpoint to look for bridged categories such as:

  1. bridged-usdc
  2. bridged-wbtc
  3. bridged-weth

Then you may use /coins/market endpoint to retrieve the list of coins