Closed psparacino closed 7 months ago
Describe the bug Circle recently issued native usdc: https://www.circle.com/blog/native-usdc-now-available-on-polygon-pos
vs the previous bridged version. The frontend only supports the bridged version: 0x2791bca1f2de4661ed88a30c99a7a9449aa84174 which is identified on Carbonmark as USDC.
So if a user has the new native USDC they will see a zero balance for their USDC (as the balance is actually querying USDC.e).
Carbonmark should either specify USDC.e or support both tokens for payment.
To Reproduce Steps to reproduce the behavior:
Expected behavior Either both tokens should be supported or USDC clearly labeled USDC.e with an explanation.
Screenshots Screenshot from user:
Describe the bug Circle recently issued native usdc: https://www.circle.com/blog/native-usdc-now-available-on-polygon-pos
vs the previous bridged version. The frontend only supports the bridged version: 0x2791bca1f2de4661ed88a30c99a7a9449aa84174 which is identified on Carbonmark as USDC.
So if a user has the new native USDC they will see a zero balance for their USDC (as the balance is actually querying USDC.e).
Carbonmark should either specify USDC.e or support both tokens for payment.
To Reproduce Steps to reproduce the behavior:
Expected behavior Either both tokens should be supported or USDC clearly labeled USDC.e with an explanation.
Screenshots Screenshot from user: