Polymarketwhy is this issue marked resolved? it's definitely not!
why is this issue marked resolved? it's definitely not!
Zura参与话题 0消息总数 11
该用户的聊天记录定位。
聊天记录
共 11 条，显示第 1-11 条> Market maker confirms or declines within the 1-second confirmation window. more like add some lol.
> Market maker confirms or declines within the 1-second confirmation window. more like add some lol.
anyone else started getting timeouts during order placement? just started getting them
anyone else started getting timeouts during order placement? just started getting them
something seems to be wrong with bridge. I'm requesting USDC but getting PUSD from the bridge. output from llm The bridge status endpoint says the 0xE230... withdrawal was “COMPLETED” with toTokenAddress=0x3c499... native USDC, but the actual settlement tx emitted a pUSD transfer to your recipient. So the request is correct; Polymarket’s bridge is reporting native USDC while executing pUSD for that withdrawal.
something seems to be wrong with bridge. I'm requesting USDC but getting PUSD from the bridge. output from llm The bridge status endpoint says the 0xE230... withdrawal was “COMPLETED” with toTokenAddress=0x3c499... native USDC, but the actual settlement tx emitted a pUSD transfer to your recipient. So the request is correct; Polymarket’s bridge is reporting native USDC while executing pUSD for that withdrawal.
The remaining fix is not “send to this address anyway”; it needs either: 1. Polymarket fixes their bridge route for pUSD -> native Polygon USDC, or 2. We replace the bridge withdrawal with our own explicit on-chain route: pUSD unwrap/offramp -> USDC.e -> swap to native USDC -> recipient. Do I have to go the second route?...
The remaining fix is not “send to this address anyway”; it needs either: 1. Polymarket fixes their bridge route for pUSD -> native Polygon USDC, or 2. We replace the bridge withdrawal with our own explicit on-chain route: pUSD unwrap/offramp -> USDC.e -> swap to native USDC -> recipient. Do I have to go the second route?...
output from llm The bridge status endpoint says the 0xE230... withdrawal was “COMPLETED” with toTokenAddress=0x3c499... native USDC, but the actual settlement tx emitted a pUSD transfer to your recipient. So the request is correct; Polymarket’s bridge is reporting native USDC while executing pUSD for that withdrawal.
output from llm The bridge status endpoint says the 0xE230... withdrawal was “COMPLETED” with toTokenAddress=0x3c499... native USDC, but the actual settlement tx emitted a pUSD transfer to your recipient. So the request is correct; Polymarket’s bridge is reporting native USDC while executing pUSD for that withdrawal.
looks like someone else had the same problem https://discord.com/channels/710897173927297116/782024576275447848/1510251112194642020
looks like someone else had the same problem https://discord.com/channels/710897173927297116/782024576275447848/1510251112194642020
yeah probably your old account was EOA and new one requires deposit wallet flow
yeah probably your old account was EOA and new one requires deposit wallet flow
anyways.. will figure it out
anyways.. will figure it out
I'm constructing polygon transaction myself. it worked 5 days ago, I received usdc but today with the same binary/run I received PUSD instead
I'm constructing polygon transaction myself. it worked 5 days ago, I received usdc but today with the same binary/run I received PUSD instead
did you change something about the withdrawal logic? same binary/configs (after pusd and v2 change) used to withdraw usdc on the configured polygon address, but now it withdrew as PUSD instead of USDC
did you change something about the withdrawal logic? same binary/configs (after pusd and v2 change) used to withdraw usdc on the configured polygon address, but now it withdrew as PUSD instead of USDC