Digest Polymarket & UMA Discord

POLYMARKET DIGEST — 26 MAY 2026 ⚠️ Bugs & Issues API & Trading: • Email verification 404 errors continue • BTC 5m markets showing pricing bugs and ghost fills • API connection errors since 1:39 UTC with "Connection reset by peer" • WebSocket tick size events not firing reliably • FOK orders failing specifically on BNB 5-minute markets • VPS IPs blocked from order placement, only residential IPs work Wallet Migration Problems: • New accounts require signature_type=3, old accounts use existing API • Social login + deposit wallets can't place CLOB API orders • Python SDK issues with POLY_1271 signatures ⚡ Disputes Weather Market Refunds: • May 17-19 markets still pending refunds across multiple cities • Denver May 17: User bought "No" on 72-73°F range, result was "No" but marked as loss • Taipei May 19: Two conflicting markets (28° vs 29°+), user lost ~$500 despite 31° actual temperature • Almost all May 25 temperature markets stuck in resolution Allegations: • User claims Hong Kong Observatory officials using inside information for HK weather markets, requests settlement source change 📋 Clarifications Infrastructure: • Taker delay confirmed at 250ms for crypto markets • Latency: ~300ms RTT for orders, 40ms achievable for some users • Colocation approval taking 8+ days With so many temperature markets stuck in resolution and conflicting outcomes, should Polymarket consider pausing weather market creation until the refund backlog is cleared?

UMA DIGEST — 26 MAY 2026 ⚠️ Bugs & Issues Polymarket changed their clarification address, causing clarifications to be hidden from UMA voters. Both teams are working on a solution. ⚡ Disputes A proposer referred to as "ducci" has been hit with a mass dispute wave, accumulating around 40-50 dispute losses. The user appears to be making poor proposals without proper research, including F1 disputes and falling for unreliable NBA MVP tweets. With current P&L at only +458, they're set to become the platform's biggest loser after Risk Labs. A Trump/Maduro insult market was flagged for potential dispute - 0xlykt found only evidence of Trump calling Maduro an "outlaw" at Coast Guard Academy, which may be factual descriptor rather than insult. The market has since settled. 📋 Clarifications bennidaytime confirmed that Trump posted "granddaddy" which counts for Dad/Daddy markets as compound words qualify. This prevented a potential misresolve. How much due diligence should proposers realistically do before submitting, or is losing 40+ disputes just part of the learning curve?

POLYMARKET DIGEST — 25 MAY 2026 ⚠️ Bugs & Issues kaishibazhou1 reported POLY_1271 order signer validation errors: "the order signer address has to be the address of the API KEY" despite Safe having 20 USDC.e on Polygon. update_balance_allowance() returns empty string for POLY_1271 + funder=Safe. afonso003 encountered a tennis betting display bug where a bet on Starodubsteva +1.5 sets shows as Blinkova +1.5 sets in portfolio, requesting refund. super_matmat reported all "price to beat" finance markets broken since Friday. mindless_lexie and hft_panda confirmed ghost fills are back despite previous fixes. johnleftman noted exact share price on limit order button not working again. kpiqua discovered crypto 5-minute markets stopped being created around 18:41 UTC on May 24. On-chain factory still active with 961 events in 30 minutes, but markets not indexed in gamma or CLOB. satatardy found Club Brugge resolution showing as NaN in UEFA Champions League winner market, positions can't be redeemed. Multiple users reported "maker address not allowed, please use the deposit wallet flow" errors with new accounts. servercookie9082 confirmed new 2026 email signups default to deposit-wallet (POLY_1271/sig_type=3) model, blocking all new users from programmatic trading. Clarification notices not displaying on certain browsers/devices per egging745. 📋 Clarifications Polymarket confirmed Taker Rebate Program now starts Thursday, May 28, 2026 (moved from May 29). ⚡ Disputes Weather market refunds remain severely delayed. Multiple users report 0 or minimal refunds (0.01) received despite promised 1-2 day timeline extending to weeks. user_v123 confirmed nearly all archived weather markets can be redeemed on-chain but website blocks access. suooshi threatened Twitter campaign over team's handling of the situation. Given the pervasive bugs affecting new user onboarding, crypto market creation, and basic trading functions, how many of these issues do you think stem from a single systemic problem versus separate unrelated failures?

UMA DIGEST — 25 MAY 2026 ⚡ Disputes Mass Indy 500 Dispute: 39 Indianapolis 500 markets were mass proposed and all disputed as early. im.the.wizard confirmed official box scores aren't out yet and all PDFs show "preliminary" status. Same precedent as last year's Indy 500 dispute. Disputes completed within 7 minutes - im.the.wizard took 15, flame took 17, others split the remainder. F1 Monaco GP Dispute: User rex proposed F1 markets before final classification, arguing FIA isn't mentioned in rules so no need to wait. Multiple users confirmed this is P4 - final classification required, penalties still possible. Clarification fee paid but unlikely to come due to Memorial Day weekend. Weather Disputes: Shenzhen 29°C NO proposal disputed as early by user_v123 - market can't resolve NO without hitting 30°C first. Another weather proposer (0xf25b2ae925ca17a88890df35c716c49904ce49ab) been proposing early for two days, usually 5-6 seconds too fast. Earthquake Market Dispute Threat: Market about 5.5+ earthquakes May 18-24 proposed after crossing 9 earthquakes. Some debate whether 24-hour wait rule applies since threshold already crossed days ago, but most agree no wait needed when threshold already surpassed. ⚠️ Bugs & Issues Clarification system having display issues after recent exploit/hack - clarifications not showing properly on web interface, though mobile seems to work. PM team aware and working on fix. Are proposers who resolve markets seconds too early becoming a systematic problem that needs stricter penalties, or is the current dispute system catching them well enough?

POLYMARKET DIGEST — 24 MAY 2026 🔥 News & Announcements Enhanced Games markets rules updated for clarity on three payout threshold markets ($0-2M, $2M-5M, >$5M) ⚠️ Bugs & Issues Weather market refunds crisis: Multiple users still awaiting refunds from May 18-19 weather markets. Only 25% processed for some users, with threats of public media escalation. Refunds stalled over weekend - team expected back Monday/Tuesday. Archived markets stuck: Users have funds trapped in archived Jakarta May 18 weather event. Markets resolved on-chain but team hasn't called reportPayouts() to enable redemption. Trading system issues: • Ghost fills increasing (3 reported today) • Order placement failures when tick size changes (1 to 0.1) • Websocket disconnections every 2-5 minutes, missing fill messages • Cannot split shares on multiple markets • Login issues requiring cookie clearing, Google login failing 6+ days API/Technical problems: • CLOB API returning 401 "invalid api key" errors • getOrder endpoint randomly returns null with 200 status • V1 to V2 migration "maker address not allowed" errors • Balance migration issues from old proxy wallets 📋 Clarifications Price display bug affecting Monday stock markets - "Price to beat" not showing. Market categorization error causing maker rebate issues (geopolitics vs politics). ⚡ Disputes Manila May 18 weather market resolved to 38°C without clear data backing. Lucknow dispute over IMD showing 43°C while WeatherUnderground resolved to 42°C - questions about resolution source accuracy. With refunds still stuck and data disputes plaguing weather markets, should Polymarket pause weather market creation until they can guarantee reliable resolution sources and faster payouts?

UMA DIGEST — 24 MAY 2026 ⚡ Disputes SpaceX IPO lead underwriter proposal disputed as P4 - armanh01 proposed Goldman Sachs as lead underwriter based on preliminary S-1 filing, but market rules require waiting until actual IPO date as amendments can still occur. virtual.realization disputed, noting it should resolve "Other" if IPO doesn't happen. F1 race classification proposal P4 - New proposer wynn0747 disputed for proposing before provisional results were officially posted. Multiple users confirmed P4 status despite live timing being available on site. Overwatch Champions Series Game 2 discussion - jsoeasy questioned if proposal was correct regarding draw result. stradiveri noted precedent from previous vote where similar case went P2 when not disputed second time, but exquisite_wolf_79651 confirmed P4 based on established precedent. Goldman Sachs bracket proposal unexpectedly resolved Yes at 3:13pm, causing confusion. armanh01 argued his original P4 proposal should now be valid since one bracket already resolved in negrisk contract, but im.the.wizard maintained it's still P4. Discussion about whether undisputed misresolutions affect validity of earlier P4 proposals. ⚠️ Bugs & Issues User gi9p posted dispute-related comment in wrong channel (#report-bugs instead of dispute channel). If a market resolves incorrectly but nobody disputes it, should that resolution affect the validity of earlier proposals in related markets?

POLYMARKET DIGEST — 23 MAY 2026 ⚠️ Bugs & Issues Major security exploit hit UMA CTF Adapter contract - $573.8K drained over 2 hours due to compromised private key. User funds safe (non-custodial). Official market creator address changed. Settlement bugs preventing crypto market redemptions. Email verification throwing 404 errors. Profile pages showing all users as "Anon". Order placement failures when orderbook switches to decimals. Weather markets refund crisis continues - users still waiting for refunds since May 18th despite team promises. Mixed resolution outcomes, some incorrect per actual weather data. 📋 Clarifications Trump China tariff market: ongoing negotiations don't qualify as "definitive announcements" for resolution purposes. ⚡ Disputes Iran/Xi Jinping market facing whale manipulation allegations. Jakarta weather markets discontinued due to claimed manipulation. 🔥 News & Announcements CLOB latency improvements deployed - maker latency dropped from 1000ms+ to ~40-120ms (80% improvement for some users). Taker latency still problematic at 3+ seconds. Websocket resets increased 20x post-maintenance. New KYC colocation applications backed up with 5+ day delays. Taker rebate program launched. Community volunteer user_v123 resolved additional 550+ weather markets - approximately 100-150 remaining of original 2000+. Given the weather market refund crisis, settlement bugs, and disputes over incorrect resolutions, do you think prediction markets need mandatory third-party verification before any weather-related settlement?

UMA DIGEST — 23 MAY 2026 ⚠️ Bugs & Issues UMA confirmed monitoring an unspecified situation in coordination with Polymarket team. User funds and market resolutions remain safe, with UMA contracts and systems unaffected by any exploit. ⚡ Disputes Iran Airspace Closure — Contentious dispute over whether NOTAM closure of western Iran qualifies as "major closure." pingu0018 and aenews argue YES, citing broad closure definition and 2024 precedent. teebee0931 disputes, claiming insufficient official sources and continued flights to excepted airports. alborzmirzaeii1536 notes 8 of 15 western airports remain operational. jessicaonlychild confirmed closure meets criteria based on rules and examples. Market disputed twice, reproposed as P2. Trump "3250" Mention — Dispute over whether Trump saying "3250" counts for market seeking "250" or "250th." nefffooor requests dispute citing unclear precedent. gi9p argues NO, stating "3250" is distinct numeric entity not covered by plural/possessive exceptions. armanh01 supports YES, comparing to previous "six seven" precedent. Multiple disputes filed. SpaceX Starship Markets — teebee0931 requests P4 on Super Heavy booster explosion claim, stating no evidence exists. .kaan121 questions splashdown success after explosion, but armanh01 confirms splashdown occurred before anomaly per rules. Which of these three disputes—the Iran airspace closure, Trump's "3250" comment, or the SpaceX splashdown timing—do you think has the clearest resolution criteria?

POLYMARKET DIGEST — 22 MAY 2026 ⚠️ Bugs & Issues Weather markets continue experiencing major redemption failures from May 17-19 outage. Users reporting partial refunds only, missing hundreds to thousands of dollars across multiple cities including Miami, Dallas, Istanbul, Helsinki, Warsaw, Buenos Aires. May 20 markets stuck 24+ hours with claims not enabled. Winning positions disappearing from portfolios then reappearing. API users facing different issues than UI users. 📋 Clarifications Community member abhiz69 explained redemption delays: Polymarket cannot process refunds until UMA resolves markets. Over 450 previously unproposed weather markets now resolved by UMA volunteers (primarily user "Vince" handling ~90%). Current redemption status: • May 17th markets: Most redeemable • May 18th markets: Partially available • May 19th markets: Still pending UMA settlement Toronto May 19 and Seattle May 19 have incomplete market configurations missing brackets. ⚠️ Security Alert User q835014141 scammed by impersonator pretending to be abhiz69, lost $150 after sharing Google auth codes. Real abhiz69 only helps through public Discord, never requests private details. Market Impact: New weather market liquidity down to 1/3 of pre-outage volumes due to trust issues.

UMA DIGEST — 22 MAY 2026 ⚡ Disputes Active dispute over Polymarket event about whether Candace Owens or Hunter Biden would say "cash" on Thursday. tmoneyyyy claims Candace clearly said "Cash" at 1:03:16 mark in YouTube video, providing quote: "They expected Trump to be ride or die. They expected cash." However, community members point out this appears to be dispute bait - the word was actually "Kash" referring to Kash Patel, not "cash." infinity_d and laccs confirmed the context shows she was referring to Kash Patel. laurleo noted the clip was taken out of context from discussion about Charlie Kirk assassination aftermath.

POLYMARKET DIGEST — 21 MAY 2026 🔥 News & Announcements Emergency maintenance completed at 12:10-12:25 UTC with additional fixes at 14:50 UTC. Weather markets back online but with severely impacted liquidity due to trust issues. ⚠️ Bugs & Issues CRITICAL SECURITY BREACH: Systematic wallet draining via Polymarket's own relay infrastructure. Attacker (0xd40cBF...e34b) compromised 11+ proxy wallets with victims' accounts marked "deleted" post-theft. Major System Failures: • Auto-logout bug hitting users every 30-40 minutes • Auto-redeem completely broken after maintenance • UMA oracle mapping errors preventing redemption of winning weather positions • CLOB API showing $0 balances when funds exist • Sports data/websockets not updating since maintenance • Website crashes on weather market browsing API/Builder Issues: • Builder Program quota limits not applying despite verification • Deposit wallet migration errors: "order signer address has to be address of API KEY" • Signature type confusion between old/new accounts • Taker latency spiked to 3000-5000ms in BTC markets 📋 Clarifications Weather Market Refunds: Partial processing underway with positions appearing but redemption UI broken. Team manually minting pUSD from null address as workaround. Most users receiving only 30-70% of owed amounts, with winning positions largely unredeemable. Other Resolutions: • Trump kiss market: Disputed interaction ruled qualifying, orderbook cleared • Target Q1 earnings: All resolving to "3%+" with losing share refunds • Multiple esports markets canceled due to incorrect team/date references ⚡ Disputes Multiple daily crypto markets (May 18-19) have incorrect UMA queries. Seoul May 17 and NYC May 17 temperature markets still lack clarification despite being on processed lists. How concerned should traders be about using Polymarket right now given the wallet security breach, or do you think this is just a rough patch for an otherwise solid platform?

UMA DIGEST — 21 MAY 2026 ⚠️ Bugs & Issues abhiz69 reported that weather proposal alerts contain outdated market strings, causing proposers to lose bonds when UMA bot auto-disputes incorrect proposals. Example: Hong Kong temperature market showed "20°C or below" resolution criteria in explorer but different string in actual proposal. 📋 Clarifications Weather market dispute ongoing in Shenzhen - niko2da questioned 31°C+ market showing 100% while Weather Underground data shows max 29°C. hans32312 confirmed it reached 31°C at time of message. Nantes vs Toulouse football market clarification received - enoughunknownsources provided evidence that disciplinary committee will likely uphold 0-0 score when match was stopped rather than awarding 3-0 default victory. ⚡ Disputes Active dispute over live broadcast market - zen_hare_26737 argued P2 YES position citing CNN's JSON-LD metadata identifying page as "LiveBlogPosting" with real-time updates during summit, claiming this proves live coverage occurred. Technical claiming issues resolved - looppah unable to claim redeemable position due to frontend bug, abhiz69 provided contract-level fix to enable manual claiming. Multiple users still awaiting weather market refunds, with abhiz69 noting bottom 4 positions already processed. Could the weather proposal string bug be costing the protocol more in disputed bonds than it would to implement automated proposal validation checks?

@atteonthephone @mustafap0ly @williamlegate 20 minutes ago they restored my positions fo 17-19 May. But cannot redeem none of them

It's now day 3 since "decentralized" crypto exchange Polymarket pressed a magic button that made our money disappear. @mustafap0ly and @williamlegate keep repeating that refunds are coming without specifying which positions will be paid, despite multiple people asking for days.

So true

@submittime I don't receive anything yet. Still have 0% refund

@predictdigest 只收到10%的退款。对PM团队的效率和沟通方式表示不理解。 他们没有把客户放心上，对待我们的方式就像对待雇工。

POLYMARKET DIGEST — 20 MAY 2026 🔥 News & Announcements Weather Markets Crisis Update: Polymarket processed refunds for ~2k archived weather markets (May 17-19) but implementation severely flawed. Users receiving only 2-10% of expected refunds, with some getting nothing despite affected positions. Several major markets missing from refund list including Seattle, Los Angeles, Toronto, and NYC May 17 temperature markets. Database Migration: Scheduled maintenance May 20, 12:10 UTC with 10-15min trading downtime. Post-only mode for ~2min after restart. ⚠️ Bugs & Issues Critical Resolution Errors: • Frontend incorrectly mapped markets on-chain causing wrong resolutions for ~2k markets • London temperature market resolved at 15°C despite actual high of 16°C • BTC 5min markets showing timing discrepancies with Chainlink feeds System Failures: • Sponsored rewards not displaying on rewards page • Auto-redeem broken for winning positions over $1 • Sports markets disappeared (NBA, cricket) • CLOB API showing false "UNDERMAINTENANCE" status • Connection issues and cancelled orders across browsers • Post-migration wallet balance display problems 📋 Clarifications Gaza Flotilla Market: Vessels must enter Israel's territorial waters as part of flotilla - interdicted vessels don't count. Strait of Hormuz: Deadline extended due to data integrity issues with IMF Portwatch. Jakarta Weather Markets: Officially discontinued due to manipulation concerns, but Lagos mysteriously removed while Jakarta remains active. ⚡ Disputes May 20 Refund Demand: User eeehhh demanding refunds for May 20 positions, arguing unfair market restart after 24+ hour lockup period created disadvantage for existing position holders. Communication Breakdown: Users filing CFTC complaints over poor communication, inconsistent support responses, and lack of official website announcements during crisis. With refunds only returning 2-10% of expected amounts and critical markets still missing from the payout list, should Polymarket halt all weather market activity until they can guarantee accurate resolution and fair compensation?

POLYMARKET DIGEST — 19 MAY 2026 🔥 News & Announcements Weather Markets Mass Archival: Polymarket archived all temperature markets (50+ cities globally) due to Oracle configuration errors with Weather Underground data source. Markets disappeared from UI with positions vanishing. Refunds promised within 7-10 business days, with markets expected to return around May 20-21. User Bans: Admin banned users for phishing/malware distribution and bot selling activities. Geographic Restrictions: Philippines users confirmed geoblocked from platform access. ⚠️ Bugs & Issues API & Trading Issues: - Multiple users experiencing "invalid signature" and "maker address not allowed" errors with CLOB API - Authorization balance prompts persisting for 2+ weeks despite SDK upgrades - HTTP 500 errors from Gamma API - 504 gateway timeouts on /order endpoint - "Not enough balance" errors affecting multiple users - Silent fills and trading inconsistencies reported Platform Performance: - Latency improvements noted (down to 300-500ms) but later degraded to 1500ms+ - Search functionality broken - Mobile UI glitches - Missing trade history for 8-hour overnight period Other Technical Issues: - KYC verification delays with no responses - Deposit wallet signature problems for post-May 9 accounts - Portfolio balances displaying incorrectly - Limit orders cancelled without user action 📋 Clarifications Weather Market Resolution: Oracle failed due to missing Weather Underground data, causing markets to resolve to minimum temperature brackets incorrectly. Losing positions will receive refunds, winning positions will be paid out according to actual weather data. API Limitations: Maximum 3000 trades per API call, use multiple calls with offsets for larger datasets. Refund Timeline: Despite initial 10-day estimate, staff indicated faster processing without specific methodology details. Given all these technical issues and the weather market fiasco, do you think Polymarket needs to pause new market launches until they stabilize their core infrastructure?

UMA DIGEST — 19 MAY 2026 ⚡ Disputes Active dispute on Iran market "What will Trump say during bilateral events with Xi Jinping?" with major whale manipulation allegations. gyhwh argues the market should resolve YES, claiming opposing side only proves footage existed beforehand but not that it wasn't part of live broadcast. rubenfix__03819 accuses whale poorsob of holding 1M+ short position and using bot network to force Invalid bailout, citing Kalshi precedent that settled same market as YES. youaretalkingtogod confirmed he is poorsob with 1,012,945 short position, claiming "clarification is final" and threatening to add another $5M. Multiple markets disputed including Nuclear and other bilateral event markets. 📋 Clarifications Exact Score football markets refund confirmed: abhiz69 clarified that shares bought before 2026-05-15 05:25 PM ET for markets 2152873 (Aston Villa FC 4-2) and 2205094 (Any Other Score) will be refunded. looppah had issues claiming winning shares on 4-2 market despite auto-redeem being enabled. Nantes vs Toulouse match placed under formal LFP investigation with ruling scheduled for May 27, 2026 - all match brackets will wait for official governing body decision. ⚠️ Bugs & Issues User looppah unable to claim winning shares on Aston Villa 4-2 market despite auto-redeem enabled and market settling correctly before archiving. Position and money disappeared from portfolio. Suspicious re-proposal activity detected - say105 reports request and propose transactions occurred simultaneously, suggesting potential automated or insider involvement rather than normal community sniping. Do you think the whale's $5M threat to add shorts is a real conviction play or just intimidation tactics to force an Invalid resolution?

POLYMARKET DIGEST — 18 MAY 2026 ⚠️ Bugs & Issues Major weather market oracle failure caused wrong temperature brackets to be resolved across multiple cities (Miami, Mexico City, Seoul, Hong Kong). Mass archiving of weather markets led to positions disappearing from portfolios. Root cause identified as changes to oracle price request batching system causing mixed-up indexes. User reports exploiting merge/split error to redeem $98K from $1.8M phantom position. Migration bugs continue with users losing funds during v2 transition - deposits vanishing and accounts being reset. Severe platform performance issues: CLOB latency hitting 2000ms+, suspected DDoS attacks. API rate limiting causing 700+ errors per 5 minutes for bot operators. Authentication problems with frequent logouts. 📋 Clarifications Polymarket confirmed weather market refunds will be issued within 10 business days, stating positions are "safe." New May 20 weather markets opened but were immediately archived again. LRS 2026 Split 1 gaming market rules updated. Different taker delays observed across markets: 1 second for LoL, 3 seconds for CS2. With oracle bugs causing mass archiving and phantom position exploits, should Polymarket temporarily pause high-value markets until the indexing system is fully audited?

UMA DIGEST — 18 MAY 2026 ⚠️ Bugs & Issues user_v123 identified critical issues with weather and crypto markets - some Polymarket markets aren't resolving properly despite proposals settling. Markets initialized through different UmaCtfAdapter addresses aren't getting resolve links. pumpedlunch confirmed there were issues with the new market initialization process. All weather markets have been archived/hidden until technical issues are resolved. ⚡ Disputes Russia-Ukraine Ceasefire Markets: poncho3142 filed formal complaint about inconsistent rule application between two related ceasefire markets. 13 affected users are coordinating, requesting share transfers between markets rather than cash payouts. Claims rules were applied inconsistently and duplicate market creation caused trader confusion. Peru Election Dispute: Heated debate over Aliaga elimination proposal. greedisgood6091 argues JNE (final judicial authority) results make second round official, while im.the.wizard contends market was already unambiguous after ONPE results and credible reporting on Friday. Dispute centers on whether JNE confirmation changes the proposability of previously disputed candidates. Ligue 1 Match Abandoned: Nantes vs Toulouse match abandoned due to fan pitch invasion after Nantes relegation confirmed. Discussion about whether to resolve as 3-0 forfeit (standard) or maintain score at time of abandonment. FFF will make final ruling. NBA MVP Announcement: Early proposal disputed when announcement timing was unclear - official announcement came later at 7:30pm, costing proposer significant bond loss. 📋 Clarifications Ligue 1 season ongoing - goals/assists leader proposals may be premature. Soccer verification moving to manual website checks, ending automation. Should markets resolve based on the official governing body's final decision, or does credible reporting beforehand make that decision inevitable?