POLYMARKET DIGEST — 30 JUNE 2026
⚠️ Bugs & Issues
Widespread platform instability reported throughout the day. Key issues:
• Ghost orders flashing on/off (especially on esports/LP-reward markets) — 0xdanzu confirmed this is a known issue; fix involves shifting to maker rebates on fills and reducing traditional LP incentives
• CLOB latency spiked sharply (~09:00 UTC), median jumping from ~400ms to 1700ms+ — unusual as degradation was sudden rather than gradual. 0xdanzu confirmed team is aware; latency partially recovered by ~20:00 UTC
• MetaMask login broken (Windows/Brave) — users unable to log in, error: "Request Cancelled"
• API errors: order timeouts, EIP-7702 authorization rejections, batch nonce mismatches, 504s, merge failures, "Not enough balance" false errors, RTDS briefly down
• Split shares function broken ("split shares failed")
• Direct market links failing ~90% of the time; workaround is searching from homepage
• Market comments no longer expandable on Chrome/Android
• Taker rebates skipping days / arriving every other day — backpay requested; maker rebates also reportedly missing
• Beacon wallet deployment (scheduled ~12:00 UTC) suspected as possible cause of latency spike, though unconfirmed — parameter435123 raised concerns about potential queue-position implications
• 45trinity reported losing ~$500 to a reward-mining ghost order exploit on weather markets — orders placed to farm LP rewards but never genuinely fillable; reported to Polymarket team with video evidence
blunkoed asked about Data API moving to euw1 and whether CLOB will follow — no official response. Per Polymarket Devs Friday update: Data API production cutover to euw1/EKS cluster is already live.
📋 Clarifications
• Israel × Lebanon diplomatic meeting markets (by July 10, July 17, July 31): all three markets will immediately resolve to "July 31st"; losing shares refunded
• Republican House incumbents market: title error corrected to reflect actual contract terms; all No positions at time of clarification refunded
• World Network verification market: resolution source updated — "Unique humans" no longer shown on World homepage; will now use n_verifications from https://t.co/MN7Yqe7uqu
With latency spiking to 1700ms+ and ghost orders still exploitable, how much longer do you think traders will tolerate these friction costs before switching to competing platforms?
UMA DIGEST — 30 JUNE 2026
⚡ Disputes
Major dispute wave over soccer player prop markets (Germany vs. Netherlands, extra time game). 100+ markets were proposed prematurely while the match was still in extra time/penalties. Under the new UMA rules, all markets must wait for the official final result before being proposed.
im.the.wizard and tenacious_mango_59265 split a 750 USDC bond to dispute one market (Havertz assists) as a test case, arguing proposals are P4 since the match wasn't final. im.the.wizard cited explicit confirmations from egg and infinity that the match must be fully over, and jessica previously flagged similar situations as likely P4.
kelkel8165 argued that "within the first 90 minutes of regular play plus stoppage time" is already a final, deterministic result — opposing the P4 claim.
The counter-argument: if player props don't need to wait for the match to end, then neither should moneyline or other main markets — which notably were not proposed mid-game, suggesting even proposers implicitly knew to wait.
A second extra time game appeared later in the day, raising further concerns.
📋 Clarifications
laurleo and abhiz69 raised a separate concern: shots, assists, and shots-on-target stats are often revised post-match, and FIFA only officially publishes match reports ~8 hours after the game. abhiz69 suggested requesting Polymarket extend the waiting period for these stat markets to 8 hours. Note: UMA has previously voted to treat the live blog as the final result, meaning live blog stats are not revised even if the official report differs.
im.the.wizard confirmed Goalscorer E = Florian Wirtz.
NY-13 Democratic Primary markets: stradiveri flagged a possible P4 concern on the margin-of-victory market. im.the.wizard clarified that losing candidates are generally eliminated even without official results — no challenge filed yet.
Should player prop markets really be treated differently from match-winner markets when both depend on the same match outcome?
POLYMARKET DIGEST — 29 JUNE 2026
⚠️ Bugs & Issues
Combo/Parlay system was down from ~12:36 UTC on June 28 — trades dropped to 0 while quote stream remained alive. kurwamach. confirmed engineering team was on it. The outage coincided with the start of World Cup matches, causing frustration. As of late June 28, status unclear.
Additional reported issues:
• Combo bets stuck on "Updating payment..." across multiple users/browsers/wallets (valentlem, razvi.19, stefino)
• Positions API failing (nzrod.)
• Gamma API returning connection errors / max retries exceeded (coltiw)
• Orders placed on mobile (MetaMask) not visible on other devices — cannot cancel cross-device (daysgoby_)
• 3-leg combo bet with all legs won is missing from Positions and History, $40.11 stuck — support unresponsive for 2+ days (adelejr06)
• MLB Totals market missing alt lines for 2+ days (amanforthepeople)
• UMA interface throwing persistent errors (spatrad)
• Taker rebates not backpaid for at least one user (anon_67046)
• Site inaccessible / tabs consuming 5+ GB RAM (alias1.possibly251)
• Suspected fake limit orders farming liquidity rewards with zero risk (silvaselva)
📋 Clarifications
"Will Trump post 'UFC' on Truth Social this week?" — resolved Yes. Polymarket ruled that a photo posted to Trump's Truth Social during the June 23–28 window, showing the UFC Freedom 250 event at the White House with the "UFC" logo clearly visible in large-format arena lettering, satisfies the rules requiring the term to be "spelled out clearly and in full." Order book was cleared at 4:00 PM ET on June 28.
🔥 News & Announcements
Polymarket appears to be moving its data API to Ireland — referenced via a tweet from @PolymarketDevs, noticed by wheelies5257 and confirmed by the link shared. Details sparse; blunkoed and tehnoobkiddo expressed surprise.
With the combo system down during major sporting events and multiple API failures stacking up, how much longer can Polymarket afford these outages before traders seriously migrate to competitors?
UMA DIGEST — 29 JUNE 2026
⚡ Disputes
Trump Mobile phone market — Active debate over whether the Trump Mobile T1 phone qualifies as "released" by June 30. blowingmoney initially flagged a misbonded "No" proposal, noting the site showed a waitlist. However, the phone now appears available for $499 on the official site. rex416. argues this is still effectively a pre-order, citing the official https://t.co/rd2sHLNy5I page stating an August launch and that phones haven't shipped yet. rex416. requested a market extension but ultimately dropped the dispute idea due to having no shares at stake.
📋 Clarifications
FIFA match stats (shots, etc.) not published on the official FIFA match page were previously believed to be P4, but a past dispute on this resolved in favor of allowing such proposals — as the FIFA live blog was ruled an official source. tenacious_mango_59265 confirmed this was news to them.
Is a product that's purchasable online but hasn't shipped yet actually "released," or does physical availability need to come first?
POLYMARKET DIGEST — 28 JUNE 2026
⚠️ Bugs & Issues
Multiple critical platform issues reported simultaneously:
• Login broken for several users for up to 4 days — no verification codes sent, sessions dropped mid-use
• Site inaccessible / loading indefinitely reported by multiple users; US app crashes on market click
• PnL chart severely broken — .hit9 reports Combo positions excluded from PnL calculation entirely, showing false profit for months, directly impacting risk decisions
• Missing funds after "Balance migrated" — itan6226 reports $31 combo position vanished from portfolio and balance after migration event
• Taker rebates not paid out for June 25–26; multiple users (alias1.possibly251, tomas3662, zoltar02) report missing payments; verylowsharpe is checking whether the rebate distributor wallet has changed
• Combo modal stuck in infinite "updating payout" loop (njokac)
• Daily Rewards counter decreasing after displaying a value (.chomeur)
• 403 errors from London API connections (1p3nny)
• Ghost fills reported again — famouspet describes order failure that simultaneously wiped resting bids; derek7049 asks if ghost fills have returned
• CSGO forfeit markets — juzi6665 flags that intentional forfeits result in 50/50 splits rather than refunds, enabling exploit
📋 Clarifications
All MSI 2026 "Make Finals" markets (T1, G2, Furia, Karmine Corp, BLG, Team Liquid, Lyon, Team Secret Whales, Top Esports, Deep Cross Gaming, Hanwha Life) had rules updated: "Finals" now explicitly refers only to the two teams reaching the Grand Finals, not any semifinal stage.
Taker rebate calculation clarification (from support, shared by nikitium): on taker BUY orders, the on-chain fee is charged in outcome shares, not USDC — raw fee summation overstates real USD fees. Multiply buy-side fees by fill price to get correct USD value.
Polymarket Perpetuals docs went live — blunkoed shared docs link. Current fees: makers receive 0.5bp rebate, takers pay 2bp. Tiered fee structure will be announced before transition.
With login broken, PnL completely unreliable, taker rebates missing, and ghost fills returning, how are traders supposed to make informed decisions on a platform you can't trust right now?
UMA DIGEST — 28 JUNE 2026
⚡ Disputes
Lebanon recognizes Israel markets — rex416. disputed one of two markets (June 30 and Dec 31 deadlines). Both have been extended. Risk Labs bot has up to 24h to dispute after extension. infinity_d clarified that an extended challenge period doesn't guarantee RL will dispute — it could resolve at any time. Poly team is also aware. Outcome still pending.
James Bond market — disputed by UMA bot after someone proposed based on an unannounced leak. im.the.wizard and others praised RL for catching it early.
TV show self-disputes — recurring pattern of self-disputes on TV show markets noted by laurleo. lexyuri attributed this to inaccurate TV captions. Another case emerged where a proposer bought ~1.8k shares at 1c, realized the proposal was wrong, and self-disputed.
Memphis Depay market — virtual.realization accidentally disputed a valid proposal, admitting they missed that the Polymarket web UI showed a different title ("Player G" vs "Depay Memphis"). Dispute resolved, both sides acknowledged the mistake amicably.
When a proposer buys thousands of shares cheap and then self-disputes when they realize they got the terms wrong, is that a feature or a flaw in the system?
POLYMARKET DIGEST — 27 JUNE 2026
⚠️ Bugs & Issues
buggy05646 posted an official status recap:
Fixed: frontend memory leak, logout issues, deposit wallet migration, geoblocking bug, World Cup goals market, taker rebates backpaid, June 20 liquidity rewards backpaid.
In progress: PnL/stale portfolio value (new indexing rolling out), "not enough balance" errors, order cancellation/open orders going stale, combo system issues, cancel-all-orders UI (ships tomorrow).
Coming up: Beacon deposit wallet release moved to Monday June 29, 8am ET. Rate limit changes TBD.
Additional active issues reported:
— PnL chart excludes Combo positions entirely (.hit9)
— Mutable market slugs in Gamma API breaking integrations — old slugs return 404 with no redirect or alias (cvijan_73915); elgato0615 notes this has been unfixed for weeks
— Safari unable to open profile URLs with wallet addresses (silviust7); multiple users affected
— Navigation bars missing for some users (phenomenal_quokka_24286)
— Positions not displaying (gernotti1710)
— Site performance: slow loading, freezing reported by multiple users
— Limit sell orders not working on WC markets (desanta)
— New market not appearing in UI after announcement (youngiliz)
— 0xdanzu confirmed a combo display bug fix was shipped (~15:11 UTC)
📋 Clarifications
"Will Trump say 'Mutilation'" market: Polymarket ruled that Trump's use of "Mutilization" at 22:07 counts as an intentional mispronunciation of "Mutilation" and qualifies per rules ("minor, unintentional mispronunciations qualify if context makes the intended word clear" — intentional variant also accepted). Order book was cleared at 7pm ET. Losing shares bought between 7–7:30pm ET will be refunded.
"Will Depay Memphis be top goalscorer at 2026 FIFA World Cup": resolves No due to market duplication. Losing shares held at clarification time will be refunded.
🔥 News & Announcements
0xdanzu confirmed no VPC setup exists on the platform. Combo market-making last-look access now requires >$2,500 notional volume; application form published at https://t.co/3h6Wm7Y8WY.
With so many ongoing bugs—PnL issues, stale orders, Safari crashes—do you think Polymarket's stability problems are starting to erode user trust, or is the compensation through refunds enough to keep traders engaged?
UMA DIGEST — 27 JUNE 2026
⚡ Disputes
"Worst-placed South American team" market: nik4456 initially argued Brazil/Argentina couldn't become worst-placed based on group tiebreaker rules, but wynn0747 pointed out this is an overall tournament prop — not group-based — meaning both teams could still be eliminated early and rank below teams with fewer points. nik4456 conceded the point, calling it a clear P4 proposal.
"Depay Memphis / Memphis Depay" duplicate market: laurleo reproposed "Depay Memphis No" arguing the name is misspelled and a player named "Depay Memphis" doesn't exist. virtual.realization disputed, claiming no strikes can be proposed as No yet — invoking the FIFA goalkeeper replacement rule (injured GKs can be substituted mid-tournament, theoretically allowing a "Depay Memphis" to appear as emergency GK). im.the.wizard called this argument "insane and antithetical to every early resolution." The market was quickly clarified by admins to close the duplicate, before laurleo could collect an extra $250. wynn0747 noted frustration that this was clarified instantly while the "worst placement" issue remained unresolved.
Belgium Group G winner — early resolution dispute: pumpkinseed14 flagged that the Belgium winning Group G market was proposed immediately after the Belgium–New Zealand match ended, while Egypt–Iran still had ~5 minutes remaining. Had Egypt scored, they would have won the group.
If a market resolves while a single match is still actively being played, should the resolution be automatically invalidated regardless of the final outcome?
POLYMARKET DIGEST — 26 JUNE 2026
⚠️ Bugs & Issues
Масштабный сбой платфор��ы 25 июня: множество пользователей сообщают о невозможности размещать и отменять ордера, ошибках входа (email и MetaMask), высоких задержках (p99 >2–3 сек у API-трейдеров, отдельные случаи до 20+ сек), зависании UI. kurwamach. подтвердил, что команда работала над исправлением. К вечеру ситуация частично стабилизировалась.
Отдельные активные проблемы:
— API возвращает 500 / DeadlineExceeded при размещении ордеров (несколько API-трейдеров паузировали ботов)
— Закрытые позиции отображают некорректные данные (0 PnL, неверные позиции)
— Комбо-рынки зависают на «updating payout», возвращают «quote unavailable»
— Лимитные награды исчезают при наличии ордеров в диапазоне (jimmerish. сообщает о проблеме на 12+ рынках)
— Gamma API /markets/keyset возвращает 500/503 при пагинации (gusttin. приложил детали)
— Пользователь imcrypto сообщает о ghost fill: ордер получил статус MATCHED, но подтверждение не пришло, активы не зачислены
— Кастомное время экспирации ордеров сломано в Firefox на Mac
— Награды ликвидности за 25 июня у ряда пользователей не отображаются
— Chrome временно блокировал размещение ордеров из-за Content Security Policy (позднее заработал)
🔥 News & Announcements
alfa4663 сообщил, что danzu подтвердил: кастомная цена резолюции через смарт-контракт (отмена правила 50/50) появится до августа. По словам alfa4663, это устранит проблему убытков при форфейтах на теннисных и киберспортивных рынках (команда потеряла ~$20k на Roland Garros).
0xdanzu подтвердил, что функция last look для ��омбо-рынков включается точечно командой для маркет-мейкеров с высоким объёмом и корректным поведением котирования. lochnload2718 публично потребовал раскрыть критерии отбора, указав, что предоставление привилегированного доступа «за кулисами» несправедливо.
📋 Clarifications
— Рынок «Bitmine sells any Ethereum in 2026?» — обновлены правила резолюции для уточнения.
— Рынок «Will another person advance to the second round of the next French presidential election?» — все позиции будут возвращены в полном объёме (рефанд).
Given the massive platform outage, API failures, and ghost fills affecting traders, do you think Polymarket should temporarily pause new market creation until core infrastructure is stabilized?
UMA DIGEST — 26 JUNE 2026
⚡ Disputes
CONMEBOL "Worst Placed Nation" markets — vlfph flagged that Argentina and Brazil markets resolved too early. jessicaonlychild confirmed: since no CONMEBOL team has been eliminated yet, Brazil/Argentina could still exit in R32 while the other 4 advance to R16 — making one of them the worst-placed. lonfus agreed after reviewing: "shoulda been p4." Extension/dispute requested for these proposals.
CONCACAF "Worst Placed Non-Host Nation" — Curaçao market — armanh01 requested proposal extension; jessicaonlychild argued Polymarket's tiebreak rule is wrong (ignores points, uses goals instead), but under Poly's own flawed logic the current resolution (Curaçao Yes) is technically correct. Haiti has more goals scored than Curaçao, triggering the 2nd tiebreak. jessicaonlychild: "Poly screwed up." Panama still has a match pending which could affect final standings.
Trump "Publicly Insults Someone" — June 25 — mak_disc questioned why the market resolved Yes. lonfus clarified Trump insulted Biden, resolution appears valid.
If these CONMEBOL and CONCACAF disputes prove the tiebreak rules were fundamentally flawed, should prediction markets establish independent rules committees before launch instead of relying on platform defaults?
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 (https://t.co/qxtRNxLlaN) 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 = https://t.co/qpgDnyxu09 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 https://t.co/XaqaTFIn9q.
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 — https://t.co/KaIVmmL9tV 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 — https://t.co/x30HDW7qkM 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?