Digest Polymarket & UMA Discord @predictdigest

POLYMARKET DIGEST — 25 JUNE 2026 🔥 News & Announcements Taker rebate level-up bonuses will be paid starting Monday June 29th — only for new levels reached from that date onward. Whether already-reached levels get retroactive payment remains unclear. Multiple users (szinkler, ramonegc, satatardy) still waiting on unpaid bonuses. ⚠️ Bugs & Issues Major CLOB outage (June 24) — the worst incident of the batch. Following a maintenance update, the CLOB suffered widespread HTTP 500/425/504 errors, failed/lost order placements, cancel timeouts, and Cloudflare throttling below documented rate limits. p90 maker latency hit ~1s+. Multiple MMs stopped quoting; reported losses range from $5K–$6K per individual, with one estimate of ~$100K total. 0xdanzu acknowledged at 20:39 UTC; pmkeaton posted "We're investigating" at 20:42 UTC. Status page showed "all systems operational" throughout — widely criticized. alfa4663 confirms ~$2K loss from bot errors and has suspended trading. Other active bugs: • Gasless merge 500 error (since ~June 23 19:25 UTC) — POST /submit returns HTTP 500 on all merge_positions calls via gasless relayer; mint/split unaffected; SDK-independent • Combo markets broken broadly, separate from the merge issue • Gamma API 429s — previously working requests now rate-limited intermittently; alfa4663: "everything changed today" • New tick size 0.0025 discovered on "Gavin McKenna" market (undocumented) — causes Unknown tick size validation errors in CLOB orders • Login issues — users getting logged out, security errors, cancelled request on login • Unauthorized AGELITE position (~$466, -$227 loss) opened with no corresponding buy tx — user directed to Polymarket US support • Partial fill / phantom cancel — GTC order of 1000 shares matched only 700, remainder cancelled without user action • Win showing as loss display bug (hhumps_) — ongoing • World cup market decimal display bug (stupidm0ney0723) • Losses on open orders during CLOB restarts — long-standing bug, repeatedly promised fixed, never resolved per verylowsharpe Critical: Taker fee calculation bug (reported by satatardy, filed on Cantina, acknowledged but disputed then ignored by Polymarket): Taker fees calculated on average price across levels; maker rebates calculated per level — inconsistent formulas. Consequences: fees often exceed documented amounts, same trade can incur different fees depending on order structure, and buying shares in a winning outcome can cause a net loss. Confirmed onchain. Bugs consistently favor Polymarket. Traders can partially mitigate by structuring orders differently. Climate markets archived mid-trading — Singapore, Wuhan, Sao Paulo, Buenos Aires weather markets archived with some brackets never tradable (0 volume) but resolved anyway. Mod kurwamach. confirmed archived markets normally get refunded and a fix is in progress; Sao Paulo and Buenos Aires June 22 markets still archived. 📋 Clarifications • SC2 Lambo vs SHIN (5 markets): Match rescheduled June 9 → June 16 — within the 7-day window, so 50-50 delay clause does not apply. Match played; resolves on actual result. • "Will Trump speak to [X] in June?" (20 markets): Rule language updated for clarity across the series. • Collocation KYC contact: [email protected] (not builders@) • Polymarket US API (polymarket.us) runs a separate CLOB on AWS NYC; non-US users cannot obtain an API key • WebSocket practical limit: ~500 assets/socket; disconnects above ~10K • WS docs typo: matchtime → match_time (fixed) • "Queue exploit" reportedly fixed (June 24 17:04 UTC) With the taker fee calculation bug consistently favoring the platform over traders, how much longer do you think Polymarket can maintain credibility without a transparent, independent audit of their fee structures?

POLYMARKET DIGEST — 24 JUNE 2026 🔥 News & Announcements Chainlink charges (originally July 1) pushed to September. Quebec (QC), Canada officially added to restricted geographies June 22 — confirmed intentional by staff. Docs not yet updated (still show QC as allowed). Side effect: froze multiple trading bots. Planned maintenance June 24 04:00–05:00 UTC (queue exploit fix) — "NOT ready" errors during window were intentional. ⚠️ Bugs & Issues Rewards chaos: June 20 LP rewards still missing; June 22 maker rebates paid ~14:56 UTC June 23; June 21 rewards reportedly paid twice. Taker rebates backpayment ran from June 1, not May 28 — affected users should DM staff. Referral rewards show as sent but not received. API: GET /events hard-fails at offset ≥ 2100 (keyset next_cursor also broken). Rate limits tightened without announcement — 403/429 errors widespread. HTTP 425 on order placement returns no order_id. Cancel API returns success but order still fills (confirmed race condition). Minimum observed latency ~295ms even when colocated in same AWS zone as CLOB. WS orderbook silently muting; 1–2s latency spikes p99. UI: Limit sell orders invisible after placement, cannot be cancelled, blocks new orders — reported as potentially causing major losses. Won trades displaying as losses with wrong amounts (multi-day). PnL display unreliable; one user saw +$2.5K swing overnight with no explanation. "Removed rewards" filter shows no orders despite active limit orders. Combo button missing on sports page — ENG aware. Live markets: Portugal vs Uzbekistan — CLOB broken during live play, volume dropped to 0, users unable to close positions. Goals tab issue confirmed fixed ~19:34 UTC. Esports (Dota 2 OG vs Grind Back) scoreboard widget showing reversed per-game outcomes vs resolved results. Geo: Ireland misidentified as GB; Ecuador blocked as USA. General geoblock bug fixed ~19:32 UTC June 23. Wallet: Migration failing, funds temporarily disappearing. Gnosis SAFE not supported for new wallet deployment (EOA only). 📋 Clarifications MrBeast views markets (133–136B by July 31): all resolving to "134 billion," losing shares refunded. Bilibili Gaming roster change before July: resolving NO, losing shares refunded. Bitcoin vs largest company before 2027: rules updated — BTC cap source = CoinGecko daily; largest company = companiesmarketcap.com hover value. CL Oil markets: new strikes ($80/85/90) use 1-min Pyth candle rules; existing strikes use daily CME settlement — inconsistency flagged, clarification pending. Wunderground (#climate): temp data reverting after updates — mod advises not to trade affected markets. With the API still hard-failing at offset 2100 and cancel orders filling despite returning success, how confident would you be trading programmatically on Polymarket right now?

UMA DIGEST — 24 JUNE 2026 ⚡ Disputes A Polymarket market (linked by abhiz69) was nearly mis-resolved due to a Yahoo bug showing incorrect data at proposal time. lonfus disputed with ~1 minute to spare before settlement, preventing a mis-resolution. The bug self-corrected after the proposal was submitted. Colombian election results market was proposed at ~99.9 — users noted results may not yet be final, with AI suggesting finalization today/tomorrow. Dispute risk flagged. 📋 Clarifications Multiple Polymarket temperature markets (Madrid, Wuhan, Milan, Singapore, Sao Paulo, Buenos Aires) were taken down, seemingly due to an over-eager response to bug reports — only Madrid and Wuhan had real issues. user_v123 acknowledged he knew the markets were broken and should have disabled the entire event, noting his process needs a better kill switch. The Madrid clarification used an incorrect temperature, though both the true winner and the clarified winner were untradable so no one held positions — refunds expected. Wuhan may not have been clarified before settlement. Regarding dispute authority: Thonker is not considered authoritative — he's just a trader. JessicaOnlyChild's track record is largely because UMA voters follow uma.rocks. How many markets do you think get quietly mis-resolved every week because disputes arrive too late or go unnoticed?

POLYMARKET DIGEST — 23 JUNE 2026 🔥 News & Announcements CLOB Maintenance: Wed Jun 24, 04:00–05:00 UTC. Fixes for queuing tiebreak and cancellation edge cases. Trading intermittent up to ~1 hour; 2-min post-only window after restart. UFO markets resolved Yes — Trump declassifies new UFO files by Jul 31 and Aug 31. Starmer Resignation Speech word markets batch-resolved: "Ban", "Labour", "Europe", "Russia/Ukraine", "Thank" (5+) and others → Yes; "Trump", "NHS" (3+), "Crime", "World Cup" and others → No. Madrid Jun 22 temperature resolved → 39°C. Milan Jun 22 → 35°C. Losing shares refunded. Referral rate cut from 30% → 10% confirmed. ⚠️ Bugs & Issues Positions showing N/A — filled orders deduct balance but positions invisible in portfolio and excluded from P&L. Team acknowledged, investigating. Auto-redeem broken — winners can't claim; losing $0 positions inflate equity display; "Close Losses" button unavailable. Ongoing for weeks. Weather markets archived (Singapore, Wuhan, Milan, Madrid, Sao Paulo, Buenos Aires — Jun 22). Positions disappeared, funds not returned. Mod confirmed team notified; refunds expected per standard procedure. At least one user still awaiting refund from a May outage (1+ month ago). LP rewards Jun 20 not paid — only Jun 21 distributed. Maker rebates for Jun 22 and level-up bonuses also outstanding. No official response. Data API outage — data-api.polymarket.com/positions returning 408 timeouts for hours. Dev claimed fixed; users reported issue persisted. Order/cancel latency spike — P95 ~800ms vs normal ~70ms, started ~10:00 UTC Jun 22. DeadlineExceeded RPC errors at ~3800ms. Reportedly normalized by ~18:32 UTC. Crypto price endpoint blocked — polymarket.com/api/crypto/cry… returning Cloudflare 403 for Python/bot clients since ~04:30 UTC Jun 23. Workaround: use curl-style requests. PNL chart broken — shows massive losses on profitable days; cost averages and traded amounts display as 0. Frozen for hours; team investigating. Geoblocking bug — users from Quebec (CA) and other unrestricted regions getting geo-restricted with no announcement. CLOB SDK auth bug (critical, ongoing) — new accounts (post-Apr-28) hit "order signer address has to be the address of the API KEY" error. Root cause: Privy EIP-7702 deposit wallets; SDK L1 auth binds API key to EOA instead. Reproduced on py-clob-client-v2 1.0.1 and Rust SDK 0.5.1. Old accounts on sig_type=1 unaffected. GitHub: #64, #65, #70, #83, #344. No engineering response yet. WebSocket disconnects at ~10k asset IDs and ~10 min after connection (heartbeat issue). Perps API still unreleased despite being promised "shortly" 3+ weeks ago. 📋 Clarifications Shenzhen Jun 23 — user reports 32°C market not settling despite recorded temp of 33.33°C. Unresolved. Iran-USA peace deal market — user alleges Jun 12 option was erased from the market. Unconfirmed. ⚡ Disputes Madrid 39°C clarification timing — user_v123 proposed 40°C YES at 22:06:41 UTC; clarification issued at 22:12:55 UTC (6 min later). User questions legitimacy of post-proposal resolution. Polymarket policy: losing shares at time of clarification to be refunded. With the CLOB SDK auth bug blocking new accounts from trading for weeks, how much longer can Polymarket afford to keep new users locked out before they migrate to competitors?

UMA DIGEST — 23 JUNE 2026 ⚡ Disputes IEM Cologne 2026 Grand Finals — "team ace" market: carlitos2d2 disputes a NO resolution, claiming the phrase "It's a team ace." was said at 00:56:23 in the stream. aboss argues the instance doesn't count as the game hadn't started yet. carlitos2d2 counters that the market was proposed NO due to bots not catching it (they only auto-propose YES), which has allegedly happened multiple times before. mebeim told carlitos2d2 to read the rules more carefully. Status: unresolved. Argentina vs Austria — "Ronaldo" market: .rucat is asking whether FOX Sports YouTube and FOX TV channel broadcasts differ for resolution purposes. mebeim offered to compare clips if sent one from today's France vs Iraq match. im.the.wizard noted that flame only just realized World Cup games are still on old rules. armanh01 mourned another roundtripped dispute. If bots are consistently missing YES instances while auto-proposing NO, should markets have different resolution standards or stricter bot training to level the playing field?

POLYMARKET DIGEST — 22 JUNE 2026 ⚠️ Bugs & Issues LP rewards delayed: Multiple users report missing LP rewards for June 20. kurwamach. confirmed the team is aware and payouts will be distributed ASAP. As of ~00:12 UTC June 22, the missing rewards are still outstanding (recent payouts received are for a different day). Taker rebates: Several users (including Platinum-tier) reported missing taker rebates for June 20–21. Rebates appear to have hit around 01:25 UTC June 22. Discrepancy between betmoar data and Polymarket UI noted. PnL chart broken: Widespread reports of PnL charts showing incorrect losses — some users see losses larger than their total wallet balance. Closed winning positions are displaying as "Lost" with 0 PnL. Affects both frontend and API. Multiple users confirm the issue persists into June 22. Order book issues: Broken order tabs showing nothing, orders not appearing after placement, cancel button missing, canceling leaves ghost orders. CLOB also reportedly restarted, wiping resting orders from the past ~1–2 hours. 5-minute crypto markets unresolved: BTC and ETH 5m markets stuck unresolved for hours past resolution time. Some required manual redemption. gibumee81_91638 reports positions queried via API returning alive at 0.505 instead of resolving. Weather markets (June 22): Several cities (Singapore, Wuhan, Milan, Madrid) have markets marked active: false, making them inaccessible. Sao Paulo and Buenos Aires markets are missing a resolution source. user_v123 flagged that UMA price request multicalls are being used again — the same mechanism that caused incorrect resolutions a month ago. hans32312 acknowledged and said they'd escalate. Account balance showing zero: At least one user (ugain) reported balance unexpectedly dropping to 0 with no activity to explain it — reported twice ~8 hours apart with no resolution. KYC bug: KYC form page 4 switches to a KYB form. Noted by qu27362; tsmultra acknowledged. Trezor hardware wallet + combo bets: Persistent error for 1+ week preventing combo bets via Trezor-connected wallets. Hot wallets unaffected. Deposit wallet SDK (sig_type 3): py-clob-client-v2 users with deposit wallets unable to place orders — API key binds to EOA but orders require deposit wallet signer. suhailkakar confirmed the fix is on track pending general UI access rollout. Rewards "boosted" label showing despite reduced rates: UI inconsistency flagged by avniyayin. Settled markets not auto-closing for trading: At least 3 Netflix weekly show markets settled and redeemable but still open for trading. General site performance: Widespread complaints about freezing, lag, slow load times. berth6833 listed broader systemic concerns: frequent CLOB restarts, rate limit inconsistencies, known exploits taking months to fix (ghost fills, taker delay bypass, queue position skip), and heavy reliance on third-party tool betmoar due to slow official UI. With so many backend issues stacking up—CLOB restarts, ghost orders, unresolved markets—do you think Polymarket should pause new market creation until core infrastructure stabilizes, or would that hurt adoption too much?

UMA DIGEST — 22 JUNE 2026 🔥 News & Announcements A suspicious whitelisted address (0x16d01c0d2fd3fb2a1c26d6d02d88239bb3def3e0) with no prior proposal history submitted disputes on Spain and Uruguay markets. alexchunus suggested this is likely a Polymarket/UMA staff address exempt from performance requirements. Separately, a new contract address (0xd2ef90fc52ad515cdb210543eb492a48b420c94c) appears to be testing a modified UMA request method — alexchunus strongly criticized this, noting the same approach caused a previous "disaster" and calling for whoever is responsible to be fired. ⚡ Disputes US–Iran Diplomatic Meeting (June 21) — resolved YES, post-resolution debate ongoing. _cyrus.fernaldo argued for NO, claiming: (1) the meeting was derailed into third-party crisis management over Lebanon/Hormuz rather than bilateral US-Iran diplomacy, and (2) delegations remained in physically separate villas at Bürgenstock, allegedly failing the "in-person indirect" threshold. The request failed to attract a whale to post the dispute bond. Community reaction was largely dismissive — mebeim and others noted the market had already resolved YES and no official dispute was raised in time. ghost69 raised skepticism about whether an actual meeting was formally announced, but acknowledged it's inconclusive at best (P4 territory). The window to dispute has effectively passed. If a market resolves YES but the details were ambiguous enough that people debate it for days afterward, should resolvers be required to publish a detailed reasoning statement alongside their decision?

POLYMARKET DIGEST — 21 JUNE 2026 ⚠️ Bugs & Issues LP/Maker Rewards not distributed correctly: Multiple users report that daily liquidity rewards (normally at 00:00 UTC) arrived ~15 minutes late on June 21 and were severely underpaid — elvinn.p expected $200+, received $0.76; pooty999 expected $3k+. Issue appears to affect many LPs. No official acknowledgement yet. Orders disappearing / unable to cancel: hakei. reports a critical bug where limit orders placed on the book become invisible and uncancellable via both the UI and portfolio page, creating uncontrolled risk exposure. Demands acknowledgement, fix timeline, killswitch, and clarity on refunds. CLOB API — sig type 3 (deposit wallet) broken: Multiple users (cryptosamy, shenlol., 1nevitably, martincaballero, muhammadmahibnazir_28497) report that new accounts using the deposit wallet flow (POLY_1271 / sig type 3) cannot place orders. Errors: maker address not allowed, please use the deposit wallet flow and the order signer address has to be the address of the API KEY. No working workaround confirmed; legacy wallet accounts (sig type 0/1/2) are unaffected. API — invalid TAKER_REBATE filter: /data/activity endpoint returns invalid activity filter type TAKER_REBATE — frontend dropdown references a filter value not accepted by the backend. jgoyvaerts confirmed the issue persists. Frequent auto-logout: sabari_crypto and others report being logged out 20+ times/day over the past 3 days, especially when opening new tabs. Taker rebates not being received: jgoyvaerts, satatardy, lostgorilla24 and others with Silver rank report receiving zero taker rebates despite being eligible. /data/trades endpoint lagging: yc.hh notes matches on /data/trades only appear several minutes after execution — ongoing issue reportedly broken for weeks (mebeim). Relayer redeem API: beastie67 identified that ~9 hours ago the positions API stopped returning newly resolved winning positions under redeemable=true, showing old lost positions instead. Resolved manually; relayer now working again. Combos not counting towards PnL: ccashcrypto reports combo positions are excluded from PnL calculations. UI showing $0 profit on settled markets: krasnaya. reports markets auto-redeemed at 100¢ display as $0 profit / a loss. RTDS dropping ~70s each hour since yesterday's maintenance (mr.w1ggles). Chainlink RTDS issues also reported by _valentyn_. Hype events API: evmpapa reports eventMetadata.priceToBeat field not returning data for hype markets via gamma-api. If you were affected by the LP rewards underpayment or API issues today, would you stick with the platform or look for alternatives?

UMA DIGEST — 21 JUNE 2026 📋 Clarifications Two FIFA World Cup Group E proposals were flagged by virtual.realization as potentially incorrect — specifically markets resolving Germany as not qualifying for the next round. The concern: if Ecuador wins both remaining games and Ivory Coast beats Curacao, all three top teams finish with 6 points, and tiebreakers could theoretically place Germany 3rd. After discussion, virtual.realization and infinity_d concluded the proposals are likely correct — a 3rd-place team reaching 6 points requires a very specific circular win pattern, which is already impossible in many groups due to draws, making Germany's advancement mathematically guaranteed regardless. ⚠️ Bugs & Issues A bot has submitted 7 incorrect tennis proposals over 2 days due to a bad data source (including a wrong set ball reading). woodmark520 noted the bot is profitable in MLB/NBA but has lost ~10k in June from tennis alone, suggesting the bot owner should switch tennis data sources or stop proposing tennis markets entirely. im.the.wizard flagged an ongoing issue: reviewed plays at end of 1st and 5th innings in MLB games may cause bad proposals — monitoring is in place but coverage within the 15-minute liveness window is not guaranteed. Given that this tennis bot is hemorrhaging money on bad data while staying profitable elsewhere, should bot operators be required to pause markets in sports where they're consistently underperforming?

POLYMARKET DIGEST — 20 JUNE 2026 🔥 News & Announcements Taker rebates went live ~June 19–20. Payments confirmed, but amounts don't match expected fee calculations. Gold-tier users received $376–$384; one address got $1,970. (alias1.possibly251, drowndrawn) Queue-jump exploit confirmed by Polymarket — was active for several weeks; taker delay bypass fixed separately. Polymarket servers confirmed in London; AWS Ireland recommended for lowest latency (~11ms RTT). London VPS requires KYC approval (~3 week wait) but offers best non-geoblocked latency. UK residents blocked from KYC entirely. ⚠️ Bugs & Issues API / Orders: POST /orders returning 425 "Too Early" / "order manager not ready". Hidden orders that can't be cancelled continue to fill. py-clob-client-v2 1.0.1 failing with "maker address not allowed" on Polygon mainnet (sig types 0, 1, 3 all fail) — refs GitHub #70, #71, #75, no fix yet. (dekey1, xniiinx) Shares disappearing: 2.62 YES shares lost after market close despite auto-redeem off; API also fails to detect position. (donnell3516) Auto-redeem triggering for users who never enabled it. (dark_souls2) Perps UI showing empty account despite confirmed on-chain deposit. (klim_nova) Mobile: Changing pages logs user out — platform effectively unusable on mobile. Rewards click also causes logout — unresolved for months. Other: Combo wins/losses not in PnL. Leaderboard bug. Balance freeze on redeem. RTDS dropping more frequently post-maintenance + ~2–3 min outage observed. Chainlink sending intermittently delayed data. WS 403 errors. Rate limits appear tightened without doc update. Python client described as broken. (mr.w1ggles, alias1.possibly251, thetathunberg) Fund recovery: USDC deposited to API wallet via BNB chain — "Login with Mail" not supported on BNB recovery site. (butlfirst) 📋 Clarifications Iran uranium enrichment markets (Jun 30 / Jul 31 / Dec 31): Clarification issued ~9 PM UTC June 19. The signed MOU states Iran "will not advance its nuclear program" but does not explicitly state it will halt/suspend/cease enrichment → MOU does not qualify for YES resolution unless credible reporting clearly establishes an agreement to stop enrichment by the specified date. Order books were cleared at 5 PM ET June 19. (nickthechopper flagged misleading end dates.) Valorant Masters London 2026 ACS markets (~50 player markets): Resolves to player with highest average ACS across all maps played at the event. Dallas temp (June 19): 86°F reading at 00:00 not captured by WunderGround (METAR only at ~:53 past hour) → 84°F stands as the daily high. NYC low temp: 12:51 AM counts as the following day; last reading of the current day is 11:51 PM. (modali1) Overwatch BO5 vs BO3: Matches incorrectly listed as BO3 — recurring issue. (golduss12) With the taker rebate payouts showing such wild discrepancies, do you think Polymarket should pause the program until they fix the calculation logic, or just manually adjust individual accounts?

UMA DIGEST — 20 JUNE 2026 ⚡ Disputes Gold (XAUUSD) $4,200 Low — Week of June 15 Market proposed NO, currently in dispute window. iknow_75794 argues it should resolve YES: a Pyth XAU/USD 1-minute candle on Jun 18 at 19:17 ET showed Low = 4194.323, during active Gold Globex trading after the daily break. His argument: rules cite Pyth 1m High/Low during "applicable trading session" — no mention of CME trade-date accounting. Community is split; kaanha_ cited the rule "only prices during applicable trading session of the specified timeframe's business days" as the reason for NO. No one stepped up to dispute on his behalf due to $1,500 cost. Market appears to have settled NO. US lifts Iran OFAC Sanctions by June 17 Proposed NO by "Scout" in a low-liquidity market. ronin331 argues YES: the US-Iran MOU (signed electronically before June 17, text released June 17) explicitly commits Treasury to issuing oil export waivers — qualifying as an "official action materially easing OFAC sanctions," with rules explicitly covering actions not yet in effect. dbipc counters that the MOU promises waivers but hasn't issued them. The NO proposal was auto-extended (bot extension ≠ RL dispute, infinity_d clarified). June 15 strike settled NO; June 19 heading NO — signing date ambiguity (electronic vs. physical on June 18) appears to be key. No dispute filed due to low liquidity. Trump Truth Social Posts June 12–19 (120–139 bracket) Proposed as 140–159. ezhimkv disputes: xtracker shows exactly 139 posts at market close. psachin_ manually counted 151, noting xtracker has a known bug missing retruth/reposts — so the 140–159 proposal may actually be correct. alexchunus advised manual counting before spending $750 on a dispute. US-Iran Diplomatic Meeting by June 30 kongkong5318 flagged a premature YES/NO proposal; community confirmed it will resolve P4 (Too Early). If the Pyth candle truly hit $4,194 during active trading, does the market's strict interpretation of "business day" rules actually match the spirit of price discovery, or did it miss the intent?

POLYMARKET DIGEST — 19 JUNE 2026 ⚠️ Bugs & Issues Queue-jump exploit (critical, unresolved): A CLOB order queue exploit using manipulated EIP-712 signedAt timestamps allows certain accounts to jump ahead of resting orders. lostgorilla24 confirmed it was submitted via the bounty program on 05/26 and is actively being used by hundreds of wallets (at least 8 identified on BTC 15m since mid-April). coolnyul and others are pressing for an urgent fix. chrund1e acknowledged it and said eng is looking into it, but no patch timeline given. Scheduled CLOB maintenance (Jun 19, 04:00–05:00 UTC): 0xdanzu announced planned downtime — trading intermittent for ~1 hour, post-only window for ~2 min after restart. Maintenance confirmed started and nearly complete by 05:03 UTC. Data API / Positions outage (~13:45–14:23 UTC): /positions returning 404, profile pages inaccessible, gamma API slow. suhailkakar confirmed it was a data API issue and rolled out a fix by ~14:23 UTC. Other active bugs: — Auto-redeem triggering despite being disabled — Combo PnL not reflected in overall account PnL (any time window) — Portfolio history tab not loading for ~1 week — Esports map data UI showing incorrect map winners — App logging users out on Settings → Trading — /closed_positions showing realized_pnl: 0 for World Cup winning positions (wrong update timestamp logic) — Gamma API offset now capped at 2000 (undocumented change); limit also silently capped at 100 despite docs saying 500 — Rewards disappearing from markets as soon as qualifying orders are placed — UI date-rendering loop on US cities / Mexico weather markets — current day skipped, shows tomorrow instead (ongoing 2 weeks, unresolved) — Python SDK: UserTradeEvent silently dropped due to fee_rate_bps empty string → Decimal conversion error. brainjammer noted a fix was shipped in yesterday's release (GitHub issue #107) — API tick size delay: 0.999 tick available on UI immediately but API needs 10–15s to accept it (ongoing 1–2 months) 🔥 News & Announcements Taker rebate first distribution confirmed by 0xdanzu to go out at 12:00 UTC, continuing daily from Jun 19. Chainlink data stream access will require $500/month starting July 1 for RTDS feed used in crypto market resolution. deadshot453 raised the issue; suhailkakar confirmed they are in discussions with Chainlink and will share updates once finalized. Community reaction strongly negative — teun983 and others noted this effectively prices out smaller market makers, especially combined with taker-rebate tier requirements. deadshot453 also requested an update on the previously mentioned VWAP resolution migration before committing to Chainlink fees. 📋 Clarifications UMA Optimistic Oracle docs incorrectly state "anyone can propose or dispute an outcome" — drinksaucer flagged that proposers must be whitelisted and have $750 available; docs have not been corrected. CLOB maintenance: 0xdanzu clarified this specific release targets cancellation error consistency fixes and extra logging. Latency improvements (DB path + async processing) are ongoing but need extended testing before release — dates TBD. With the queue-jump exploit actively being used by hundreds of wallets and no patch timeline given, do you think Polymarket should halt affected markets temporarily to protect other traders?

UMA DIGEST — 19 JUNE 2026 ⚡ Disputes Iran enrichment freeze market — Active dispute over whether Iran's "nuclear status quo" clause in the US-Iran MOU constitutes a qualifying pledge to end all uranium enrichment. P2 (YES): jaroborzita argues a consensus of credible reporting (Reuters, WSJ, NYT, Washington Examiner, JHU professor) confirms "status quo" = enrichment freeze. Iranian MP Nabavian explicitly stated it means "no more enrichment." P1 (NO) / P4 (Too Early): Multiple users contest this: — hiroshifumando demands an official Iranian pledge, noting Iran previously stated it would continue enriching — pi7486 calls it a "scam attempt," arguing market rules require an Iranian pledge, not media interpretation; accuses orchestrated resolution of lower-volume brackets first — __jkh__ cites AP, Axios, Reuters, CTP and IAEA report confirming enrichment facilities were not inspected, making "status quo = zero enrichment" unverifiable — drinksaucer notes only 1 news article and 2 blog posts explicitly state the YES outcome; also points out historical "freeze" terminology means halting expansion, not all enrichment — ken51444 argues status quo legally defaults to JCPOA 2015 terms (low-level enrichment permitted) registar89 expects YES resolution along with the Iran enrichment December market. FIFA World Cup Group A (Mexico) — undertaker8993 raised a dispute claiming the market resolved too early. Community consensus pushed back: Mexico holds head-to-head tiebreaker over South Korea regardless of final match result. petroni_k withdrew the dispute request after confirming the tiebreaker rules. ⚠️ Bugs & Issues kekone0 reports losing access to UMA dispute thread discussions and asked for clarification on whether they were demoted. No response recorded. Does the lack of official Iranian verification of the "status quo" clause make this dispute fundamentally impossible to resolve fairly?

POLYMARKET DIGEST — 18 JUNE 2026 🔥 News & Announcements CLOB Maintenance — rescheduled to Jun 19, 04:00–05:00 UTC (2 sequential restarts). Postponed from Jun 18 due to Gamma being unhealthy; team wanted a clean state first. Taker rebates still unpaid despite May 28 announcement. Maker rebates were delayed but at least one user confirmed receipt ~04:33 UTC Jun 18. Chainlink Data Streams going paid ($150–500/mo) from July 1 — community discussing alternatives (Polymarket relay, Pyth, etc.). SPX 5min markets blocked for legal reasons (confirmed by dev 0xdanzu). Gold/oil 5min markets under discussion; Hyperliquid has gold feed, Pyth has oil. Scam alert: attackers hijacking US government X accounts to impersonate Polymarket. Do not interact. ⚠️ Bugs & Issues UI / Orders: Limit orders disappearing/reappearing; cancellations not reflecting; filled/cancelled orders showing as active. Portfolio page not displaying open orders. Users logged out every 5–10 min on macOS Safari. "New" tab missing on mobile. Redeems: Combo bet shares missing; "redeem failed" / 0 received errors despite on-chain resolution in user's favor; frequent execution reverted errors. Shares being auto-redeemed without consent (ongoing days). BTC 5min/15min markets disappeared from UI and API ~20:13–20:41 UTC Jun 17; fixed. Timer bug: BTC 5min showing >5 min remaining. Climate markets (Jun 18) — all major cities (Atlanta, NYC, Miami, etc.) broken: active: false, no resolvedBy address, priced at $0 via API. Likely UMA price request failure. Gamma API down 01:43–04:28 UTC Jun 18 (500s / timeouts); fix deployed ~04:28 UTC. Latency: Crypto market taker latency degraded — avg ~980ms, p95 crossing 3.5s. Root cause: shared infrastructure with sports markets overloaded by World Cup. Decoupling fix acknowledged as invasive / no ETA. Bilibili Gaming MSI 2026 market archived on UI, position still exists on-chain, condition unresolved — user cannot manage position. Cash-out UI shows wrong yes/no token price in some cases. CLOB queue suspected non-FIFO; live orders not matching and not cancellable. ⚠️ API / Dev py_builder_relayer_client broken — TypeError: RelayClient.__init__() got an unexpected keyword argument 'host'. User innerstanding claims gasless order signing via relayer is fully blocked by Polymarket; all related builds non-functional until API reopens. ⚡ Disputes Wash trading suspicion on PGA US Open market — volume spiked 100k → 500k, attributed to single-use accounts trading at 99.8¢. Community flagged it; no official response yet. With taker rebates still unpaid and latency hitting 3.5s on crypto markets, how much longer can Polymarket retain traders before they migrate to competing platforms?

UMA DIGEST — 18 JUNE 2026 ⚡ Disputes US-Iran Peace Deal (June 15) — Highly contentious. The market resolved YES despite Trump explicitly stating "It's not final, it's a memorandum of understanding," with the MOU only signed electronically on June 17. NO holders are vocal but the dispute window has closed and UMA votes are finalized (99.98% YES). Some are emailing [email protected] as a last resort. No mechanism remains to overturn. Trump Physically Signed Iran Deal — Initially disputed by famouspet, arguing Bloomberg, Al Jazeera, and Iran's FM all confirmed only an electronic signature. aenews countered with AFP and a US official confirmation; usernamethr33 posted a video of Trump physically signing at Versailles during G7. famouspet conceded ("gg"). Market resolving YES. Iran Airspace Closure — Strong YES case: NOTAMs confirm complete closure of all western Iranian airports including Shiraz (OISS) and Isfahan (OIFM) — exactly the two airports named in market rules — due to non-weather causes (drone/missile launches toward Kurdistan). Market was proposed YES, then disputed (allegedly by a large NO holder to stall). ronin331 and ferragamore argue evidence is overwhelming and a clean rules strike. pi7486 is calling on admins to settle. Market is currently extended and sitting at ~66-92c, with no substantive NO argument presented. Trump Daily Insult Market (June 16) — Debated which quote qualifies: "Nobody ever heard of him" (about Sen. Jack Reed) vs. "Os(jerk!)off" (about Sen. Ossoff). laurleo proposed based on the Reed quote; mak_disc and ronin331 lean toward it qualifying. Market has a $500 bond due to a reward glitch at creation, limiting dispute reward to $125. Football Player Props (Shots on Target / Live Blog stats) — Ongoing meta-dispute about whether live blog data is valid for proposing. im.the.wizard argues live blogs are not official final stats and cites a new UMA rule that all markets settle on final results. banhmichuoi and whosay8888 push back, questioning whether the precedent was legitimately set (alleging it may have been a self-dispute to manufacture precedent). Significant personal conflict between im.the.wizard and abhiz69 throughout. ETH $1800 (June 17) — Proposed YES. Market opened 12:35 AM ET, price hit at 12:50 AM, UMA timestamp 12:52 AM. Community consensus: counts, rules say any candle 12:00 AM–11:59 PM ET, no dispute expected. Given that the Iran Airspace market has overwhelming evidence but sits in limbo while someone disputes it purely to stall, should UMA implement a "bad faith dispute" penalty to discourage frivolous challenges?

POLYMARKET DIGEST — 15 JUNE 2026 ⚠️ Bugs & Issues Major website performance issues during World Cup period — multiple reports of severe lagging, site not loading, login problems requiring 8+ attempts. Several critical API/websocket problems: - Trading API requests timing out completely - Auto redeem activating without user permission - Limit orders disappearing from profiles but remaining on orderbook, unable to cancel - WebSocket connection dropping immediately after subscription, affecting live data feeds - Order latency severely degraded (900ms average vs usual 30ms) - Websocket vs API orderbook inconsistencies lasting over a week - $1,152 stuck in sponsorship contract for 3+ days awaiting refund - Combo betting odds calculation bug showing incorrect multipliers - Amount won column displaying wrong values on Closed Positions page Market-specific issues include wrong country flags (Congo vs DRC), incorrect market slugs (Germany vs Curacao showing as "ger-kor"), and token splitting failures via builder API. 🔥 News & Announcements No delay policy implemented for World Cup markets — Major market makers expressing strong opposition to zero-delay trading on live soccer matches. alfa4663 (1M daily maker volume) reports turning off World Cup market making entirely due to adverse selection risks from courtsiding and latency spikes. Multiple MMs arguing this harms liquidity provision and increases spreads, benefiting only short-term taker fees while potentially driving makers to competitors like Kalshi. verylowsharpe revealed the no-delay decision was a direct request from a major Polymarket investor who is also a market maker with people at matches. 📋 Clarifications Deposit wallet API integration still broken for post-April 28 accounts — py-clob-client-v2 cannot properly handle signature_type=3 orders, with multiple developers reporting identical failures. No official workaround available despite being a core API feature. Given the combination of severe technical issues, market maker exodus over the no-delay World Cup policy, and potential conflicts of interest, do you think Polymarket prioritizes infrastructure stability over market integrity?

UMA DIGEST — 15 JUNE 2026 ⚡ Disputes Major dispute over early proposal rules after Germany-Curacao match. Users questioning systematic discrimination in proposals, with specific addresses (0xd3100864311af00423D8B7133D97B46a33DB8224 and 0x4ADe37f58C505aCd00528a062615E26d67c423b3) allegedly proposing players who didn't play. Discussion centers on whether goals+assists can be proposed before official statistics if exceeding team's total goals. banhmichuoi raised concerns about inconsistent precedent: "So lineups is allowed to be used but not timeline? What's the logic." Community waiting for P4 dispute vote to establish precedent on 2-hour rule enforcement. Active dispute on US-Iran Peace Deal markets. arien_80526 argues for NO resolution citing "explicitly temporary" clause violation - the June 14 announcement is a 60-day ceasefire framework, not permanent peace. okbrear99109 supports NO across all dates, noting Reuters calls it "peace framework" with no signed document yet. im.the.wizard disputed Stanley Cup Finals assists market after McNabb was incorrectly proposed as NO despite having most assists. 📋 Clarifications Confusion over "include a player not listed above" market interpretation - virtual.realization clarified "above" doesn't mean literal UI position, causing abhiz69's initial misunderstanding. ⚠️ Bugs & Issues testoo7 flagged potential scam market created overnight for US-Iran nuclear deal. boatylife criticized nuclear deal market rules as "terrible" and "open to way too much interpretation" - noting "any mutual agreement works. ANY." abhiz69 complained about lack of response from Polymarket over 3 days before main clarification, citing difficulty reviewing 200 proposals in 600 seconds. Which matters more for market integrity—enforcing strict rule definitions upfront, or having flexibility to adjust based on how disputes actually play out?

POLYMARKET DIGEST — 14 JUNE 2026 ⚠️ Bugs & Issues Multiple API and platform issues reported: - Balance errors: "Not enough balance" errors when placing limit orders despite sufficient funds - API exceptions: danye03 reported PolyApiException errors for post/get/cancel order requests, though orders execute successfully - WebSocket data inconsistencies: saas2501 noted price/bid/ask mismatches in market WebSocket channels - Queue ordering problems: walem observed orders not following FIFO queue position - later orders getting filled first despite queue position - Auto-redemption bug: satatardy reported positions auto-redeeming despite setting being disabled - Ghost fills epidemic: parameter435123 reported massive increase in failed transactions/ghost fills, affecting both old proxy wallets and new deposit wallets - described as "50 times today" and forcing bot shutdown - PnL calculation errors: yc.hh reported sudden $1000 accounting error in bot - FOK order failures: error403kabaaperror experiencing Fill-or-Kill orders failing despite sufficient liquidity at better prices - Temperature data bugs: user_v123 confirmed ongoing issues with Weather Underground temperature changes affecting multiple cities (Mexico City, Seoul, Manila, Lucknow) 📋 Clarifications - tsmultra confirmed team will flag balance/limit order bug despite workaround availability - highhopes13 noted py clob client v2 doesn't work with new accounts, recommending new python SDK instead - alias1.possibly251 confirmed deposit wallet feature is being upgraded to v2 With ghost fills happening 50+ times daily and even experienced traders getting forced to shut down their bots, is Polymarket's infrastructure stability at a breaking point?

UMA DIGEST — 14 JUNE 2026 📋 Clarifications Polymarket clarified several World Cup soccer prop bets, specifying that "goals + assists" markets combine both stats - players with 0 goals and 1 assist count as hitting their "1+" lines. Multiple markets received this clarification after confusion from proposers. ⚡ Disputes Box Office Negrisk Refund Request: abr7x7 proposed "Yes" on duplicate movie brackets within the same negrisk group, following what appeared to be precedent from a resolved market. Users are divided - some blame Polymarket for creating duplicate brackets, others say proposers must understand negrisk mechanics. infinity_d confirmed awareness of the situation. Risk Labs considering possible refund similar to previous lonfus case. Early Soccer Props: cricket_666 self-disputed two World Cup prop markets - one for proposing wrong answer, another to test precedent on early proposals. Despite having 11k+ proposals without error, chose to break perfect record rather than let wrong precedent stand. LoL Tournament Markets: Early disputes on League of Legends bracket resolutions questioned for being proposed before consensus reporting, but liquipedia has since updated confirming results. ⚠️ Bugs & Issues Reveal functionality temporarily broken but has been fixed by infinity_d. _cyborg_1 reported ASSERT_TRUTH identifier not whitelisted on Base mainnet, blocking OOV3 usage and locking user funds in 2 production markets. Team has workaround using ASSERT_TRUTH2 for new deployments. Should Polymarket prioritize fixing duplicate bracket issues proactively, or is it ultimately the proposer's responsibility to understand negrisk mechanics before posting?

POLYMARKET DIGEST — 13 JUNE 2026 ⚠️ Bugs & Issues Major CLOB system outage with PostgreSQL connection errors ("FATAL #53300 remaining connection slots"). Multiple critical bugs affecting trading: • Auto-redeem malfunctioning - positions redeemed despite feature being disabled • Combo betting broken: odds resetting to x1, "unavailable" errors, incorrect profit calculations • API authentication failures - 50% of requests getting 401 "Unauthorized" errors • Order system issues: GTC orders auto-cancelled, timeouts, 5+ second latency spikes • Orderbook UI showing wrong prices and phantom cancelled orders • New accounts (post-April 28) blocked with "maker address not allowed" errors • WebSocket rate limiting (429 errors) affecting live data feeds Additional issues: World Cup markets visibility problems, sponsorship contract bug ($1152 stuck), incorrect PNL calculations, site logout glitches. 📋 Clarifications Market mechanics clarifications: • Market sells have no $1 minimum limit (unlike buys), explaining consecutive small fills of 0.01-0.05 shares during sports events • Fee structure questions regarding PUSD vs share deduction methods • Discussion of new rate limits being implemented across the platform Weather markets update: Munich temperature hit 17°C with unexpected late-day timing. Users claiming rewards from 3-week-old Seattle temperature incident. With half of API authentication requests failing and new accounts completely locked out, how much trading volume are you estimating Polymarket is actually losing right now?