CoinGecko Asset Naming Methodology
Last updated: October 2, 2026
At CoinGecko, we are committed to providing users with accurate and user-friendly information on various crypto Assets. A key part of this effort is ensuring that the asset names listed on the platform are distinctive and unique. Given how diverse crypto assets can be, along with numerous variations of an existing token, we have designed and will be implementing a standardized naming convention. This article outlines the methodology that we employ and provides a clear framework for naming different asset types.
Issues with Non-Standardized Use of Names
In the cryptocurrency space, multiple variations of the same token based on common themes or entities exist. Think native and bridged USDC tokens, for example. Due to the nature of decentralization and transparency of each project, almost anyone can fork/ replicate the token’s codebase to recreate another similar token, catering to different blockchains and use cases in different areas.
The lack of standardization carries the risk of:
- Data Inaccuracies: The data (ie, price) for the underlying token may become inaccurate in the events of de-pegs, hacks and exploits. For more information, visit this KB article.
- Confusion: Users might struggle to identify the version or variation of a token they are looking for. This potentially leads to issues such as mistakes in trading the wrong token or token variant.
- Hidden Risks: Users not well-informed may be exposed to risks that may not be immediately apparent. For example, some users may bear the impression that owning a non-native USDC is as safe as owning native USDC backed by its official issuer - Circle, which can be a fatal misconception since non-native USDC is vulnerable to exploits. The Multichain’s bridge exploit incident is a good example of this.
Our Approach
To address the issues, CoinGecko has established a naming convention based on the following principles:
- User-friendly: Asset names should be easy for users to understand and recognise at one glance.
- Uniqueness: Each project should have a distinct and easily identifiable name.
CoinGecko Asset Naming Convention
Please adhere to the following naming formats depending on the Asset type:
| Asset Type | Naming Style | Examples |
Native Stablecoins |
Suggested:
|
|
| Remark: Please include the protocol or issuer of the token, followed by the token ticker symbol. You may refer to this KB for detailed steps. | ||
Wrapped Assets |
Native:
Issued by 3rd party:
|
Native:
Issued by 3rd party:
|
|
Remark: If the token is not natively deployed by the project that issued the underlying token, kindly include the issuer as part of the naming style. For Bridged and Wrapped Assets, the Issuer is defined as the entity that has ownership over the bridged token contract, unlike other Asset Classes that define the Issuer as the entity that deployed the token contract. This is because Bridged/ Wrapped tokens can also be deployed by third parties despite representing/ being backed by a common cryptocurrency (ie USDT by Tether). If the Wrapped Asset is bridged, it should be classified as a Bridged Asset instead. For example, the following is a bridged asset. |
||
Bridged Assets |
Singular Instance:
Multichain but issued by a single entity:
|
|
|
Remark: If the Bridged token is not natively deployed by the official party, kindly indicate the protocol/ issuer of the token, usually the bridge for this type of token. If the text ‘Bridge’ is part of the name the issuer refer themselves as ie Arbitrum Bridge, remove it and adhere to the following styling: Correct: Arbitrum Bridged USDC (Arbitrum) Incorrect: Arbitrum Bridge Bridged USDC (Arbitrum) |
||
Merged Assets |
IssuerName_'Merged'_NativeTokenTicker_(Network) |
|
| Remark: Nova Merged Assets are tokens mirroring underlying tokens issued by Nova on zkLink. For more information, kindly refer to their documentation. | ||
RWA Tokenized Assets - Sovereign Bonds / Money Market Funds |
IssuerName_TokenName_AssetType |
|
| Remark: IssuerName is mandatory. | ||
RWA - Tokenized Equities / Pre-IPO Assets |
TokenName_IssuerName_AssetType (if applicable) |
|
|
Remark: IssuerName is mandatory. Real-world assets/ commodities that have been tokenized onchain. |
||
Synthetic Assets, Asset-backed tokens, Options |
IssuerName_NativeTokenTicker_(Network) |
|
| Remark: - | ||
Staked Assets / LSTs/ LSDs |
Staked (Issued by Original Project/ Native):
Staked (Issued by 3rd Party / Restaked):
Staked (Duplicate Variant):
|
Native:
Issued by 3rd party:
Duplicate:
|
| Remark: Tokens minted from users staking or re-staking underlying tokens. | ||
Escrowed Assets |
Native:
Issued by 3rd party:
|
Native:
Issued by 3rd party:
|
| Remark: Tokens held in escrow but minted for specific use cases in DeFi. | ||
Lending/ Borrowing Vault Receipt Tokens/ Yield- Bearing Cryptoasset |
Issuer Name_Base Asset Ticker_([Network (Optional)]) |
|
|
Remark: These are tokens representing positions in lending/ borrowing vaults on DeFi protocols. They usually consist of collateral deposited by users and are managed (curated) according to the protocol's terms. NOTE: For the vault-name, refer to the protocol's UI for identification. |
||
Note: This comprehensive list is non-exhaustive and will accommodate future changes whenever needed.
By adhering to the guidelines, we aim to create a standardized and user-friendly experience for all CoinGecko users. We highly appreciate your cooperation and support in assisting us to maintain the integrity and clarity of our platform.
FAQs
- Do memecoins have a naming convention to follow?
The Asset Naming Convention does not apply to memecoins and any other asset types not explicitly stated in the list above at the moment.
- My Coin does not fall into any of the categories above. What should I do?
Please submit a support ticket on the top right corner of this page for assistance.
- My Coin Listing request was rejected. Could it be due to the incorrect use of a convention?
No. There are numerous reasons for a rejection and it is unlikely to be solely due to the incorrect use of naming convention. Kindly refer to this article for more details.