Digest Polymarket & UMA Discord

POLYMARKET DIGEST — 31 OCTOBER 2026 🔥 News & Announcements Polymarket published a full post-mortem on the October 29 supply-chain attack. A third-party performance-monitoring script loaded on polymarket.com was compromised; the malicious replacement used active user sessions to sell positions and drain wallets during a short window. suhailkakar confirmed the following response actions: the compromised script was removed, all caches were cleared, trading and the relayer were paused then reopened, all active login sessions were reset, and third-party scripts are being redeployed with stronger CSP, explicit version pinning, and sandboxing. The case has been referred to law enforcement. Refunds total $3.9M: $2.7M for directly drained wallets and $1.2M in goodwill payments covering positions force-sold during the attack and losses incurred while trading was paused. suhailkakar stated that as of October 30, 95% of affected wallets have been refunded in full. No claim tickets are needed — eligible wallets were identified from on-chain and trading data. Users who believe their refund amount is incorrect can fill out this Google Form. bluelaminate noted that the incident could have been far worse: some compromised wallets had their positions market-sold by the script before it could execute withdrawals, allowing users to withdraw their remaining balance themselves. 45trinity praised the speed of the response, attributing improvements partly to the ICE investment, while also criticising the use of the word "goodwill" (arguing that in a regulated-exchange context this is a compliance obligation, not goodwill), the NDA reportedly required for refunds over $10k, and the lack of pre-existing guardrails against third-party script swaps. yasarhoca and david_82262 both called for mandatory 2FA on withdrawals, noting it would have significantly limited the damage. ⚠️ Bugs & Issues Several unrelated bugs are active: yannis4845 reports a translucent/invisible orderbook persisting even after clearing cache and cookies across browsers. guma777a reports that the live feed for Counter-Strike 2 games (showing map and kill data) has been missing for two days. shaz1996 reports that the Match Winner orderbook has disappeared across multiple cricket markets, with only fixed buy buttons remaining visible; other market orderbooks (Toss Winner, Top Batter) are unaffected. viniipaquete flagged that the bug preventing additional markets from loading is still unresolved. abtonmoy8 has been unable to withdraw funds or trade for over six weeks due to a "API key signer address mismatch" error and repeated withdrawal failures; the case was escalated to the backend team but remains unresolved. ice071059 reports that transferring funds between wallets causes inaccurate PnL calculations, a regression introduced by a recent PnL calculation update. becksinc flagged that orders in BTC 5-minute Up/Down markets are sometimes held for ~1 second rather than the documented 250 ms taker delay. david_82262 clarified that the taker delay was reduced from 250 ms to 150 ms on September 4. berth6833 reported an unusually high number of WebSocket timeouts on the evening of October 30. ⚡ Disputes sushi4uuu disputes the refund amount they received, stating that funds stolen from their account alone totalled approximately $30,000 USDT — not counting positions liquidated at fire-sale prices — yet Polymarket offered only $197 USDT. No response from Polymarket staff is recorded yet. dipsybitsy is still waiting for a separate misresolve refund on an NBA market, unrelated to the October 29 attack. Given the mix of praise for the fast response and criticism around the refund process, here's an engaging question: Should Polymarket have paused all withdrawals for 24-48 hours after the attack to verify refund amounts before releasing funds, or was the speed of getting money back to users more important than perfect accuracy?

UMA DIGEST — 31 OCTOBER 2026 ⚠️ Bugs & Issues A user (tt_tt00) reported an unexpected drop in their UMA stake balance. infinity_d explained that if a voter hasn't voted and revealed in over a year, they would have been slashed repeatedly every 2 days, which is likely the cause of the balance loss. 📋 Clarifications World's Largest Company (End of October) markets: jessicaonlychild flagged that several brackets of the "2nd largest company end of October 2026" market were proposed prematurely. The correct elimination logic: Apple (#1), Nvidia (#2), Microsoft (#3) — brackets below the current rank are eliminated, but top-ranked companies must remain open until all relevant exchanges close. Since October 31 falls on a Saturday, only the Tehran Stock Exchange trades, closing around 12:30 PM local time (~5 AM ET). jessicaonlychild and im.the.wizard confirmed proposals should not be made until ~5 AM ET. Three incorrect proposals were disputed; all other brackets were confirmed fine. jessicaonlychild reiterated her standing suggestion that Polymarket should standardize end-of-month resolution to 4 PM ET on the last NYSE trading day to avoid recurring confusion. Saudi Arabia vs. Yemen strike market (September 26): A dispute over whether Saudi forces carried out a qualifying military action on Sep 26 was resolved via P1 clarification. The official clarification text stated: "The totality of information available from this market's resolution sources does not attribute any qualifying military action to the armed forces of Saudi Arabia on September 26, 2026." raskell1 noted this is consistent with a prior precedent from September 20. ⚡ Disputes Israel election result markets: jenia9419 proposed resolution on Israeli election markets, citing 100% vote counts, coalition-building coverage in newspapers, and Kalshi having already resolved the equivalent market. armanh01 and others filed P4 (ambiguity) disputes, arguing that statements by Netanyahu regarding an investigation into alleged irregularities in Arab villages created sufficient ambiguity to require waiting for official certified results (expected November 4). laurleo and jenia9419 argued the annulment scenario is a mathematical impossibility and that P4 is being abused — laurleo stated: "Rules need to make it explicitly fine for mathematical impossibility to be proposed across the board because until then the scams will continue." The dispute went P4, locking funds until at least November 4. jenia9419 expressed strong frustration, calling the outcome a scam given Kalshi's resolution and the absence of any formal investigation. armanh01 maintained the precedent of waiting for official results whenever any ambiguity exists. Systemic concern — P4 abuse: Several users including laurleo and abhiz69 raised broader concerns about coordinated P4 filings using suspected alt accounts to push markets to ambiguity even when outcomes are practically certain. laurleo called for rule changes to explicitly allow resolution when recount or annulment is a mathematical impossibility, stating the issue was not addressed properly in a prior Bulgaria case due to reluctance to challenge certain influential voters. Should prediction markets allow resolution when an outcome is mathematically impossible to reverse, or does requiring official certification always outweigh logical certainty?

UMA DIGEST — 30 OCTOBER 2026 ⚡ Disputes Anthropic training pause market (Polymarket): wang02272 argues the market should resolve NO, contending that Anthropic's SEC filing explicitly uses the word "delay" — not "pause" — for the recent pre-training event, and that Anthropic itself distinguishes the two terms. The Reuters headline calling it a "training pause" is described as a journalist's interpretation. Wang also notes the previously disclosed RL training pause predates market creation and thus cannot qualify. Drew Jenner / Clarence mayoral election: eip15942 raised a concern that Jenner also needs to be elected as city councillor to legally assume the mayoralty. The majority view (enormouz, im.the.wizard, jamestalaricof, ghostmbao) is that the market rules only reference "the result of the election," with no requirement to officially assume office, and that credible reporting plus the Tasmanian Electoral Commission declare Jenner elected. im.the.wizard cited France mayors as precedent that swearing-in is not required unless the rules explicitly say "officially assumes." Consensus leans toward resolving YES. Israeli Knesset election markets: An active dispute is ongoing over whether to settle Israeli election markets now or wait for official certification. armanh01 argues the ambiguity clause is satisfied because the prime minister has alleged voter fraud and arrests have been made, citing precedent where a loser merely contesting results triggered P4. jenia9419 counters that 100% of votes are now officially counted, two of the parties proposed are nowhere near the top 10, and credible reporting is sufficient for resolution. lonfus notes most results have no real ambiguity. jamestalaricof points out Kalshi has also not settled these markets. The dispute remains unresolved, with armanh01 holding a disputed position worth ~$1,500. Rex416 / Raskell conflict: A personal dispute erupted between rex416. and raskell1 over proposals for military-action markets. raskell1 accuses rex416. of extortion, deliberately leaving markets unresolved for 40 days, and claims rex416. is banned from the Polymarket Discord. rex416. denies bad faith and says raskell previously told him to just dispute rather than warn. armanh01 called the behaviour a pattern. No resolution reached. 📋 Clarifications Market with incorrect player surname: jarmax asked about markets where a player is identified by a wrong surname. mebeim and laurleo explained: if it is clear which player is meant, it is generally acceptable; however, if another real player shares the typoed name and could plausibly be the subject, the market would likely resolve NO without an official clarification from the Polymarket market team. Crypto hack market (>$100M): alexchunus flagged the Bybit and Binance hacks, with Tether freezing ~$970M in USDT, and suggested proposing the relevant Polymarket market. fernando5495 noted it should appear on the Rekt leaderboard or have clear consensus. im.the.wizard instructed not to propose it for now. ⚠️ Bugs & Issues Several NBA prop markets linked in proposals return "Page not found" on the Polymarket UI (raised by what_the_ginger). It is unclear whether these are duplicates or archived markets. Is the Anthropic market's distinction between "delay" and "pause" a linguistic gotcha or a genuine material difference that should affect the outcome?

POLYMARKET DIGEST — 29 OCTOBER 2026 🔥 News & Announcements Beta WebSocket streams launched: habitual_revers announced a beta rewrite of the WebSocket subscription streams at new endpoints: wss://ws-subscriptions-clob.polymarket.com/beta/ws/market wss://ws-subscriptions-clob.polymarket.com/beta/ws/user Same protocol/payloads as production, but reportedly more stable with latency improvements. Current beta limits are 10 connections per channel per IP. Multiple devs (blunkoed, up0rabn1k) confirmed rare disconnects and reduced "slow consumer" errors compared to the old endpoint. habitual_revers noted the beta will be monitored for 1–2 weeks before a production rollout decision. CLOB latency & fee holiday side effects: Users are reporting 2000ms+ match delays and cancel timeouts. purpletyoma noted the likely main trigger is order spam from the ongoing zero-fee promo, and expects improvement after the promo ends on November 1. A separate matching engine rewrite in Rust is in progress but is independent of the WS beta. mrbobbybeans flagged that the fee holiday does not count toward weighted volume (wV) for rebate tier calculations, causing tier decay for active traders — sports markets are noted as permanently excluded from proportional wV. 📋 Clarifications Vermont elections — Constitutional process added to rules: Polymarket updated bulletin board rules for all 2026 Vermont Governor and Lieutenant Governor markets to clarify that resolution includes the Constitutional process whereby the State Legislature elects the winner if no candidate secures a majority. "Will Trump say 'Two Percent'" market: Polymarket noted awareness of a dispute on this market. A clarification was to be issued (or not) at 6:00 PM ET on October 28. The order book was cleared at that time regardless of outcome. NuScale & CoreWeave bankruptcy markets: Rules for "Will NuScale announce bankruptcy by December 31, 2027?" and "Will CoreWeave announce bankruptcy by December 31, 2028?" were updated for clarity. ⚠️ Bugs & Issues LoL Worlds market wrong date: jayson0 reported that the MKoi vs T1 market displayed the match date as October 29 when the match was actually on October 28. "Address in closed only mode" error: laucyph3r and guizao2439 reported their addresses entered a restricted "closed only mode" as of 02:30 UTC on October 28, blocking order placement. No resolution was confirmed during the period. Cancel timeouts: Multiple users (berth6833, pumpty_dumpty) reported order cancellations consistently timing out or being delayed by ~1 second. pumpty_dumpty flagged that some orders could not be cancelled during a CLOB maintenance window and were picked off as a result; skulldoom97 asked for logs to investigate. Reward bait-and-switch: viniipaquete complained that market rewards were changed to $1 after being set higher, effectively baiting liquidity providers. Will the Rust matching engine rewrite successfully resolve the 2000ms+ delays, or is order spam from the fee holiday the real bottleneck?

UMA DIGEST — 29 OCTOBER 2026 🔥 News & Announcements UMA's dispute bot, which previously auto-disputed early proposals, has reportedly been discontinued. alexchunus noted that extending liveness is now the preferred approach — effectively "disputing for free" without spending on losing disputes. ⚠️ Bugs & Issues joe_jureidini reported an unknown error when trying to commit votes. infinity_d directed them to check their support ticket. baltazar.f reported that their support ticket thread (ticket-2220) appears to have disappeared from Discord, though the ticket limit message suggests it is still open on the backend. infinity_d provided a direct link to the thread. 📋 Clarifications A debate emerged around the P4 timing rule (proposals must wait for HLTV listing or 2 hours after event conclusion). stradiveri and alexchunus clarified that for map-specific markets (Map 1, Map 2, etc.), the 2-hour window starts after that map concludes, not after the full series ends — a position attributed to dmitry's earlier explanation. This interpretation has always been how such markets are proposed. ⚡ Disputes CS:GO/HLTV P4 Bond Loss: geoffreywalker30_91195 lost 8 bonds after being voted P4 for proposing results inside the 2-hour HLTV window on a match that HLTV never listed (Dark Moon, 14 Sep). He argues that other proposers did the same thing on similar unlisted matches at least 10 times in the prior month without being disputed, making enforcement inconsistent. stradiveri countered that the rule is clear regardless of selective enforcement, and that anyone disputing those earlier proposals would have also won P4 votes. A forum post by geoffreywalker30_91195 is pending moderator review. Community consensus is that his case is unlikely to succeed. Keinan Davis "1+ Shots on Target" market: ostrich_knight flagged that the market resolved No but should have resolved Yes, citing Serie A official match stats. The request was submitted for review. US–Iran / Israel–Iran ceasefire markets: ashley51782 posted links to two ceasefire continuation markets without further explanation; jarmax confirmed action was taken ("Done"). Is the shift from auto-disputing to extending liveness actually saving UMA money, or does it just move the cost and risk onto proposers who extend claims too early?

POLYMARKET DIGEST — 28 OCTOBER 2026 🔥 News & Announcements Polymarket Protocol V2 migration is approaching. Canary markets run through October 30, with new markets tentatively switching to V2 on November 2. The migration introduces a unified exchange contract across market types and a new Data API v2 backed by an on-chain indexer with cursor pagination. A migration guide is available at poly.market/v2-migration. Users trading via the website need no technical changes; the steps are for SDK/API/smart contract integrators. kartojal clarified that the /activity RTDS endpoint does not provide V2 markets and should not be used by integrators. The November 2 date remains tentative — gasuajex noted an update is coming soon, meaning integrators may need to support both versions simultaneously for a period. habitual_revers confirmed that a major infrastructure rewrite (Rust rewrite / CLOB overhaul) is still in progress, targeting completion of internal builds by end of year, with actual release depending on traffic and market conditions. Users expressed concern this means roughly 3 more months of current degraded performance. Polymarket is exploring daily wind markets — ak504111 asked the community which cities would be of interest. Suggestions focused on coastal cities with notable wind phenomena (Mistral, Bora, Chinook, Santa Ana, etc.). ⚠️ Bugs & Issues Order cancellation queue overload is an ongoing issue. laucyph3r noted cancellations can take anywhere from 10 ms to several seconds depending on matching engine load, and the queue has been "out of control for days." berth6833 reported cancel requests reaching Cloudflare Dublin in ~3 ms but then timing out despite being well under rate limits. habitual_revers disclosed a network routing bug — a Cloudflare/CloudFront IP resolution issue was causing incorrect network path routing. A fix was pushed; users were asked to confirm if the issue persists. The dual CDN layer is described as temporary during ongoing infrastructure work. High CLOB match latencies were reported throughout the day, with jungle_jo noting match times climbing all week. Market data feed latencies of P50 200 ms / P90 1.5 s were reported from AWS eu-west-1. "Show more markets" button on the homepage disappears ~2 seconds after page load (reported by laccs). Stuck phantom orders on metal markets — floaty_boi reported orders appearing on the order book that cannot actually be taken. 📋 Clarifications hans32312 explained UMA proposal mechanics for temperature markets: the bond is $500 (fixed), reward is $0.60 per correct proposal, and the bond is lost on incorrect proposals. Some market types require higher bonds (e.g., $750 or $25,000 for 2028 presidential nomination markets). Standard resolution time for temperature markets is ~15 minutes, though proposals can be extended automatically. hans32312 noted he only proposes temperature markets where he is confident in accuracy, and also trades on Polymarket and Kalshi in parallel. Given the infrastructure struggles, network issues, and migration challenges, do you think Polymarket can actually complete the V2 migration smoothly on November 2 or will they need to delay again?

UMA DIGEST — 28 OCTOBER 2026 🔥 News & Announcements The ITF updated the Brengle vs. Nilsson result to 2-1 (previously shown as 2-0 on the ITF scoreboard at the time of proposal). A significant price drop after the proposal raised concerns about insider knowledge of the ongoing third set. A mod (infinity_d) placed the market on hold pending review. Separately, im.the.wizard flagged some disputers as potentially from OFAC-sanctioned countries. ⚠️ Bugs & Issues An MLS SOT discrepancy was flagged for the SDvsSEA match (10-24-2026): im.the.wizard cited the MLS official site showing Amahl Pellegrino with 1 SOT, while the UMA feed and tenacious_mango_59265 showed 0. The market had already settled before the discrepancy was fully investigated; infinity_d stated the team was "taking a closer look," with no resolution yet. 📋 Clarifications Visa Earnings Market: fernando5495 disputed a proposal over whether ~9% or the more precise 9.5% (possibly 9.47%) figure should be used. Both parties agreed the market rules' "most numerically precise version" clause applies; aboss suggested the actual figure may be 9.47%. Quebec Election Proposals: PLQ launched a legal challenge to the judicial recount following the Oct 21–22 results. gum5683 argued the challenge window was 4 days post-election and results are final, but laurleo expressed uncertainty given the ongoing legal proceedings. Sabail Soccer Proposals: exquisite_wolf_79651 flagged multiple Sabail match proposals as potentially P4, as proposals were made at the end of regular time while the game went to extra time. laurleo suggested letting it pass if the dispute window had already closed; alexchunus noted an ~80% confidence threshold is needed for a dispute to be +EV. ⚡ Disputes Bulgaria Presidential Election Margin of Victory: laurleo (proposer) proposed multiple margin-of-victory brackets before official CEC certification, invoking the "overwhelming consensus of credible reporting" clause. 7h0nk3r (disputer) argued proposals are only valid after official certification. im.the.wizard and rex416 noted prior UMA votes have unanimously gone P4 in pre-certification cases, treating the consensus clause as a fallback for when certification never occurs — not an alternative to it. mebeim countered that current rules are written with consensus as an alternative, not a fallback, and called for Polymarket to clarify. Bulgaria's CEC officially certified results later the same day (Oct 27, ~18:31 UTC), confirming a ~3% margin (<10% bracket). The mathematically impossible 20–30% and 30–40% No brackets were also disputed. The dispute remained unresolved pending UMA vote. Participants across both sides called on Polymarket (Bel/Jessica) to issue binding guidance, as significant disagreement persists on whether undisputed past proposals constitute precedent. Brengle vs. Nilsson Set Handicap: joes49572 argued that a result revision made hours after the fact should not count toward the set handicap market outcome. ITF showed Brengle winning 2-1, but some users noted ambiguity in how ITF displayed the result, and the timing of the update remained contested. If the ITF can silently update match results hours after the fact, should markets settle on the scoreboard snapshot at proposal time or the "official" result whenever it's corrected?

POLYMARKET DIGEST — 27 OCTOBER 2026 ⚠️ Bugs & Issues API/CLOB latency crisis (ongoing): Order placement and cancellation latency has been consistently above 500ms, with some users reporting over 1000ms from Dublin. The issue has worsened since an October 21 infrastructure incident. Multiple market makers report the situation is fatal to FAK orders and unpredictable tail latency makes market making a "lottery." vader1208 confirmed their team has halted trading entirely, stating it is "just impossible" to operate. piercethecircle noted other large accounts have also stopped trading. skulldoom97 (Polymarket dev) provided an official update outlining three mitigation approaches: 1. WebSocket improvements (coming soon, but won't fix core CLOB slowness) 2. Further DB tuning (limited options without architectural changes) 3. Rate limit adjustments as a last resort, with prior notice given skulldoom97 attributed the root cause to increased load from the fee holiday and sports season returning, and confirmed lag is especially severe on high-activity markets (e.g. BTC 5m). A new exchange is in development with much higher throughput; it will roll out in stages (sandbox → beta → broader release). Formal announcements are expected within 1–2 weeks. vader1208 requested that current maker-tier rate limits be preserved in the interim. LP rewards accrual interval changed: muzzammil2 reported the rewards page switched from showing accumulation every 1 minute to every 5 minutes, asking whether this was intentional. Typhoon market inconsistent resolution sources: brassbonanza4655 flagged that in the new "How strong will In-fa be?" market, the "Violent" outcome uses JMA as the resolution source while "Super Typhoon" uses JWTC — two agencies that measure wind speed very differently. This could lead to contradictory resolutions and may be a market setup bug. RTDS v2 activity topic not migrated: pinner reported not receiving v2 trades from the RTDS activity topic. kartojal (dev) confirmed the activity topic has not yet been migrated to v2 and is investigating. 📋 Clarifications NBA Kings market possible misresolution: dipsybitsy and crypt0blonde raised a case where a Kings NBA quarter-spread market (Kings 3Q -1.5) appears to have been resolved incorrectly via UMA, with the score feed corrected after the proposal was submitted and the dispute window too short for anyone to react. crypt0blonde argued Polymarket should issue a refund as platform responsibility, regardless of UMA's role. If latency keeps market makers offline, does Polymarket risk losing liquidity depth permanently before the new exchange launches?

UMA DIGEST — 27 OCTOBER 2026 🔥 News & Announcements A massive wave of disputes hit Bolivian soccer markets. A proposer submitted results for multiple matches (including "potos"-tagged markets) within one hour of game end instead of the required two hours, and the resolution source had not yet updated. rex416. filed disputes backed by double archives (Wayback Machine + archive.is), making the "cached page" defense unavailable. im.the.wizard noted the proposer is already down roughly $34k with an additional ~$7.5k in pending golf losses. All exact-score proposals were disputed; the proposer continued submitting new proposals even after disputes were filed. Earlier in the day, two Indonesian football markets (idn1-bpi-mak-2026-10-26 and idn1-ps-mau-2026-10-26) were also flagged as early proposals, with the resolution source showing both matches still live at proposal time. ⚠️ Bugs & Issues The UMA bot for proposal requests was reported not working by elie220 on the morning of Oct 26. infinity_d confirmed it was resumed and fixed later that day. NBA stats inconsistency: im.the.wizard flagged that official NBA stats briefly showed James Harden with 22 three-pointers before correcting to 19. mawyoo confirmed other sites also adjusted. No dispute needed. 📋 Clarifications A market asking whether Democratic House incumbents lost primaries (capped at September) was proposed resolved "No" on the basis that reaching 13 losses is mathematically impossible — 7 lost votes, 4 filed then left the race, and the Louisiana special election is a new election outside the market scope. justinnocent_ stated the proposal was vetted with multiple proposers and confirmed as good by Cruz. armanh01 and laurleo agreed it appears fine. ⚡ Disputes A heated exchange broke out between exquisite_wolf_79651 and alexchunus, with alexchunus accusing exquisite_wolf_79651 of "intentionally and knowingly misresolving oracle disputes" and front-running, while exquisite_wolf_79651 called alexchunus a "convicted scammer." exquisite_wolf_79651 suggested a video meeting be arranged with alexchunus (Penguin), joes49572 (0xWater), jason.k7 (Jason), and nickc01457 (NickC), implying multiple accounts belong to the same person. abhiz69 noted the wallet in question has been doing the same thing with multiple wallets and was previously removed by UMA. No resolution to this dispute was reached. When resolvers have a history of multi-wallet tactics and accusations of intentional misresolution fly, at what point should UMA consider stricter identity verification to maintain oracle integrity?

POLYMARKET DIGEST — 26 OCTOBER 2026 ⚠️ Bugs & Issues Multiple traders reported significant API and infrastructure degradation starting around 21:00 UTC on October 25. 001_raghav noted POST /order latency jumping from ~220 ms to 500–1,500 ms since 12:00 UTC on Oct 25, potentially linked to the Oct 22 CLOB update. berabuilder and berth6833 confirmed p99 cancel latency exceeding 2 seconds on esports markets, with WebSocket delays also severely impacted. r33nter and pool6225 reported order kill confirmations taking 600 ms to 10+ seconds. The issues appear to be known but unresolved. Additionally, pog_is_pog flagged a PnL discrepancy — their balance increased by ~$300 with no trades, redemptions, or deposits. satatardy noted PnL display in the UI has been broken for a long time with no fix. bluvv_.xo flagged a potential rounding error in weather market rules: a reading of 16.5°C rounds to 16°C under half-to-even rounding, not 17°C as the rules appear to assume. hellbot632 reported the UI cracking with more than 2,000–3,000 resting maker orders. crypto_hamster raised a detailed concern about the taker delay mechanism on BTC 5-minute markets: held orders are released inconsistently (100 ms to 1+ seconds rather than a flat 150 ms), cancellation of held orders via precomputed order ID is refused, and minimum expiration is enforced at 180 seconds. One wallet (0xcd30) appears first in the post-hold queue ~1,500 times in September, 4–7 ms after a trade clears, raising questions about queue ordering (submit time vs. other criteria). 📋 Clarifications Cape Town October 18 temperature markets have been updated. Due to a National Weather Service outage, all Cape Town high-temperature markets (9°C or below through 19°C or higher) will now resolve using the Weather Underground Daily Observations Table. The previously identified erroneous 19°C reading (originating from another airport and incorrectly assigned to FACT) remains excluded from resolution across all markets. The consensus view, confirmed by hans32312, is that the actual peak temperature was 16°C and markets should resolve accordingly. ak504111 confirmed the clarification was posted, and hans32312 subsequently submitted the resolution proposal. velvet_soulb raised several open questions about the Protocol V2 migration (scheduled for Nov 2 for net-new markets), including: whether recurring BTC/ETH/SOL/XRP 5-minute Up/Down markets will launch as V2 from day one, slug naming conventions, auto-redemption behavior for deposit wallets, whether fee schedules and the 150 ms taker delay carry over, and whether a discovery endpoint will exist for upcoming recurring markets. 2773380 echoed broader frustration about insufficient advance communication around deprecations, noting that real money is at stake. Given the multiple infrastructure issues and unresolved bugs, do you think Polymarket should pause new market launches until core API and UI performance is stabilized?

UMA DIGEST — 26 OCTOBER 2026 🔥 News & Announcements Brazil's presidential runoff was called by the superior electoral court, with Flávio Bolsonaro refusing to concede and demanding annulment. Brazil election markets on Polymarket were proposed by non-whitelisted users and settled without dispute. armanh01 noted the market became resolvable when the electoral court made the official call. 7h0nk3r requested that extensions on the Trump Michigan rally speech brackets be undone, noting a typo on the page (October 26 vs October 25) caused extensions, while several brackets — including 3 Yes brackets — had already settled. He also argued that the "No Qualifying Event" bracket should now settle No since it cannot logically coexist with settled Yes brackets. ⚠️ Bugs & Issues im.the.wizard flagged a misresolution on the Kings 3rd quarter lines market, which kept flipping between 29-29 and 29-31. The spread market was extended and then unexpectedly settled, while the total was disputed. Users were directed to contact Polymarket directly for a refund on the incorrectly settled spread. 📋 Clarifications Archived Brazilian LGBT markets: Three Polymarket markets on LGBT federal deputies in the 2026 Brazilian elections were found to be archived yet proposed. 7h0nk3r clarified that archived markets can still be proposed if the outcome is determinable from the ancillary data. laurleo confirmed proposals were correct per the resolution source. The markets were likely archived due to their sensitive subject matter. One proposer self-disputed after realizing uncertainty in one bracket, saving ~$500. Israel/Iran ceasefire markets: A dispute arose over early proposals on ceasefire markets following the Sirik explosion. armanh01 and 7h0nk3r argued markets should stay open given the unclear attribution of the strike and the active, escalating conflict. A US/Iran clarification confirmed that all related markets should remain open for 3 days from the incident. armanh01 noted that UMA Rocks voted against this and were slashed as a result — notably the first round in which Rocks chose not to publicly post their vote. Color vs. Ex-Zero esports markets: nopsuke raised a concern that several Color match markets were proposed before HLTV (the designated resolution source) had confirmed the walkover result. The debate centered on whether the 2-hour rule applies from the moment the forfeit was declared by the TO or from the scheduled match start time. alexchunus noted the rules require only 2 hours from the event's conclusion, and since the walkover was declared 7+ hours before proposals, most participants leaned toward the proposals being valid. nopsuke maintained that the resolution source should have been waited on; HLTV did eventually update confirming the result. ⚡ Disputes im.the.wizard vs. committee member (corruption allegation): im.the.wizard publicly accused a committee member (not named but tagged) of corruption and manipulation, stating: "I'm glad you are changing your process to not post anymore, but I hope you can recognize it's still a large problem to have a fraudster and manipulator on the committee." No formal response was recorded in the channel. When resolution sources like HLTV conflict with market timing rules, should the community prioritize waiting for official confirmation or stick strictly to the 2-hour window from event conclusion?

POLYMARKET DIGEST — 25 OCTOBER 2026 ⚠️ Bugs & Issues Significant API and latency issues were reported throughout the day. Starting around 14:00 UTC, multiple users reported extremely high place order latencies — hft_pro noted P50s above 500ms on sports markets, while phoenyx69 reported P50 of 300ms+ on 5-minute crypto markets. laucyph3r described it as "a massacre" on 5m crypto latency. Later, exuberant_lynx_38171 reported Taker P50 of 550ms and P90 as high as 1700ms. skulldoom97 confirmed the team was investigating. Latencies reportedly improved somewhat around 15:52 UTC (hft_pro noted P50 returning to ~35–40ms on sports), but issues persisted for crypto. Additionally, berth6833 reported recurring HTTP 500 errors ("order queue full for maker") and "Context deadline exceeded" errors, raising frustration about wallet queue limits despite respecting rate limits. pepesong reported random heartbeat errors, and later noted that Redeem is failing. berth6833 also flagged that user fill events are being sent with significant delays again. 📋 Clarifications The Shenzhen lowest temperature market for October 21 remains unresolved. hans32312 (VIP) noted it should be resolved soon. Regarding combo last look access for v2 migration, quantwifbag reported filling out the access form and meeting volume requirements but receiving no response, and asked whether the team reaches out via email/telegram or enables it automatically — no answer was provided yet. How much latency is too much before you'd consider moving your trading volume to another platform?

UMA DIGEST — 25 OCTOBER 2026 ⚡ Disputes Israel–Iran Strike Market (Sirik explosions): A dispute is active over whether the Sirik explosions qualify as an Israeli strike. jenia9419 proposed YES resolution was pushed through, arguing there were zero credible reports implicating Israel and that Polymarket's "Too Early" clarification on the US–Iran ceasefire market is irrelevant here. gum5683 disputed, arguing there was a non-zero chance Israel was responsible and that the "Too Early" clarification for the US–Iran market cannot be applied to the Israel–Iran market, where YES remains appropriate. armanh01 noted that Polymarket has accepted the Sirik strike's attribution as unclear, and criticized the proposal for potentially scamming NO holders in a high-volume market. The dispute appears likely to resolve in jenia9419's favor as gum5683 missed the window to dispute a second proposal while sleeping. Ukraine targeting Moscow on October 21: A NO proposal was put forward on the market asking whether Ukraine targeted Moscow on October 21. tranquil_dolphin_46729_72282 contested this, citing AP, TASS, and Kyiv Post all reporting that 630 drones were directed toward the Russian capital from 20:30 on October 21. The NO side argues that the drones near the city were only intercepted after midnight on October 22. tranquil_dolphin_46729_72282 sought others to dispute but admitted having only $300 in their wallet — insufficient to fund a dispute — and was largely dismissed after it emerged they were using a purchased Discord account. The market resolved NO without being disputed. András Schäfer 1+ Shots market: ostrich_knight flagged that a market was proposed NO despite ESPN, Flashscore, and Sofascore all recording a shot for András Schäfer in the Augsburg vs Union Berlin match. ⚠️ Bugs & Issues NBA score data was reported as unreliable, with scores randomly changing back and forth across sources including the official NBA website. whoooo8888 noted the NBA site was in a particularly bad state. Separately, bromley86 flagged that the Polymarket resolution UI is showing markets as finally resolved when they are still in review, and even appears to allow share purchases after a final outcome is displayed — confirmed as a cache/display issue. When attribution is genuinely unclear but market volume is high, should disputes prioritize protecting majority holders or setting strict evidentiary standards?

POLYMARKET DIGEST — 24 OCTOBER 2026 📋 Clarifications NATO x Russia military clash markets: Polymarket issued a long-awaited clarification on the "NATO x Russia military clash" series (Oct 31, Nov 15, Nov 30, Dec 31). The October 17 incident — two Romanian F-16s shooting down two Geran-family drones over Romania's territorial waters — does not qualify as a NATO-Russia military clash. Per the rules, interceptions of munitions targeting a third party (in this case a civilian/commercial vessel, not Romania or its forces) do not count, even if the vessel was within Romanian territorial waters. Order books were cleared at 4:00 PM ET on October 23. Russia-Ukraine diplomatic meeting markets: All "Will Russia and Ukraine hold any diplomatic meeting by…" markets (Oct 31, Nov 15, Nov 30, Dec 31) received a bulletin: the October 23 meeting between Ukrainian Ombudsman Dmytro Lubinets and Russian Human Rights Commissioner Yana Lantratova in Belarus qualifies as a diplomatic meeting under the rules. These markets are expected to resolve YES. US x Iran ceasefire market: The "ceasefire continues through October 22?" market remains open due to conflicting sourcing around reported October 21 explosions in Sirik. The market will stay open until October 24, 2026, 11:59 PM Iran Standard Time for the 3-day attribution window to expire. Landskrona BoIS vs. IK Oddevold corners markets: All corners-related markets for this Superettan fixture (Total Odd/Even, Home O/U 4.5, Home O/U 5.5, Total O/U 7.5, Total O/U 8.5) will resolve using the official Superettan governing body website as the primary source. 2026 Spanish general election markets: Language on both "Will PSOE win the most seats?" and "Will PP win the most seats?" markets has been updated for clarity. ⚠️ Bugs & Issues Severe CLOB latency degradation: Multiple users reported a significant and ongoing spike in taker order latency over at least two days. Typical figures cited: median around 544–623ms, P90 at 1,200–1,400ms, P99 reaching 3+ seconds — compared to a median of ~297–300ms and P90 well under 1s the previous week. habitual_revers confirmed the team is investigating the edge networking stack. papakarlo8, purpletyoma, dust7829, and exuberant_lynx_38171 all independently confirmed the issue persisting from EU-west-1 and other regions. FAK order status unknown after taker delay: the_purple_person flagged that Fill-and-Kill (FAK) orders in markets with taker delay (e.g. sports) leave no order event and return null from GET /data/order, making it impossible to reliably determine whether the order filled without polling with an arbitrary timeout. Self-trade prevention undocumented for predictions: dean_weez asked how self-trading is handled for prediction markets (as opposed to perps). hft_pro noted from observation that the taker order is not matched against the user's own maker order, and the maker order is ignored rather than cancelled — but this behavior is not officially documented. V2 trades missing from RTDS stream: pinner reported that the RTDS activity/trades stream on wss://ws-live-data.polymarket.com appears to contain no Protocol V2 trades. Out of ~3.7 million RTDS trade records from October 23, none matched 99 V2 transaction hashes returned by the Data API. It is unclear whether V2 trades appear on a different subscription or are simply not yet included. Some RTDS payloads also have a populated asset field but an empty conditionId, which is unresolved. gasuajex confirmed investigating and testing. Unrealized PnL non-zero despite closed positions: up0rabn1k reported the user-stats API returning a non-zero unrealized_pnl (-35.48) despite all positions being closed. Cause remains unknown. WebSocket 1013 "slow consumer" errors: up0rabn1k flagged persistent 1013 slow consumer: send buffer full disconnections from Polymarket's WebSocket, reproducible across Java, Go, Python, and C clients, suggesting a server-side issue. Which resolution criteria surprises you more — that drone interceptions don't count as NATO-Russia clashes, or that a human rights meeting qualifies as diplomatic engagement?

UMA DIGEST — 24 OCTOBER 2026 🔥 News & Announcements A massive MLB proposal incident occurred when approximately 400 proposals were submitted while a game was still in progress following a call overturning. Most game-related proposals (excluding player props and overs) were disputed as P4. The UMA settlement bot processed and settled nearly all of them within ~15 minutes because at settle time the game was officially over, leaving disputers very little time to act. im.the.wizard confirmed being the proposer and acknowledged the loss as a "quarterly mistake." Russia-Ukraine diplomatic meeting markets were extended well beyond the standard challenge period (~8 hours), frustrating many traders with large positions. infinity_d confirmed that extensions are applied by bot or manually, and that removing them is always manual. The markets were eventually held pending a Polymarket clarification; armanh01 noted the clarification came through confirming the meeting counts as YES. tsybka criticized the lack of communication during the ~8-hour wait, and armanh01 agreed that pending clarifications should be disclosed to all traders equally rather than kept silent. ⚠️ Bugs & Issues Two Sao Paulo temperature dispute markets ("16°C" and "22°C" on Oct 19) showed "unable to settle" in the Oracle UI while all other similar disputes resolved normally. alexchunus attributed this to the UMA settlement bot experiencing lag due to high proposal volume over the weekend and advised waiting until morning. 📋 Clarifications Superettan corners dispute (IK Oddevold vs Landskrona Bois): ghostmbao and eip15942 argued that the official superettan.se source recorded only 4-2 corners due to a tagging flaw — corner kicks tagged as "goal" or "shot" are not counted in the stats widget. Six major tracking sites (FotMob, Sofascore, Flashscore, etc.) all show 7-2 (9 total corners). eip15942 noted the official source contradicts itself, showing 0 second-half corners for Landskrona despite their own match events feed and video showing a corner-kick equalizer at 51'. alexchunus argued against the "6 corners + 3 direct kicks from corner" interpretation. Russia-Ukraine meeting market inconsistency: .rustyn raised a question about why a previous market (created Aug 19, meeting on Aug 21) resolved NO while the current market resolves YES under apparently the same conditions. tsybka and raskell1 clarified that the previous market always resolved off the Lubinets–Lantratova meeting, and that the prior NO resolution was due to a timing issue — the referenced meeting predated that market's creation window. MLB spread proposals mid-game: laurleo and im.the.wizard discussed the edge cases around proposing spreads before a game ends. im.the.wizard noted that once 5 innings are complete, a game is official (including playoffs), and that spreads can technically be proposed once mathematically determined — e.g., a home team losing by 5+ cannot cover -4.5. laurleo confirmed he will vote P4 on the Brewers -4.5 dispute as nonsense, while cautioning proposers to be certain before attempting such proposals due to their complexity. ⚡ Disputes P4 dispute involving im.the.wizard (esports/sports market): A major ongoing dispute centers on whether a market was proposed before the resolution source updated. im.the.wizard presented an archive snapshot and a video recorded in a fresh browser session showing the score was not yet published at proposal time. exquisite_wolf_79651 (cruz), a uma.rocks voting committee member, argued the archive may be inconclusive due to potential CDN caching and that the site was known to serve stale copies. im.the.wizard, abhiz69, joes49572, and alexchunus all accused exquisite_wolf_79651 of voting based on a personal grudge rather than evidence, pointing to his prior voting history where he accepted P4 on far weaker soccer disputes. abhiz69 stated: "Cruz, everyone knows it's because of your personal beef — everyone can see your past votes." exquisite_wolf_79651 maintained his reasoning was based purely on the evidence posted in dispute threads. 7h0nk3r stated he will vote P4 (supporting wizard), arguing the archive should take precedence over the video given trust concerns, but noted CDN caching is a real possibility. The dispute remains active and heading to a community vote. Why should markets with ambiguous resolution sources allow proposals mid-game when the outcome isn't mathematically certain yet?

POLYMARKET DIGEST — 23 OCTOBER 2026 🔥 News & Announcements Istanbul Temperature Markets – Dispute & Resolution A large group of Istanbul temperature markets (highest and lowest temperature brackets for Oct 20–22) faced disputes after Weather Underground returned "The location supplied is invalid" for Istanbul Airport (LTFM). Per market rules, markets with no data by 11:59 PM ET the day following the observation date resolve to the lowest bracket. Order books were cleared at 11:00 AM ET on Oct 22. For the Oct 20 highest-temperature market specifically, a dispute over whether coordinate-based WU data showing 21°C qualified as valid LTFM data was rejected — the market resolved 13°C or below. Polymarket confirmed no valid data existed under the rules, and the disputer lost their bond. Rule change: All temperature markets created after Oct 22, 11:59 PM ET will resolve using METAR data. Existing markets remain under current rules. The community criticized the lack of a precise WU URL/station definition in the original rules; the team acknowledged the ambiguity. ETH Price Markets – Oct 22 Resolution The Binance ETH/USDT 1-minute candle closing at 12:00 ET on Oct 22 settled at $2,398.91. Key implied resolutions: Above $2,300 → Yes; Above $2,400 → No; Between $2,300–$2,400 → Yes. Russia–Ukraine Diplomatic Meeting Markets U.S. Envoy Steve Witkoff's separate meetings with Ukrainian officials in Oslo and Russian officials in St. Petersburg on Oct 20–21 do not qualify as a diplomatic meeting under market rules, as both countries' representatives were not physically present at the same meeting. Third-party mediators do not count as representatives of either country. This clarification applies to all related markets with deadlines from June through December 2026. Tampa Bay Rays vs. Milwaukee Brewers MLB Markets Rules clarified: if an inning is not played or the game is cancelled, inning-by-inning and first-five-innings markets resolve to Draw. --- ⚠️ Bugs & Issues CLOB Performance Degradation (Ongoing) Significant API/CLOB issues persisted over the past 24+ hours: - FAK/taker order latency rose from ~315ms (Oct 19) to ~670ms, with p90 reaching ~1.4–1.5s. - Cancel acks remain fast (~20ms); GET round-trips unchanged. - WS fill latency severely worsened; one user measured a ~150ms (>1.5×) median increase. - EU-based traders reported WebSocket messages routing via US (JFK CloudFront) instead of Dublin, adding ~70ms per message. - GTC orders receiving repeated "can't be canceled because it is pending/delayed" rejections for up to 3,350ms after submission. Staff member skulldoom97 confirmed the issue is load-related, not caused by recent changes, and that the team is investigating tuning options. No ETA provided. Additional issues reported: - gamma-api IPv6: DNS not returning an IPv6 address; reported to devs. - "Market opening rate limit" error on POST /orders: undocumented rate limit causing developer errors; documentation formally requested. - Builder API / session-key 403 error: Developers receiving 403 {"error":"not allowed"} from the relayer; directed to DM staff. - API returning HTML instead of JSON: Some bots receiving raw Cloudflare error pages instead of API responses. - Intermittent order placement/cancellation failures via API (sig type 3) reported; skulldoom97 suspects a Cloudflare issue and is investigating. --- 📋 Clarifications - WebSocket snapshot staleness: WS subscriptions sometimes provide outdated snapshots with gaps in updates. Community requested sequence numbers and a unified order_book channel with verifiable update continuity. - SDK feature request: Event filter for list_account_trades endpoint requested (already available for list_trades and list_activity). Given the Istanbul temperature market dispute and the shift to METAR data, are prediction market rules better served by being overly specific upfront or flexible enough to adapt when data sources fail?

UMA DIGEST — 23 OCTOBER 2026 🔥 News & Announcements Crypto Daily Above/Below markets experienced a rule confusion: on Oct 2, rules were silently changed; reverted on Oct 8 to Binance 1-minute candle closing at 12:01 ET; then silently changed again around Oct 10 back to 12:00 ET with no announcement. lonfus stated the platform is now reverting again to 12:01 ET for all markets from Oct 8 onward (including Oct 6–7 live markets), and promised that any future rule changes will be announced well in advance. The chaotic rule flip-flopping allowed user fernando5495 to make an estimated $125k–$150k+ by positioning correctly on the "Ethereum above 2400" market. ⚠️ Bugs & Issues A Superettan match score (4–2) listed on the official resolution source (Superettan.se) appears to be a bug in their video tagger, according to eip15942. rex416. flagged that proposals based on that score differ from what the official resolution source shows, while the proposer (identified as GhostMbao, with possible alt accounts including aartirai) cited Sofascore/Flashscore as corroboration. enormouz noted the dispute requests bot was down. im.the.wizard also flagged a Getafe vs. Lugano UEFA Conference League market proposed as 2–5 when the official source did not yet confirm that scoreline; he attributed the proposal to "corgi" and called it at minimum a P4. 📋 Clarifications NFL player props (Bills-Bengals game): laurleo disputed several NFL player prop markets proposed during live play as P4, citing the rule that they must wait for the official NFL gamebook (published ~10 minutes after game end). laurleo noted precedent from the Damar Hamlin incident where stats from an abandoned game did not count. im.the.wizard and jessicaonlychild agreed props should wait for official stats. Markets for Taylor Swift and Colston Loveland were proposed after game end but before official stats — both im.the.wizard and laurleo considered letting those slide but leaned P4. NBA vs. Uruguay soccer rule inconsistency: abhiz69 questioned why some voters applied P4 to Uruguay half-time markets but P2 to NBA markets, flagging the inconsistency. Regarding the soccer HT market disputed during a bombing alert interruption: exquisite_wolf_79651 noted it was proposed after HT but the match was interrupted in the final 2 minutes due to a bombing alert. 7h0nk3r said that case is "reasonably debatable," while calling the NBA dispute (proposed mid-second quarter) "one of the most open-and-shut P4s" he'd seen. whoooo8888 agreed it was clearly P4. ⚡ Disputes im.the.wizard vs. exquisite_wolf_79651 (soccer score dispute): im.the.wizard disputes a soccer market proposed by a rival proposer, claiming archive.org evidence and video footage prove the official source had not yet updated at the time of proposal (9:58), with the site updating only after 10:04–10:06. exquisite_wolf_79651 counters that cache issues could explain the discrepancy and challenged the validity of the archive as proof. The dispute escalated into mutual fraud accusations: im.the.wizard alleged exquisite_wolf_79651 accepted an on-chain bribe of ~$750 to intentionally misresolve a prior tennis dispute; exquisite_wolf_79651 denied it and accused im.the.wizard of fabricating evidence with associate "Scout." rex416. flagged the matter to a moderator. lonfus crypto market dispute: lonfus bonded a resolution on the "Ethereum above 2400" market at 95 cents (Yes), apparently based on the 12:01 ET rule, but alexchunus argued this market category (Daily Above/Below) was never officially clarified to follow the 12:01 rule — only the Daily Up/Down category was. The market resolved No (ETH did not close above 2400), making lonfus's bond a loss. Community consensus was that a platform bail-out/clarification in lonfus's favor would be improper given the written rules. If UMA's rule changes keep catching even experienced traders off-guard, should the platform prioritize a single immutable rule version over the flexibility to adjust for edge cases?

POLYMARKET DIGEST — 22 OCTOBER 2026 🔥 News & Announcements Protocol v2 is tentatively launching on new markets on November 2. Traders on BTC 5-minute markets are advised to prepare for migration immediately, as each 5-minute market is treated as a new market. Maker rewards on weekly/monthly stock and commodity hit markets have been slashed to ~$1/day (roughly 1/10th of previous levels), causing wide spreads and reduced liquidity. Users warn the taker fee holiday is ineffective without adequate market maker incentives. ⚠️ Bugs & Issues Order latency degradation (Oct 21–22): p50 latency rose from 38ms to 75ms; p99 from 513ms to 2,791ms; order timeout rate increased from 0.015% to 0.285%. Users baka_34910 and vader1208 noted zero communication from Polymarket. Separately, market WebSocket latency and random connection drops were flagged as an additional concern. API & endpoint errors: Users reported HTTP 429 "market opening rate limit" errors immediately after new market announcements (lunmoonatik, miships), and 500 Internal Server Error ("order timed out") on the /order endpoint (pumpty_dumpty). The Gamma API was also reported down for some users on Indian IP VPS. Weather market infrastructure: An NWS (weather.gov) outage is affecting non-US city observations. Fallback rules apply — if NOAA data is unavailable by 11:59 PM ET on the day following observation, Weather Underground (WU) Daily Observations will be used; if no data at all, the market resolves to the lowest bracket. Istanbul has no WU data available and is expected to resolve to the lowest bracket. A bug on WU causes LLBG (Tel Aviv) searches to redirect to Haifa airport; ak504111 is investigating. The Denver resolution station was switched from KBKF to KDEN without public notice. Suspicious queue behavior: User crypto_hamster flagged wallet 0xcd30457c…2dd0 for consistently appearing first in queue on new price levels with ~5ms reaction latency — faster than physically possible from AWS Dublin (~40ms round-trip). Community speculation suggests pre-placed post-only orders rather than reaction-based trading. User bootypool separately alleged preferential queue positioning for certain wallets. Other issues: joaocra2 could not view or place orders post-maintenance (workaround: clear cache/cookies or change browser); darko5586 reported missing taker rebates despite >$7,800 in trades and Bronze tier status; lvn_szn reported a missing maker rebate payment; edgod3714's KYC application has been pending nearly one month; Builder API approval requests from tchicochico (waiting since Oct 9) and inmind5624 were resolved after staff member gasuajex intervened. 📋 Clarifications WNBA GSV vs. ATL (Oct 22): All associated markets (moneyline, quarter, half) will resolve based on the event dated Oct 21 (wnba-gsv-atl-2026-10-21). CS2 — 9INE Academy vs CTRL Esports: CTRL Esports was disqualified from United21 Season 57 for suspected match-fixing and roster fraud. All match results voided; the match is treated as not having started. Championship promotion markets: Markets for Blackburn Rovers, Birmingham City, Coventry City, Bristol City, Charlton Athletic, Derby County, Hull City, Ipswich Town, Leicester City, Middlesbrough, Millwall, Norwich City, Oxford United, Portsmouth, Preston North End, QPR, Sheffield United, Southampton, Stoke City, Swansea City, Watford, West Brom, and Wrexham have all been archived and resolved to "Yes"; net losing positions refunded. UFC 331 — Tsarukyan vs Ruffy "Knockout" market: Bruce Buffer's remarks during the official referee decision do not qualify as a "Yes" resolution. Tel Aviv temperature markets (Oct 20–22): Rules updated to use Weather Underground (LLBG station) as resolution source. Weather market resolution rules (Oct 23+): METAR data will be retrieved from aviationweather.gov. SPECI reports are excluded by community consensus. Concern raised that some traders receive METAR data faster than others, creating an informational edge. Community suggestions include adding 2–3 backup sources and removing WU as a fallback due to observed historical data edits. Taker delay: Current crypto taker delay is 150ms; users are requesting a reduction to 100ms, and 0ms delay for sports markets. With maker rewards slashed 90% and spreads widening across popular markets, is the taker fee holiday enough to keep retail traders engaged, or does Polymarket need to rethink its incentive structure entirely?

UMA DIGEST — 22 OCTOBER 2026 📋 Clarifications A dispute arose over the Polymarket market "Will Trump speak to Friedrich Merz by October 31?" — a user (enormouz) was apparently baited into making a wrong dispute, with others pointing out the only confirmed call between Trump and Merz was on September 17th. A previous similar dispute resolved as early request (P4), which users noted may set a precedent that all "speak to" markets will default to P4. A broader debate emerged around NBA and soccer halftime market proposals. Some proposers have been submitting results before the official resolution source (NBA.com) updates, or before the period of play has fully concluded. The relevant rule clause states: "This market may resolve only when the listed period of play has concluded and the result can be definitively determined by the listed resolution source(s)." Users noted this rule applies to halftime/set markets but apparently not to full-game totals, which im.the.wizard called contradictory. jessicaonlychild confirmed that if the score is confirmed, a halftime proposal is not P4, but acknowledged Polymarket's rules need updating. A CS2 esports market dispute was raised: a user (verlin7469) argued that Map 1 of a match should resolve on its actual result since it was played to completion, while the forfeit only occurred on Map 2. Others explained the team was banned for match-fixing/cheating, and the tournament organizer voided all results, meaning UMA follows Polymarket's 50/50 resolution. ⚡ Disputes A significant personal conflict escalated publicly between joes49572 and exquisite_wolf_79651 (cruz). joes49572 accused cruz of voting based on personal grudges rather than rules, citing two on-chain transactions (0xd2ced7bdb1fff315c781d45de3b8f9ddbcefafe51a2dd12b18015a196f20d2d5 and 0x742a5b0a05aded532182b3bbd4fa914a82d379ec0f7f1da1a91d6b5e1f35514e) as evidence of alleged improper conduct, and claimed cruz posted P4 on a table tennis dispute without any evidence at the time. joes49572 also alleged that uma.rocks posts selectively to swing votes. Cruz denied bias, stating he only posted on the 9 first-half markets where rules were being misread, and that he watched the TT match himself before posting. armanh01 noted that regardless of personal disputes, the actual NBA/soccer proposals should be judged on the rules and prior clarifications, not on who is disputing. ⚠️ Bugs & Issues sam46 reported that the "last page" button on the UMA explorer (explorer.uma.xyz/requests) has disappeared — only "first," "next," and "back" are visible. Separately, juicec11 reported being unable to complete a reveal via MetaMask mobile or PC, with console errors shown. infinity_d directed the user to open a support ticket, but juicec11 was unable to create one due to a verification issue, which was then addressed by infinity_d. When a tournament organizer voids match results due to cheating, should UMA follow that decision even if individual maps were played fairly?