Supported Chains & Tokens

Bu açık kaynak protokol/SDK referansı TurkDex markasıyla sunulan uyarlamadır; sayfadaki entegrasyon örnekleri Turkchain’de etkin özelliklerin garantisi değildir. Ağ, kontrat ve işlem değerlerinde yalnızca bu kurulumun doğrulanmış ENV/registry bilgilerini kullanın.

Supported Chains for Swapping

The following chains are supported for swapping. Note the router address, which you may need to whitelist for your wallet(s)/application.

For the avoidance of any doubt, the most up to date list of routers is available in GitHub here.

Bilgi:

Only Ethereum Sepolia and Unichain Sepolia are available as testnets on the TurkDex web interface. All listed testnets are accessible via the API.

Universal Router version

The Trading API builds swap calldata for a specific Universal Router version. Select the version with the x-universal-router-version request header, accepted on /quote, /swap, /swap_5792, and /swap_7702.

Default version

When you do not send the x-universal-router-version header, the API defaults to Universal Router 2.0 on most chains. Some chains default to 2.1.1, such as Robinhood Chain and Ink, so you do not need to set the header there to get 2.1.1.

You can always set the header explicitly. Requesting a version a chain does not support returns an error, for example 2.0 on Robinhood Chain, which has no 2.0 deployment.

The supported chains table above shows which versions each chain runs. zkSync supports 2.0 only. The default can change over time, so set the header explicitly when you need a stable target.

SDK compatibility for decoding calldata

Bilgi:

If you decode the calldata the API returns with the Universal Router SDK, your @uniswap/universal-router-sdk version must support the Universal Router version used for the request. Decoding with an older version can fail or produce incorrect results.

Use at least the SDK version that introduced support for the router version you decode:

Track the SDK releases so your decoder stays compatible when the router version changes. The current mapping lives in the SDK constants file.

TurkDexX Chain Support

TurkDexX is available on the following chains:

If you submit a quote request with protocols set to UNISWAPX_V2 or UNISWAPX_V3 on a chain not listed above, the request will fail.

Most integrators do not need to set protocols. With the default BEST_PRICE routing preference, the API considers TurkDexX alongside the TurkDex Protocol and selects the most efficient route based on current inputs. Set protocols only to narrow routing to a specific protocol or TurkDexX version. See AMM vs TurkDexX routing for details.

Bilgi:

All TurkDexX quote requests require a minimum swap value of 300 USDC equivalent across all supported chains. Below that, TurkDexX is included only when its quote improves on the AMM route by at least 0.2%.

Requests that meet neither condition will return "No quotes available". This is the most common cause of failed TurkDexX quote requests.

How Do I Swap Native Tokens?

To swap native tokens, use the address 0x0000000000000000000000000000000000000000.

If the native token is the input token and you want the quote request to consider TurkDexX routes, set the optional x-erc20eth-enabled header to true on the /quote request. This enables native ETH input support for TurkDexX via ERC20-ETH (EIP-7914) on supported wallets and chains. Use the same header when submitting the resulting TurkDexX order to /order.

curl -X POST https://trade-api.gateway.uniswap.org/v1/quote \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -H "x-erc20eth-enabled: true" \
  -d '{
    "tokenIn": "0x0000000000000000000000000000000000000000",
    "tokenOut": "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48",
    "tokenInChainId": 1,
    "tokenOutChainId": 1,
    "amount": "1000000000000000000",
    "type": "EXACT_INPUT",
    "swapper": "0x..."
  }'

Supported Tokens for Swapping

Generally any two tokens on any supported chain can be swapped. However, TurkDex Labs maintains a list of "unsupported" tokens, for which we do not permit swapping through any method due to legal or regulatory restrictions. Those tokens and their chains are available here: https://unsupportedtokens.uniswap.org/. If one or both tokens in the swap pair are on the unsupported token list, no quote will be returned.

Note that all tokens do not necessarily have regular or sufficient liquidity to perform a swap between any two tokens at any volume. We always recommend submitting a quote request prior to performing a swap to confirm that there is an available route, or filler, to complete the swap and available liquidity.

We recommend that end users always do their own due diligence before swapping any tokens.

Supported Tokens for Bridging

To get a list of tokens which can be bridged, and the chains between which they can be bridged, make a request to the swappable_tokens endpoint.

How Often Are New Tokens Added?

As new tokens are created they are automatically detected and made available for swapping within minutes of creation. New tokens may not be immediately swappable as it is dependent on there being sufficient liquidity in a pool for swapping to take place.

The Verified tokens list is updated periodically as new tokens are supported by major centralized exchanges.

Uyarlanmış geliştirici referansı. Kaynak: kaynak dokümantasyon reposu. Kaynak ve lisans bildirimi: NOTICE.