Open jbentke opened 2 years ago
@JFrankfurt can you take a look? High priority if reproducible
Has this been resolved yet? I'm seeing the same issue on my end
Here is the proof: https://polygonscan.com/tx/0x4822979be10260a5d4b208b322b69a4873ed46b4ab81f9b0ad1cb87c7bd53909
Not sure why it took the wrapped matic + native matic + matic gas fees
Same issue here
Bug Description Connected through Metamask. Polygon Network is connected. When I select MATIC it shows the correct balance for MATIC native token. Doing a swap to USDC however sends a swap for WMATIC to USDC which can also bee seen when looking in the router. It can further be seen in the transaction data. When already approved for WMATIC its working but in my case it was not so the transaction obviously failed. Native Matic has address '0x0000000000000000000000000000000000001010' but '0d500b1d8e8ef31e21c99d1db9a6444d3adf127' is used which is the contract for wrapped MATIC (which can be selected seperatly and does work correctly).
Steps to Reproduce
Expected Behavior It should initiate a swap with native MATIC token
Additional Context Here is the transaction data where you can see that it wants to swap from '0d500b1d8e8ef31e21c99d1db9a6444d3adf127' which is WMATIC and not nativ MATIC (copied from Metamask)