Panora is dedicated to empowering the Aptos community with a seamless and secure trading experience for all tokens. Our platform supports both established and emerging tokens and guarantees that every token meets our stringent verification standards. This enables you to trade with confidence and peace of mind.
- Superior Aggregation: Combining liquidity from all available sources on Aptos for optimal swap and trade experience.
- Best Rates: Utilizing advanced multi-hop and split routing algorithms to secure the best rates.
- Exceptional UI/UX: Enjoy an intuitive and user-friendly interface designed for effortless trading.
- Advanced Token Discovery: Providing a comprehensive and categorized catalog of all tradeable tokens on the Aptos chain.
Panora's Aptos Token List is the go-to categorized catalog for both legacy coins and Fungible Assets tradeable on the Aptos chain. You can use the JSON file in github to fetch the Aptos Token List
This list contains:
-
Community-Validated Tokens: Tokens with details verified by the community/partners and are visible on the Panora platform. To get included, a token must establish a strong brand presence and credibility within the Aptos ecosystem. For example, you need to be active enough to at least be a part of the private Aptos Ecosystem telegram groups. These tokens are accessible from the Token List by setting 'isInPanoraTokenList' parameter to 'true'. -
Non-Validated Tokens: Established or emerging tokens with sufficient liquidity on Aptos, even if not community-validated yet. Tokens get added or dropped from here automatically based on minimum liquidity criteria, which is subject to changes. These tokens are accessible from the Token List by setting 'isInPanoraTokenList' parameter to ‘false’. -
Banned Tokens: Tokens that are prohibited from trading on Panora and partner projects using this list, thereby ensuring user safety. These tokens are accessible from the Token List by setting 'isBanned' parameter to 'true'.
To add emerging tokens to the Aptos Token List, follow these steps:
Fork the Aptos-Tokens repository on GitHub to create your own copy.
Add the token_symbol.svg file for the token in the logos folder in your forked repository. Ensure it's no larger than 250x250 pixels and has a unique symbol not used by any existing token.
Add a SubmitTokenRequestInfo object at the end of submit-token-request.ts list.
Provide the following details:
chainId: The chain ID to which the token belongs (default is 1 for Aptos Mainnet)tokenAddress: The complete address used to identify the token as per the Aptos Coin Standard (Legacy)faAddress: The complete address used to identify the token as per the Aptos Fungible Asset (FA) Standardname: The name of the tokensymbol: The symbol registered by the token minter on-chaindecimals: The number of decimal places for the tokenlogoUrl: The URL for the token's logo (the logo should be added to the logos folder in your repository to get the correct link)websiteUrl: The official website URL of the token (optional, but preferred for faster validations)coinGeckoId: The CoinGecko ID used for fetching price feeds (optional)coinMarketCapId: The CoinMarketCap ID used for fetching price feeds (optional)
Example:
{
"chainId": 1,
"tokenAddress": "0x1::aptos_coin::AptosCoin",
"faAddress": "0xa",
"name": "Aptos Coin",
"symbol": "APT",
"decimals": 8,
"logoUrl": "https://raw.githubusercontent.com/PanoraExchange/Aptos-Tokens/main/logos/APT.svg",
"websiteUrl": "https://aptosfoundation.org",
"coinGeckoId": "aptos",
"coinMarketCapId": 21794,
}Commit your changes with a descriptive message explaining the modifications made.
Navigate to your forked repository, open a pull request, and submit it for review. Select the base repository as Aptos-Tokens and branch as main for merging your changes.
It is highly recommended to engage in discussions when new projects seek validation into the list. Tweet @PanoraExchange to notify your community and Panora about your request submission. This increases visibility and community engagement, potentially expediting approval of your PR
Reminder: Tokens are always available for trading by pasting the complete token address into our token picker, regardless of their validation status.
Aptos Token List Response object consists of the following fields:
chainId: The chain ID to which the token belongs. (Note: The default chain ID is 1 for Aptos Mainnet)tokenAddress: The complete address used to identify the token as per the Aptos Coin Standard (Legacy)faAddress: The complete address used to identify the token as per the Aptos Fungible Asset (FA) Standardname: The name of the tokensymbol: The symbol registered by the token minter on-chaindecimals: The number of decimal places for the tokenbridge: The bridge associated with the token, if any (optional)panoraSymbol: Similar to symbol, but with prefixes based on the bridge: lz for LayerZero, wh for Wormhole, and ce for Celersimilar tosymbol, except: layerzero symbols uselzprefix, wormhole symbols usewhprefix and celer symbols useceprefixlogoUrl: The URL for the token's logocategory: The token's classification (Native, Meme, or Bridged)isInPanoraTokenList: Indicates if the token is community-validated and visible for trading on the Panora platformisBanned: Indicates if the token is prohibited from tradingpanoraOrderIndex: The default sorting order for tokens within Panora SwapcoinGeckoId: The CoinGecko ID, which may be used to fetch price feeds (optional)coinMarketCapId: The CoinMarketCap ID, which may be used to fetch price feeds (optional).
Example:
{
"chainId": 1,
"tokenAddress": "0xf22bede237a07e121b56d91a491eb7bcdfd1f5907926a9e58338f964a01b17fa::asset::USDC",
"faAddress": "0x2b3be0a97a73c87ff62cbdd36837a9fb5bbd1d7f06a73b7ed62ec15c5326c1b8",
"name": "USD Coin",
"symbol": "USDC",
"decimals": 6,
"bridge": "LayerZero",
"panoraSymbol": "lzUSDC",
"logoUrl": "https://raw.githubusercontent.com/PanoraExchange/Aptos-Tokens/main/logos/USDC.svg",
"websiteUrl": null,
"category": "Bridged",
"isInPanoraTokenList": true,
"isBanned": false,
"panoraOrderIndex": 15,
"coinGeckoId": "usd-coin",
"coinMarketCapId": 3408
}