Supported Tokens

Our protocol is designed to accommodate any Polygon native or bridged token. However, introducing new tokens requires some attention to specific details, which we allude to below for the benefit of our users.

System Operations

Incorporating tokens into the system demands a multifaceted approach due to the reliance on price data from various Oracles. To ensure seamless availability of Oracle pricing feeds, we adhere to a rigorous process:

  1. ChainLink Oracle Compatibility: For an asset to be supported, a ChainLink Oracle must be accessible. You can consult the comprehensive list of ChainLink-supported assets on their platform.

  2. Oracle Address Integration: The integration of an Oracle address into the system is a meticulous and security-sensitive task that necessitates time.

While certain assets, particularly those accompanied by ChainLink Oracles, are meticulously verified and manually integrated into the protocol by our team, users should exercise caution. It's important to acknowledge the possibility of counterfeit or fraudulent tokens infiltrating the system.

To guard against any potential scams, we recommend employing the "Verify token address" link situated at the bottom of the screen during trades. This feature helps authenticate the contract address of the token you're trading.

Incorporating New Tokens and Oracles

If you have introduced a custom token to the system and believe it boasts Oracle price data, kindly get in touch with us. By doing so, we can ensure that our system is promptly updated to retrieve Oracle price data for the token you've added.

It's important to note that tokens lacking Oracles will inevitably lack price data, rendering certain functionalities such as the Smart Trade Dynamic Price setting unavailable for them. This underscores the significance of Oracle integration for the optimal utilization of our platform's capabilities.

Last updated