Polymarkethow can the june be no and july yes ?!
how can the june be no and july yes ?!
Arien参与话题 1消息总数 8
该用户的聊天记录定位。
聊天记录
共 8 条，显示第 1-8 条july is still yes what happens now ?
july is still yes what happens now ?
do you have the link for july ?
do you have the link for july ?
thank you
thank you
where is the link of this ?
where is the link of this ?
?
?
URGENT: Undisputed UMA Exploit on Archived Market Market: Total Internet Blackout in Iran by...? (Group ID: 581589) July 31 Condition ID: 0x105aa178ee306e4d0a366d8b21990c36fe3ca1dee9dabdc1208c7b7f12f51031 My Polygon ID: 0x82c94C218D9C102Fbe58B92f7C7C920a6B4736fC Admins, a bad actor exploited the UMA dispute window on an archived market. The UI was restricted (archived: true), so traders couldn't see the dispute timer. The JSON confirms a logical impossibility: The UMA oracle was fed a NO resolution for the June 30 bracket (closed 01:40 UTC) and a YES resolution for the July 31 bracket (closed 01:44 UTC) on June 13. There was no real-world Cloudflare blackout trigger. This is a clear case of a malicious UMA proposal slipping through because the UI hid the market. Can we get an admin review to override the UMA resolution or issue refunds for affected traders?
URGENT: Undisputed UMA Exploit on Archived Market Market: Total Internet Blackout in Iran by...? (Group ID: 581589) July 31 Condition ID: 0x105aa178ee306e4d0a366d8b21990c36fe3ca1dee9dabdc1208c7b7f12f51031 My Polygon ID: 0x82c94C218D9C102Fbe58B92f7C7C920a6B4736fC Admins, a bad actor exploited the UMA dispute window on an archived market. The UI was restricted (archived: true), so traders couldn't see the dispute timer. The JSON confirms a logical impossibility: The UMA oracle was fed a NO resolution for the June 30 bracket (closed 01:40 UTC) and a YES resolution for the July 31 bracket (closed 01:44 UTC) on June 13. There was no real-world Cloudflare blackout trigger. This is a clear case of a malicious UMA proposal slipping through because the UI hid the market. Can we get an admin review to override the UMA resolution or issue refunds for affected traders?
Market Name: Total Internet Blackout in Iran by July 31, 2026 My Polygon ID: 0x82c94C218D9C102Fbe58B92f7C7C920a6B4736fC Hi Support Team, I am opening a request regarding a market that appears to have resolved incorrectly due to a technical glitch or an oracle/archiving error. The market "Total Internet Blackout in Iran by July 31, 2026" was newly created on June 11, 2026. Almost immediately after creation, the market was archived and abruptly resolved to YES. No such nationwide internet blackout has occurred in Iran since the market’s creation on June 11. It seems the market may have been caught in a premature oracle resolution or an administrative archive error that locked in the wrong outcome. Could a moderator or admin please look into the UMA resolution details for this specific market and check if a retroactive fix or refund is possible for affected traders? Thank you!
Market Name: Total Internet Blackout in Iran by July 31, 2026 My Polygon ID: 0x82c94C218D9C102Fbe58B92f7C7C920a6B4736fC Hi Support Team, I am opening a request regarding a market that appears to have resolved incorrectly due to a technical glitch or an oracle/archiving error. The market "Total Internet Blackout in Iran by July 31, 2026" was newly created on June 11, 2026. Almost immediately after creation, the market was archived and abruptly resolved to YES. No such nationwide internet blackout has occurred in Iran since the market’s creation on June 11. It seems the market may have been caught in a premature oracle resolution or an administrative archive error that locked in the wrong outcome. Could a moderator or admin please look into the UMA resolution details for this specific market and check if a retroactive fix or refund is possible for affected traders? Thank you!