CoinGecko Asset Issuance Standardisation Initiative Updates and FAQ – CoinGecko

As part of our ongoing commitment to enhancing data accuracy, CoinGecko has made significant advances in asset standardization throughout Q3. Here’s a quick recap of our progress, and a look at what’s coming up.

Q3 Standardization Achievements

In Q3, we’ve successfully standardized four major assets: Wrapped BTC, Wrapped ETH, DAI and Wrapped SOL. Through the efforts, we standardized a total of 111 tokens contracts with each organized and now maintained under its distinct Coins page. This process has already enhanced user experience by providing a clearer distinction between native and non-native/ rehypothecated tokens, drastically improving data transparency and reliability.

What’s New in Q4?

Building on Q3’s achievements, we’re expanding the scope of Standardization to include four additional Coins this quarter, selected based on their significance and impact on the DeFi ecosystem:

FRAX
Wrapped AVAX
Wrapped BNB
Wrapped Staked ETH

Expected Changes & Impact

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. standardized). 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:

bridged-usdc
bridged-wbtc
bridged-weth

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

Looking Ahead

Following Q4 2024, we will maintain and enhance asset standardization. This includes refining our categorization methodology and working on improving the way we present native and non-native assets.

Need Help or Have Feedback?

We appreciate any support as we continue to enhance our data quality! If you have any questions or feedback, please don't hesitate to reach out by contacting us at https://support.coingecko.com/hc/en-us/requests/new.

FAQ

What is the purpose of the standardization effort?
The standardization effort aims to improve the data quality and consistency of assets listed on CoinGecko.com. By separating non-native token contracts from native asset pages, we ensure that each token is correctly listed and represented.
How soon and when will these changes to the API be rolled out?
The standardization for FRAX, WBNB, WAVAX and wSTETH will be fully implemented by the end of Q4 2024.
How will these changes affect my current API usage?
If you only use data related to native token contracts, no action is required on your part. However, if your API usage includes data for non-native token contracts—which will now be listed and managed separately from native tokens—you will need to update your queries accordingly.
For a comprehensive list of token contracts and API IDs that have been moved to individual pages, please reference this spreadsheet.
Will there be any API downtime during the implementation of these changes?
No downtime is expected during the implementation.
How can I stay updated on the standardization process?
You can create and customize notifications when any changes are made in the spreadsheet. For more information, refer to the instructions here.
Will there be any changes to the API endpoints?
The API IDs for the original FRAX, WBNB, WAVAX and wSTETH remain the same. Only newly created assets will have new Coin IDs to query CoinGecko API endpoint.
What should I do if I encounter any issues after the full implementation?
Please contact us at https://support.coingecko.com/hc/en-us/requests/new for assistance. We are here to ensure a smooth transition.
What is the timeline for standardizing other assets?
Currently, we are focusing on FRAX, WBNB, WAVAX and wSTETH. Standardization efforts for other assets will be announced in due time.