Add Native USDC as option for intermediate token in multihop swap transaction on Polygon
complete
R
Rok Šerak
We recently launched a new token FLTK on Polygon and also created liquidity pool for it on Quickswap Exchange.
We used Native USDC as the second token in the LP pair.
This is the link to created LP on Quickswap.
And for the interaction with the LP we wanted to use your Swap API service, which is working well for the swap between Native USDC and FLTK, but is unable to find a swap route for any other tokens to be swapped with FLTK.
But if I try to do the same swap via Quickswap UI it is able to find a valid route and swap can be done.
For example:
Swap from MATIC to FLTK, Quickswap UI found a route
WMATIC -> USDT -> USDC -> FLTK
or for USDT to FLTK it found
USDT -> USDC -> FLTK
Now what I would appreciate if you guys check on your end is if you support Native USDC as an option for an intermediate token in the swap route.
I looked at the source code of your API in Github, which I know is deprecated but still I would assume at least part of it is still being used.
In that source code you have defined in the constants a list of tokens that can be used as an intermediate token in a swap route, constant
POLYGON_TOKENS
.Here I noticed you do have specified
USDC
token as an option but that is the Bridged USDC, not the Native USDC that Circle released a couple of months ago. And this native one is also the one we are using.Bridged USDC
Native USDC
My request would be if you guys can also add the Native USDC to that list, so it can also be used as an intermediate token in swap routes. This would help us enable more swap pairs with our token FLTK, without the need to add extra liquidity for all other tokens on your list of intermediate tokens.
Teju Adeyinka
complete
Hi Rok Šerak,
We've added USDC as an intermediate token to the new version of our API. You can try it out in beta here: https://0x.org/docs/next/category/upgrading