POLYMARKET DIGEST — 20 OCTOBER 2026 ⚠️ Bugs & Issues A National Weather Service (NOAA) outage is affecting non-US weather stations. braintr identified a likely cause: a change in the weather.gov source code around 2026-10-19 21:30 UTC added a condition restricting results to US stations only, potentially permanent. 0xbel_ announced that per market rules, if NOAA data remains unavailable by 11:59 PM ET the day after the observation date, Weather Underground Daily Observations will be used as the fallback source. Polymarket issued clarifications to dozens of European temperature markets (Milan, Munich, Paris, Madrid, Amsterdam, Warsaw) accordingly. alexchunus flagged outstanding UMA proposals on the temperature markets and warned against premature proposals; ak504111 confirmed clarifications are out on all disputed markets. The question of whether NOAA's API still returning data (via Synoptic) counts as "data available" remains open. Additionally, WebSocket connections were reported dropping every few seconds by apples147, and satatardy reported intermittent internal server errors when sending orders. The Discord invite link on the PolymarketUS docs page (docs.polymarket.us/getting-s…) is expired, per elementace. 🔥 News & Announcements Combined taker tier is still delayed. pmkeaton confirmed it is "supposedly coming early this week" and apologized for the delay, inviting users to bump him on it. Users including jungle_jo and jxmcd expressed frustration over the wait and alleged favoritism toward large accounts with Obsidian tier. berth6833 criticized wallet aggregation as undermining the newly implemented rate limits, allowing multi-account users to bypass them. pmkeaton said he would ask the team for a comment. Esports taker delay was flagged as abnormally high by gmdavid12; pmkeaton confirmed he would flag this to the esports team. 📋 Clarifications NFL "last winless team" markets (Miami Dolphins and Los Angeles Chargers) had their tiebreaker rules updated for clarity: ties go first by strength of schedule, then alphabetically by full team name; the "Other" option is excluded from tiebreaks. The Filip Zorvan Anytime Goalscorer market was clarified: a free kick in the 84th minute that deflected off a substitute is credited to Zorvan by the official resolution source (fortunaliga.cz), so the market resolves in his favor. If NOAA's API is still technically returning data through Synoptic, should that count as "available" for resolving these European temperature markets, or does it need to be directly accessible?

UMA DIGEST — 20 OCTOBER 2026 🔥 News & Announcements Polymarket issued a clarification about a National Weather Service outage affecting non-US weather stations. Per the rules, if NOAA data for the observation date is unavailable by 11:59 PM ET the day after observation, Weather Underground Daily Observations will be used as the fallback resolution source. alexchunus noted this announcement appears to signal that affected weather markets (Paris, Warsaw, Milan, São Paulo, Cape Town, etc.) should be disputed, as NOAA data remains unavailable for all foreign cities. user_v123 remarked on what a mess the situation has become. ⚠️ Bugs & Issues arkhimedean reported that vote.uma.xyz is not showing vote reveal progress, occurring on both Chrome (mobile) and Firefox (desktop). kirbs86 reported a separate issue where vote.uma.xyz fails to commit all 141/141 votes — commits work up to ~119 but fail beyond that, persisting across devices and after clearing cache and restarting. 📋 Clarifications Regarding soccer markets, alexchunus clarified that the official website's information is treated as reality for resolution purposes. For the Adam Idah assist question, this means if the UEFA Nations League site does not record it, it resolves NO — though users were warned that if different parts of the same site show conflicting data, resolution may be unpredictable. On the Whalefall box office market, the-numbers.com shows $7.8M while Box Office Mojo estimates $8M. pojiladevchka flagged this as a potential P4 (unresolvable/ambiguous) situation per the market rule requiring both sources to confirm finalized figures before resolution. For Dota 2 unplayed games, itibou raised the question of whether proposers must wait for the series page to officially confirm series completion, noting that many proposals are submitted ~5 seconds after the decisive game result, before the series page confirms. No definitive ruling was posted. ⚡ Disputes Weather market mass dispute (major event): A large wave of disputes was triggered after proposers submitted non-US temperature markets (Paris, Warsaw, Milan, São Paulo, Cape Town, and others) despite the NOAA/weather.gov outage. ab7x7x provided proof that the weather.gov JS file blocking non-US cities was updated at 21:29:41 UTC on Oct 19, with his bot detecting the change at 21:32:09 UTC, meaning proposals submitted after that point used data from a broken/unavailable source. This is being characterized as proposers "front-running" the official resolution source. As of early Oct 20, im.the.wizard counted 251 open disputes, with ~68 from this weather event alone (plus ~80 more including the Cape Town batch from the prior day). Proposers who continued submitting weather markets even after the outage banner appeared on the resolution page are facing additional disputes. alexchunus noted that Hong Kong weather markets appear unaffected as they use a different resolution page. Cleveland Guardians World Series market: Someone proposed "Cleveland wins World Series - NO" while Game 6 was still being played. laurleo and alexchunus flagged this as premature. jessicaonlychild noted the Guardians had won Game 1. The proposal is expected to be disputed and lose. Saudi military action markets: raskell1 described a recurring issue where ~10 markets from September remain unresolved, caused by proposers asking AI whether Saudi strikes occurred, with AI returning "Yes" — without accounting for the distinction between Yemeni Air Force strikes and direct Saudi military action, which requires a higher evidentiary bar. If Weather Underground data has to fill in for NOAA across dozens of markets, how confident are you that resolution will actually match what the proposers originally used to justify their answers?

POLYMARKET DIGEST — 19 OCTOBER 2026 📋 Clarifications A dispute has been raised across the entire suite of Cape Town highest-temperature markets for October 18 (covering thresholds from 9°C or below up to 19°C or higher). Polymarket confirmed it was aware of the dispute and initially scheduled a potential clarification for 7:15 PM ET on October 18, with order books to be cleared at that time regardless. Following that window, Polymarket issued a formal ruling invoking the Erroneous Data provision: the 19°C reading recorded at Cape Town International (FACT) at 07:28 SAST (05:28 UTC) on October 18, 2026 will not qualify toward resolution of any of these markets. The affected markets — including the 16°C, 17°C, 18°C, and 19°C-or-higher variants — will remain open for 7 calendar days until October 25, 2026, 1:28 AM ET, to allow the resolution source to publish a correction. If a corrected reading is issued by then, it will qualify; if not, the erroneous 19°C reading will still be excluded and markets will resolve on the basis of remaining available data. VIP user hans32312 called it a good clarification. User abhiz69 suggested that in such situations Polymarket should clear the book and clarify immediately rather than waiting, noting that two markets had already settled during the liveness period and the rest could have settled too. ⚠️ Bugs & Issues pastorlul flagged a potential API bug: for esports markets, the line field in game/map handicap API responses appears to be inverted relative to other sports. A -1.5 line for a home-spread in soccer means home handicap -1.5, but in esports it appears to mean home +1.5. No official response was received. Several developers discussed Cloudflare bypassing on sports markets. .alexzor and blunkoed speculated that 1–3 large firms may have been whitelisted, though this is unverified. jungle_jo raised frustration that achieving Platinum taker tier on a single account has become extremely difficult, while certain accounts continue to hold Obsidian tier. satatardy argued the taker tier system should be removed entirely in favor of reduced fees for all users. If Polymarket had immediately cleared the books and clarified instead of waiting, would the outcome have been fairer to traders who got caught in the settlement window?

UMA DIGEST — 19 OCTOBER 2026 ⚡ Disputes Mass dispute: Dynamo Kyiv vs. Polissia Zhytomyr (~98–109 proposals) A proposer known as "Flame" submitted roughly 100+ proposals for the Ukrainian Premier League match between FK Polissia and FK Dynamo Kyiv while the match was suspended mid-game due to an air raid alert (the alert triggered at ~90th minute, with ~2 minutes of stoppage time remaining). im.the.wizard noted he had previously disputed Flame at least 4 times for similar behavior but Flame continued proposing. The match was confirmed suspended via live stream (soccer.tv), official UPL sources, Dynamo Kyiv's Telegram channel, and Ukrainian sports sites. The game eventually resumed and concluded, making all full-time and in-play proposals P4. im.the.wizard confirmed he obtained video of the match still in progress during the proposal window. Disputed count: ~98 full-time proposals at 500 bond each (~$49,000 lost by proposer). user_v123 put the total at 109 disputes / $54,500. Multiple disputors split the rewards relatively evenly (largest single share was 19 disputes). First-half O/U proposals: A handful of first-half proposals were also disputed by some participants, though abhiz69 and im.the.wizard noted these were not P4 per an existing clarification (halftime proposals are valid once the first half is complete). im.the.wizard called the halftime clarification "haphazardly made" and expects it to be revisited. exquisite_wolf_79651 noted a precedent where first-half disputes were previously overturned via clarification. Cape Town max temperature market — erroneous data dispute A weather reading of 19°C was recorded at Cape Town International Airport (FACT) at 05:28 UTC on October 18, a jump of ~6°C above surrounding readings and inconsistent with all nearby METAR/SPECI data. hans32312 and modali1 provided evidence that the 19°C SPECI report assigned to FACT was actually a duplicate of a reading from FABL (Bram Fischer Airport, ~900 km away), including identical wind, temperature, and thunderstorm conditions — statistically near-impossible for two separate airports. alexchunus argued all brackets should be held open under the market's erroneous-data rule (up to 7-day wait), while some brackets had already settled before action was taken. user_v123 posted the official resolution clarification: Per the Erroneous Data provision, the 19°C reading for Cape Town International (FACT) at 07:28 SAST on October 18, 2026 will not qualify toward this market's resolution. The market will remain open for 7 calendar days until October 25, 2026, 1:28 AM ET, awaiting a correction. If no correction is published, the market resolves on available data excluding the 19°C reading. The 19°C "Yes" bracket is effectively dead. If no corrected reading is issued, 16°C is considered the likely true daily high. alexchunus noted some brackets had already misresolved before the clarification was issued. 📋 Clarifications In-play soccer proposals (general reminder): Proposing soccer markets while a match is still in play has never been permitted. laurleo asked if this was a new rule; abhiz69 and jarmax confirmed it has always applied to soccer specifically. China GDP market: aterex163 flagged that the China Q3 GDP figure released on October 19 uses the phrase "preliminary estimates" rather than the exact title "Preliminary Accounting Results of GDP" specified in the market rules (scheduled for October 20). armanh01 and jamestalaricof argued these are the same release and China always uses that language. No dispute was filed. Iwaki FC vs. Ventforet Kōfu (March 8 market): dyanreel raised that some props resolved 50/50 and the moneyline was proposed "Draw," but the first match played after March 8 was actually on March 14 (0–1 Iwaki). No resolution reached in the channel. With over 100 proposals from a single actor during a live air raid, does this change how you think UMA should handle real-time geopolitical disruptions to sports markets?

POLYMARKET DIGEST — 18 OCTOBER 2026 📋 Clarifications All 2026 Chicago Marathon winner markets (both Men's and Women's) have had their resolution rules updated. Due to missing official data from the Chicago Marathon results website, Polymarket confirmed that all related markets will resolve based on a consensus of credible reporting rather than the official results page. This affects markets for all listed runners including Brigid Kosgei, Hawi Feysa, Jacob Kiplimo, Amos Kipruto, and many others. ⚠️ Bugs & Issues WebSocket order book sync issue: clericode reported a potentially significant bug where the WS order book snapshot on subscribe is sometimes stale by ~1 second on average, and occasionally by several minutes. In some cases, subsequent price_change messages fail to cover the gap, leaving the book in a permanently incorrect state. REST /book appears consistently fresh. Open questions include the correct resync strategy, whether a sequence number or gap signal exists, the exact hash formula, and what the level field (1/2/3) does in subscriptions. CLOB latency under load: _valentyn_ raised a concern that spamming the CLOB during peak hours could push maker cancel latency beyond the taker delay, potentially breaking order priority. blunkoed noted the matching is "mostly FIFO with some quirks" and that past exploits around taker delay bypass have existed, though no known active one remains. llambre and others confirmed they have observed post/cancel latency spikes correlating with volatility. Outdated API docs: blunkoed flagged that the official docs still incorrectly state a 250ms taker delay for crypto markets, which is no longer accurate. Dublin API geo-block myth: blunkoed clarified that the Polymarket API was never geo-blocked for Dublin — only the frontend was. cryptowalkure added that moving a VPS from Dublin to London (AWS) yields no significant advantage since traffic routes through Cloudflare regardless. Archived market refund: jenia9419 reported not receiving a refund two weeks after their market (will-yashar-win-the-second-most-seats-israel-2026) was archived. How much should traders factor in the potential for stale order book data when building strategies on Polymarket's WebSocket feed?

UMA DIGEST — 18 OCTOBER 2026 📋 Clarifications A Polymarket market asking "Will the White House call a full lid by 6:30 PM on October 17?" was proposed early and disputed to P4. The consensus is that such markets must wait until one of the resolution sources (Roll Call or forth.news) actually publishes a lid time — even if the answer is ultimately No. 7h0nk3r clarified: "Should just wait until the first lid for the day is published (or the next day's lid for the rare instances in which no lid is published for a day)." sam46 noted this matches prior precedent, and the market was successfully disputed by nefffooor. ⚡ Disputes rex416 raised a question about an unresolved case, asking infinity_d (Polymarket) to explain how a disputed market differed from the Andy Burnham precedent, stating they lost the dispute but couldn't understand the distinction. infinity_d noted the resolution source was clear in the Polymarket UI — the player in question had no assists — and that the dispute thread had been empty, prompting them to post their opinion after the vote rolled. infinity_d also clarified they do not vote and hold no UMA staked, though nefffooor noted that posting a Polymarket opinion carries significant weight regardless. Separately, laurleo flagged what appear to be several questionable proposals on sports markets (an O/U 4.5 dispute and a spread P4 for a game), commenting these are generating easy dispute profits and telling the proposer to "cut it out." How should UMA handle disputes on markets where the resolution source is technically clear but the precedent for applying it seems inconsistent with past cases?

POLYMARKET DIGEST — 17 OCTOBER 2026 ⚠️ Bugs & Issues Significant and persistent API/infrastructure issues are ongoing. Since around 8:00 AM UTC on October 16, users have reported sharply elevated market data and order entry latencies across all markets, including sports. skulldoom97 (Polymarket staff) acknowledged the reports with "We're taking a look," but as of the time of these messages no fix had been confirmed. ari_0102 noted it previously took ~11 hours for the team to begin investigating a similar incident. Additional technical issues reported: - CLOB WebSocket randomly stops sending data without errors, even with reconnection logic in place — multiple users confirmed increased drops, particularly on live events. Switching from IPv6 to IPv4 was suggested as a partial workaround for connection errors (error 1013). - Rate limiting inconsistency: users are hitting 429 market opening rate limit errors despite the API reporting remaining capacity (e.g. 297 remaining). Some users suspect priority queuing for certain accounts; others attribute it to a sloppy implementation. No official response was given. - Tick size bug has resurfaced: orders are being rejected even when the order book shows a valid price (e.g. 96.0¢). - Auto order cancellation settings allow entering 30 seconds but throw an error requiring a minimum of 180 seconds. kurwamach. confirmed this was reported to the team. - A bar chart error was reported on the BTC Up or Down 5m market. - Combo settlement is reportedly very slow — users must wait 2+ hours for proposals plus additional time for redemption. Flagged as feedback rather than a strict bug. - A deposit bug was mentioned but not elaborated on. 📋 Clarifications Tesla Roadster 0-60 market resolved Yes. Polymarket confirmed that the official Tesla-published time for the live run on October 15, 2026 is 0.81 seconds, satisfying the sub-1-second threshold per market rules. The order book was cleared at 12:30 PM ET on October 16. Carles Puigdemont markets (October 15 and October 31 deadlines) had their rules updated for clarity, specifying that resolution requires Puigdemont to physically enter the terrestrial territory of Spain before the respective deadline at 11:59 PM ET. 2026 F1 Bahrain Grand Prix red flag market: Polymarket clarified that a red flag shown during the formation lap does not qualify. Only red flags shown after the start of the first lap count toward a "Yes" resolution. Tomás Jacob 3+ shots market: Per MLS match log data, Jacob had 2 right-footed shots against FC Cincinnati on October 10, 2026 — resolving the market No. ALCS rescheduling: Multiple Tampa Bay Rays vs. Cleveland Guardians markets have been updated. Game 4 (originally October 16) is rescheduled to October 17 at 8:00 PM ET. Game 5 (originally October 17) is rescheduled to October 18 at 5:00 PM ET. Affected markets include moneyline, spread, O/U 6.5, and NRFI. With API latency issues persisting for over 24 hours and rate limiting errors contradicting the system's own capacity reports, do you trust the current infrastructure enough to place significant positions right now?

UMA DIGEST — 17 OCTOBER 2026 ⚠️ Bugs & Issues Several UEFA corners markets were settled despite participants acknowledging the resolution was incorrect. tenacious_mango_59265 flagged that the Juventus vs Celta UEFA Europa League corners market (15 Oct) showed 3–7 on the UEFA stats tab and 4–7 in commentary, yet it settled without dispute. abhiz69 expressed frustration that UMA let these high-volume markets resolve wrongly while focusing dispute energy on low-volume (<$500) markets. A separate MLS shots-on-target market was held in extension for nearly a week awaiting a Polymarket clarification; alexchunus noted the final answer came from the official MLS player match-log page showing 2 right-foot shots, overriding a figure of 3 shown on other pages. h2orz pointed out this contradicts how Cycle 1 of the same market was resolved and called the extension mechanism "disgusting." Multiple users noted UMA profits regardless of outcome — proposers provide cheap resolution labor when correct, and bond money is redistributed when disputed. 📋 Clarifications A detailed evidence review was submitted for the Deportivo Saprissa vs Sporting FC Total Corners O/U 10.5 market (15 Oct 2026). User .3rdna cross-referenced UNAFUT/Genius Sports (official source, 10 total corners taken), Flashscore (12 total) and Futbol24 commentary (12 awarded), and provided timestamped Radio Monumental audio to argue that four second-half corner sequences (~58′, 61′, 75′, 76′) present in the broadcast have no matching entry in UNAFUT's "corner taken" timeline, while UNAFUT lists three corners clustered at 64′–65′. abhiz69 responded that UNAFUT is the sole primary source under market rules and its total of 10 governs resolution. alexchunus added that at least one of the Flashscore/Futbol24 entries was a misclassified direct free kick, and suggested emailing the league to correct the statistic before voting opens. The dispute status remains open pending the evidence review. ⚡ Disputes P4 (premature proposal) cartel allegation — table tennis markets: wzht alleged that a group of proposers operates as a cartel in table tennis markets, selectively disputing outsiders' proposals for being P4 while not disputing each other's P4 submissions. He also raised OFAC-sanctions concerns about some members. alexchunus and woodmark520 rejected the defense, noting that P4 rules are absolute (even 1-second-early proposals are disputable, as demonstrated by recent Bitcoin disputes), and that the solution is to dispute the group's P4 proposals rather than complain. woodmark520 invited anyone with evidence of their P4 submissions to post it for collective action. No resolution was reached. Kyiv drone attack market — YES vs NO: A Polymarket market on whether Kyiv was attacked resolved YES. feracios_max noted that the prevailing consensus among regular proposers had been to require an official announcement from Klitschko or KCSA/KCMA, whereas raskell1 argued that KyivAlarm alerts plus KPZSU reporting and on-the-ground explosion reports constituted sufficient evidence under Polymarket's rules. The market resolved YES undisputed; feracios_max, who held no position, expressed disappointment that no one disputed it. When official sources contradict each other on the same match stat, should UMA default to the league's internal records even if broadcast data looks more complete?

POLYMARKET DIGEST — 16 OCTOBER 2026 ⚠️ Bugs & Issues Several technical issues were reported and discussed: Data API outage: The /v2/trades and /v2/positions endpoints were returning internal server errors for roughly 2 hours. skulldoom97 flagged it to the team. exo_pm clarified that the overall failure rate was ~0.001% (≈300 errors per 20M requests/hour), attributing most failures to queries walking full historical partitions without using start/end parameters, though chickenwing_14999 disputed this, noting their queries had been working fine until suddenly breaking. London co-location latency regression: Multiple users reported that the London co-location endpoint has become slower than Dublin — previously it was ~3ms faster. The suspected cause is KYC wallet verification going through a slow Redis lookup. sparkling_swan_13776 directly asked Polymarket devs to hardcode KYC addresses into a faster data structure to resolve the issue. Cancel acknowledgements are also reported regularly exceeding 1000ms (p99/max), confirmed by thrillhouse_420 and why_monch. Relayer rate limiting: earltrad reported aggressive rate limiting on the relayer starting around 22:00 UTC. 429 "market opening rate limit" errors: alex_xoxoxxx reported orders posted to new markets (received via WSS new market message) started failing with this error since the morning of Oct 15. Soccer search "more markets" empty page: sonix_1 noted a long-standing bug where searching for soccer games shows "more markets" as the first result, leading to an empty page. $0 entry prices in positions tab: jimmybuzzard flagged a recurrent display bug showing $0 entry prices, and why_monch noted related display anomalies (shares shown at 0¢ or above 100¢). Derivative markets dropping from PolyUS APIs: datlebanese reported spreads/totals markets for multiple sports disappeared from the API around 21:46 UTC. 🔥 News & Announcements kartojal confirmed that CLOB v2 libraries are deprecated as of today (Oct 15) and will receive no further maintenance. Developers are advised to migrate to the Python unified SDK. Migration guide: docs.polymarket.com 📋 Clarifications Polymarket posted a rules bulletin for the market "Will Apple release a new product line before 2027?" The market resolves Yes if Apple publicly announces and launches a genuinely new product category (not an iteration of an existing line) by December 31, 2026, 11:59 PM ET. Apple's newly announced HomeView — a smart home device with touchscreen, camera, speakers, and Siri AI, announced October 13, 2026 — has been identified as qualifying under this definition, as it represents a product category Apple has not previously sold. Does HomeView's smart home device category count as genuinely "new" if Apple's already selling related hardware like HomePods and iPads, or does the combination of features create a distinct product line?

UMA DIGEST — 16 OCTOBER 2026 ⚡ Disputes A wave of temperature market disputes has appeared, attributed to a new/rookie proposer. jarmax notes the user already has 5 disputes and their PNL has swung from -1.6K to -3.6K. hans32312 flagged that a London temperature proposal was submitted at 24:55, making it virtually impossible to have been sourced from weather.gov. im.the.wizard added that the proposer operates more than one wallet and tends to submit proposals early. The general consensus is that all of these are likely P4 (invalid/wrong answer) and participants are treating them as free money to dispute. 📋 Clarifications abhiz69 requested that the team extend two UEL markets: uel-cel1-juv-2026-10-15-corners-team-home-2pt5 and uel-cel1-juv-2026-10-15-corners-odd-even. Are these temperature disputes actually revealing a systemic issue with proposal validation, or is this just an easy arbitrage opportunity until the bad actor runs out of capital?

POLYMARKET DIGEST — 15 OCTOBER 2026 🔥 News & Announcements A large batch of Polymarket markets for the USL Championship match Sporting Jax vs. Birmingham Legion FC (October 14, 2026, 7:00 PM ET) received bulletin board rules updates. Markets affected include over/unders, spreads, team totals, BTTS, first-to-score, halftime/second-half results, match winner, and exact scores. The resolution source hierarchy is: official stats → Flashscore → Sofascore → consensus of credible reporting. Post-resolution score revisions will not be accounted for, and markets resolve 50-50 (or "Draw") if no acceptable data is available within 24 hours. Note: several market URLs contain an incorrect date (2026-10-10); the bulletin board update references the correct event link. V2 migration: Some v2 markets are live for public testing. Developer kartojal confirmed they are investigating a reported issue with Gamma fetch details for v2 markets. A resize endpoint is planned for the new exchange (v2) but will not be backported to the current CLOB. ⚠️ Bugs & Issues CLOB latency incident (October 14): Latency degraded significantly from ~08:00 UTC, with multiple developers reporting elevated place/cancel and feed latencies. skulldoom97 acknowledged the issue ~11 hours later and attributed it to load caused by crypto market activity spilling into sports markets. Throttling measures were applied and latencies began recovering around 21:25 UTC. skulldoom97 apologized for the delayed response and asked users to tag him directly in future incidents. London vs. Dublin VPS performance: Developer discussion confirmed AWS London is currently performing worse than Dublin for order matching, with POST requests degrading significantly after passing through Cloudflare LHR compared to a month ago, despite lower ping. Geoblock/API access (South Korea): User 5am3658 reported HTTP 451 (Cloudflare 1026) errors from a South Korean IP on both the geoblock and CLOB time endpoints, despite documentation stating South Korea should have unrestricted API access. No resolution confirmed. Throttling report (October 15): User vader1208 reported being throttled despite being within Gold tier maker limits. skulldoom97 confirmed no new throttling behavior had been activated and requested a DM to investigate. 📋 Clarifications Multiple market makers and takers raised strong concerns over current fee levels, citing declining volume, reduced rebates, and difficulty sustaining profitable strategies. The community is requesting lower taker fees and higher maker rebates. Given the fee concerns and declining volume mentioned, do you think Polymarket needs to cut taker fees to stay competitive, or would better infrastructure stability (like fixing the CLOB latency issues) be more impactful?

UMA DIGEST — 15 OCTOBER 2026 🔥 News & Announcements infinity_d announced the Polymarket Protocol V2 Migration alongside UMA updates. Key changes include: — New Polymarket and UMA adaptor contracts — Minor upgrade to the existing MOOV2 deployment — New ancillary data encoding schema — A new Risk Labs Proposer API that replaces onchain proposing to eliminate toxic proposal front-running MEV A limited set of test markets is already live on Polymarket V2 (visible in the Explorer dApp). Testing ends November 2nd, after which all new production markets will be on V2. Non-programmatic users need no migration effort — Explorer and Voter dApps will be updated transparently. Programmatic proposers, disputers, and third-party builders must review the Polymarket V2 migration docs and Proposer API docs and adopt the new API. Questions and suggestions can be posted in the V2 & Proposer API Migration channel. ⚡ Disputes A dispute arose over the Gemini Argon – Humanity's Last Exam Polymarket markets. A new proposer settled these markets, but scriptlin_55968 argued the Gemini Argon model only appeared on October 14 (after midnight ET), making the resolution potentially premature (P4). The proposer's side (gum5683, alexchunus, nsc6124) countered that the burden of proof lies with the disputer, and that the only evidence offered — price action on the chart and the appearance timing relative to other models — is insufficient. A Wayback Machine snapshot from 11:39 PM October 13 ET was cited by scriptlin_55968, but alexchunus noted there is no snapshot between 11:39 and midnight to confirm it was absent, and that order book bonding alone does not prove release timing. Ultimately, scriptlin_55968 declined to formally dispute, acknowledging the lack of definitive proof. The markets remain settled as P1/P2. alexchunus and nsc6124 noted that P4 arguments based only on circumstantial evidence have consistently lost in UMA. Given that the disputer had a Wayback Machine snapshot but still couldn't prove the exact release timing, how much evidence should really be required to overturn a market settlement?

POLYMARKET DIGEST — 14 OCTOBER 2026 🔥 News & Announcements Goodwill payments have been sent to 194 affected wallets following the Crypto Daily Up/Down rule change for "BNB Up or Down on October 5?" and "BTC Up or Down on October 5?". No action is needed if you received one. Users who believe they were affected but did not receive a payment can request a review via a dedicated form. 0xbel_ confirmed all requests are reviewed individually. suhailkakar confirmed that Polybolt is already live as a very early preview at docs.polymarket.com. Binance crypto feeds are still missing, but Chainlink and Pyth streams are working. An official release will follow once Binance support and direct Chainlink API access (with sponsored API keys) are added. 📋 Clarifications The rules for the Epic Games vs Roblox - higher valuation on December 31? market have been updated for clarity. The key addition: "If Epic Games's valuation is equal to Roblox's public market capitalization at resolution, this market will resolve to 50-50." Regarding Lucknow (VILK) weather markets, hans32312 clarified that Polymarket US uses CLI (minute-by-minute data for peak temperature) while Polymarket International uses METAR/SPECI. He also noted Kalshi uses the same resolution source and resolved identically. A separate discussion highlighted that the VILK station frequently publishes multiple corrected METARs at the same timestamp, with revisions sometimes appearing 40–45 minutes later on the resolution source — raising concerns about market fairness for that station. ⚠️ Bugs & Issues A previously undisclosed exploit in the CLOB taker delay was discussed: between Oct 6–8, the taker delay was variable (0–1s instead of a fixed 1s), allowing orders to be timed to slip in just before the second boundary. why_monch noted a fix was deployed and referenced in the CLOB changelog on the status page. The issue was reportedly limited to sports markets per _valentyn_. Cancel latency was reported as degraded again by phoenyx69. Users also noted the CLOB is frequently lagging, with co-location latency at ~180–200ms (AWS London) only when the CLOB is not lagging. A Chainlink feed relay issue was raised by edityournameplease: Polymarket is not relaying the validFromTimestamp field, only the price and production timestamp, which causes data integrity issues. edityournameplease noted this was flagged previously without action. Developers flagged that the CLOB last_trade_price stream does not emit all trade transaction hashes, and the public RTDS stream only has second-level timestamp precision. pendulumflow suggested using on-chain data as the authoritative trade list and the CLOB stream as a clock, joining by tx hash where available. exo_pm confirmed that a previously reported bug (from #bug-reports) has been corrected. Do you think individual wallet reviews for disputed payments are thorough enough, or should Polymarket publish aggregate data on how many requests were denied and why?

UMA DIGEST — 14 OCTOBER 2026 📋 Clarifications A Counter-Strike market for the CS2 GoldRashers vs Zotix event on Polymarket has caused confusion due to conflicting dates. The match was originally scheduled for August 10 but was played on August 21. The moneyline and O/U 21.5 markets were created on August 10 and are being proposed as P3 (past deadline), while O/U 24.5 and handicap markets were added on August 21 and are being proposed as P1/P2. mebeim confirmed the proposals themselves follow the rules correctly. stradiveri noted that historically the moneyline date is considered authoritative for the event, which would complicate the newer markets. No formal dispute was raised — participants acknowledged the situation is messy but proposals are technically correct. ⚠️ Bugs & Issues The GitHub critical incidents in October market was nearly misproposed: the GitHub status page was showing misleading times (a ~4-hour outage listed as 10 minutes on the main page). mebeim clarified the actual longest incidents were 3h 43m 9s (Oct 6) and 3h 37m 44s (Oct 5), both exceeding the market's 1–3 hour bracket. The Trump Truth Social post tracker was reported as lagging, causing a proposal to be submitted slightly early. The post count was confirmed above threshold, making the NO proposal valid. The Zelensky tweet market tracker was also flagged as unreliable. For an MLS Brian White shots market (Chicago vs Vancouver, Oct 6), the official MLS stats page briefly showed 4 shots before being revised down to 3 via the API. im.the.wizard noted that postgame stat revisions are common, especially for shots and assists, and confirmed the API shows 3 as the final figure. The Zelensky tweet market was disputed due to a misclick, according to 7h0nk3r. When historical data sources conflict on the same event, should the earliest scheduled date or the actual event date take precedence for market resolution?

POLYMARKET DIGEST — 13 OCTOBER 2026 🔥 News & Announcements Polymarket engineering confirmed that fixing the CLOB is the highest priority. habitual_revers noted the team is focused on rebuilding fundamentals and will make only incremental, low-risk improvements in the meantime. RTDS is expected to be deprecated around October 23. 📋 Clarifications Cricket – WCL England vs South Africa: The market has been archived and will resolve Yes (England Champions). Net losing positions held at clarification time will be refunded. Will Trump say "Ammunition" this week? After announcing a 4:15 PM ET deadline for a decision, Polymarket ruled that Trump's October 6 remarks to reporters are not a conclusive mention of "ammunition" and will not qualify for a Yes resolution. The order book was cleared at 4:15 PM ET. Jack Doherty X posts (October 31 & April 30 markets): Rules updated for clarity — only posts from his official account @dohertyjackk or any successor name qualify. Posts from other accounts do not count. Gangwon FC vs Jeju SK – First Corner: Polymarket confirmed that Sofascore's "Commentary" tab may be used as a resolution source per fallback rules. Los Angeles temperature (Oct 11): A user disputed the market settlement at 74°F, claiming the actual high was 72°F. hans32312 (VIP) countered with NWS CLI data showing 74°F was reached at 12:02 AM. The disputing user maintains hourly data never showed 74°F. No formal dispute has been opened. ⚠️ Bugs & Issues Order matching / taker strategies: chickenwing_14999 flagged what they call a catastrophic bug in sports taker strategies, noting a significant drop in volume on the weekly leaderboard and pointing to order-matching reliability as the cause (not taker delay). clzzzzzzz echoed that order matching degradation is severe. Strike price / price-to-beat endpoint: Multiple traders are frustrated that no reliable API endpoint exists for the crypto market strike price. Current workarounds — RTDS, the GUI link, and Polybolt — all have reliability issues (missing frames, wrong data in the first ~10 seconds). A Polymarket dev (suhail) had reportedly promised a solution months ago. habitual_revers confirmed this is a feature request outside their immediate scope and advised not to wait on it. Login issues: data_dominus reported being logged out and unable to log back in. Tennis market resolution delays: crovax66 reported won tennis markets not resolving and some sitting at 50% odds incorrectly. Gamma-API not returning V2 markets: zhongbaolin reported that querying gamma-api by V2 condition_id returns empty results. It is unclear whether V2 markets will be queryable on gamma-api before or after the November 2 launch. ⚡ Disputes Taker rebate consolidation: jungle_jo publicly pressed Polymarket (tagging keaton) to honor a rebate consolidation request announced 4 weeks ago, stating it has not been acted on. minglee123xd alleged that keaton has repeatedly broken promises to the community. No official response was given in the channel. With the CLOB rebuild taking priority and RTDS deprecating soon, how many traders do you think will actually migrate to reliable alternatives before the October 23 cutoff?

UMA DIGEST — 13 OCTOBER 2026 ⚠️ Bugs & Issues A user reported a balance discrepancy between the official UMA webapp (oracle.uma.xyz) showing 1,071.08 UMA staked vs. UMA.rocks correctly showing 1,071.52 UMA. The issue appears to be related to frontend indexing after delegating to the TychePrime committee. A scam reply was posted in response and the account was banned. The UMA.rocks team is reportedly already looking into it. ⚡ Disputes Chicago Marathon Women's Winner 2026 (Polymarket) — A dispute arose over whether results on the Chicago Marathon official website qualify as "official results" for resolution purposes. The site currently labels its leaderboard as "Unofficial Race Results." The P4 side (majority view, including eip15942, jamestalaricof, im.the.wizard, and 7h0nk3r) argues that the organizer itself labels the results as unofficial, meaning they can still change after review, and therefore the market should not resolve yet. They also agree the October 18 deadline is irrelevant since a winner has been announced, making an "Other" resolution implausible. The opposing side (nopsuke, mebeim) notes that the resolution source language — "the first official results published by the Chicago Marathon" — could be interpreted as whatever first appears on the official website, and that a press release was also issued. mebeim warned that Polymarket may clarify against the P4 position since the "official" results may only be published after the market deadline, and PM may prefer to resolve to the announced winner rather than let it go to "Other." All 7 dispute slots were filled quickly; eip15942 missed disputing due to a wrong wallet being connected. A separate proposal was also made on the men's marathon market under similar circumstances. 📋 Clarifications Several users (laurleo, nefffooor, alexchunus) called for Polymarket to issue a clarification confirming the marathon markets will remain open past the October 18 deadline if official results are not yet published, to prevent attempts to force an "Other" resolution. The broader point was raised that MVP/award-style markets and sports result markets should not have short hard deadlines, since cancellations are extremely rare. Do you think sports markets should have flexible deadlines that extend until official results are confirmed, rather than fixed cutoff dates that don't account for review periods?

POLYMARKET DIGEST — 12 OCTOBER 2026 ⚠️ Bugs & Issues Several bugs reported: scamwisegamgee flagged a max rounding bug, egging745 reported that orders don't appear without a manual refresh, and godson01. noted that Xtracker is bugged on the White House, Zelenskyy, and possibly Elon Musk markets. On the CLOB performance side, cryptowalkure shared detailed latency measurements from a Dublin VPS: taker delay is ~150 ms, p50 match time ~41 ms, but p90 reaches 833 ms and p99 ~1.4 s, with 24% of answers slower than 400 ms — almost entirely during US hours when the matching engine appears to hold orders while the book feed goes silent. trex8791 confirmed nearly identical results and noted that attempts to clip the tail (racing idempotent orders via multiple IPs, cancelling in-flight orders) have had negligible effect. moonshotnft also reported being filled below their resting maker price repeatedly (placed at 41¢, filled at 40.8¢). There are no indications of a timeline for the Rust CLOB rewrite — _valentyn_ asked when it would go live, and phoenyx69 joked the better question is whether it ever will. 📋 Clarifications All BAL vs. NYY (2026-09-27) markets — including First 5 Innings Winner and all individual inning winner markets (1st through 9th) — will resolve as Draw due to a game cancellation. 🔥 News & Announcements Regarding co-location access: _valentyn_ confirmed there is no Cloudflare bypass available, approval is wallet-only, and the process takes approximately 2 weeks. No AWS PrivateLink or VPC peering equivalent to Kalshi is available. jb6._ noted that eu-west-2 (lower latency) requires completing a KYC form. There is also no sandbox/test environment for builders — confirmed by community members. With 24% of orders experiencing latency over 400ms during US hours, how much of Polymarket's trading edge do you think is being decided by infrastructure rather than prediction skill?

UMA DIGEST — 12 OCTOBER 2026 ⚠️ Bugs & Issues NegRisk markets stuck due to P3 (0.5) proposals: alexchunus noted that markets where proposers incorrectly resolved NegRisk contracts to P3 are still frozen and cannot pay out — emergency resolution by Polymarket would be required. One example (Tochigi SC vs. Thespa Gunma, March 2026) has been stuck for 216+ days. The whitelisting system is also under criticism: mebeim and stradiveri pointed out that proposers can get whitelisted by posting 5 trivial or incorrect requests via the bot, without anyone verifying them, leading to inexperienced proposers attempting NegRisk resolutions. 📋 Clarifications LA Temperature market (Oct 10): A dispute arose over which temperature reading to use. im.the.wizard clarified that clicking "show hourly data" yields 77°F per the resolution rules, despite the default view showing different values. hans32312 explained that the 5-minute ASOS readings are rounded Celsius conversions and do not count as real METAR readings. CS2 MW vs LP map handicap: markello_86 disputed whether Map 2 (Cache) was formally awarded to largadosypelados, citing HLTV's 0–1 record and no gameplay footage. asano.neru (Polymarket Team) responded that per the rules, maps won by forfeit count toward the handicap, and that METANOIA Wolves forfeited Map 2 by failing to connect within the allotted time, giving LP a 2-0 series victory. The matter is now in UMA voting. NFL OT scoring market: A dispute was filed over whether a team could reach 45 points in an OT game. laurleo and im.the.wizard argued it is mathematically impossible under current NFL OT rules — the maximum OT score is 14 additional points (8+6), as the game ends immediately upon the second touchdown with no PAT allowed. jessicaonlychild [VIP] raised edge cases but laurleo confirmed current rules make >14 OT points impossible; the proposals were made ~2 minutes into OT, so OT rules govern. ⚡ Disputes MLB Orioles–Yankees NegRisk cancelled game (active): A proposer (ghostmbao) proposed 0.5 (50–50) for first-five/first-inning NegRisk markets after the game was cancelled with no makeup, following the explicit rule: "If the game is canceled entirely, with no make-up game, this market will resolve 50-50." The proposal was disputed because NegRisk contracts technically only support P1 or P2, and the ancillary data states "This request MUST only resolve to p1 or p2." Two camps have formed: — eip15942 argues the proposer followed an explicit cancellation clause, the contradiction lies in Polymarket's own rule-writing, and cites a precedent (Tochigi SC, March 2026) where a NegRisk-linked UMA request settled at 0.5 undisputed. They argue UMA should honor the 50–50 clause and let Polymarket handle payouts separately. — im.hydro, alexchunus, and others argue the contract constraint overrides any written rule, proposers are expected to know NegRisk cannot resolve P3, and ghostmbao should seek a refund from Polymarket rather than expect UMA to resolve at 0.5. stradiveri acknowledged Polymarket's rule-writing is at fault but agreed proposers bear responsibility. ghostmbao is seeking a refund via Polymarket support (DMed "bel"). im.the.wizard noted the proposer has a legitimate case for a refund but that Polymarket rarely reimburses UMA bond losses. If Polymarket's own rules explicitly say "resolve 50-50" but the contract technically can't support it, who should bear the cost—the platform or the proposer who followed the written instructions?

POLYMARKET DIGEST — 11 OCTOBER 2026 ⚠️ Bugs & Issues UFC markets: silvaselva reported that open orders are not being automatically cancelled before fights start — they are only cancelled after the fight ends. The old behaviour cancelled all orders before the first fight of the event began. Daily volume stats appear to not have been updated for two days, as flagged by alexapache. NOAA data appears to be down, affecting climate-related markets. The /trades endpoint is reportedly returning persistent 500 errors (mrbobbybeans). 📋 Clarifications Polymarket posted bulletin board rule updates for a large batch of KBO markets whose originally scheduled dates did not match their actual play dates. Key notes: — All affected markets will resolve according to the official KBO box score for the rescheduled date. — The KBO: Lotte Giants vs. KT Wiz (Aug 8 market) ended in a 2–2 tie after 11 innings and will resolve 50-50. — Several markets had incorrect start times displayed; the bulletins clarify that those displayed times belong to different games and do not apply. — The Google Gemini Pro market title was updated for clarity. 🔥 News & Announcements A planned infrastructure update (referred to as the "Rust CLOB" or CLOB v2 of v2) is expected to remove legacy wallet support. blunkoed noted that users will likely be forced to migrate, though no firm timeline was given. Legacy wallets (created before approximately May 2026) currently have a latency advantage; this edge is expected to disappear after migration. richlb_predict suggested the upcoming mm.clob.polymarket.com endpoint should equalise latency across wallet types. There is broader developer discussion around colocation (London vs. Dublin), with users debating whether 1–2 ms gains matter — phoenyx69 confirmed it matters for FIFO-sensitive bots but not for retail. taygunhope submitted detailed technical questions to Polymarket devs about post-only order evaluation, taker delay routing, accepted vs. rejected order latency, and batch endpoint sequencing; no official response was logged. kartojal acknowledged feedback from yasarhoca suggesting order queue visibility, partial order size reduction without losing queue priority, and a monthly subscription model for taker rebate tiers, and confirmed passing it internally. Will the Rust CLOB migration force out the latency-advantage traders who've been relying on legacy wallet speed, or will the new infrastructure truly level the playing field?

UMA DIGEST — 11 OCTOBER 2026 ⚠️ Bugs & Issues A scam message remained visible in #dispute-requests for approximately 3 hours before being removed. Users noted it did not self-delete as typical scam bots do. It was eventually dealt with ("Infinity woke up and hammered him"). A separate scam solicitation appeared later in the channel and was mocked by regulars. 📋 Clarifications A Dota 2 match between Kineti and NEM originally scheduled for 2026-09-01 was rescheduled, and a duplicate market was created for the rescheduled date (2026-09-08). stradiveri confirmed both markets should resolve the same way based on the match result. A soccer penalty goal dispute arose: a market was proposed as "No" despite the goal being scored within 90 minutes. mawyoo identified it as a mis-proposal, with alexchunus noting a penalty goal counts like any other goal. laurleo suggested the proposer may have confused the player's name (Bogdan vs. Bohdan). A question was raised about a tornado risk market for Chicago on October 9, 2026 — specifically whether it was incorrectly resolved given a 2% tornado risk for Tampa shown in SPC data. fernando5495 indicated it was fine. ⚡ Disputes A debate broke out over whether wallet 0x94f7 was frontrunning crypto proposals. evgeniykam (wallet 0xa6d3, recently whitelisted) accused the wallet of frontrunning based on mempool priority fee behavior. mebeim and joes49572 pushed back, arguing that for crypto hourly markets the data is trivial to source independently, gas wars are inevitable, and it is nearly impossible to prove frontrunning in this context. ng_7263 clarified that pool monitoring alone does not constitute frontrunning, and that frontrunning crypto requests would make little sense given how easy the data is to obtain. oscarlard, whose site was cited as evidence, stated directly that the accused wallet is not frontrunning, adding that crypto proposals are hidden by default on the site for this reason. evgeniykam stated they have forwarded the case to RL staff for review. Is frontrunning on trivial-to-source crypto data actually worth the gas fees, or are we seeing pattern-matching where there's just normal market competition?