Digest Polymarket & UMA Discord

POLYMARKET DIGEST — 10 NOVEMBER 2026 🔥 News & Announcements Protocol V2 Migration Delayed: The Protocol V2 migration, originally scheduled for November 9, has been pushed back by a few weeks (possibly up to a month). No new date has been officially announced. Users in #v2-migration and #devs are frustrated by the lack of official communication from the team. Climate Market Cuts: ak504111 announced that several lowest-temperature market cities are being cut due to low volume and demand. Cities being removed: Guangzhou, Chongqing, Busan, Cape Town, San Francisco, Toronto, Istanbul, Chicago, Wuhan, Atlanta, Buenos Aires, Qingdao, Taipei, Dallas, and Lucknow. High-temperature markets are not affected for now. ak504111 noted that Hong Kong and Seoul are showing strong interest, and cities could return if demand recovers. A UI sorting bug affecting climate markets was also reported and later confirmed fixed by ak504111. ⚠️ Bugs & Issues The Android app "Save" button for bookmarking markets is missing. taimoor789 has been reporting this for four days with no response from the team. The news tab bug also remains unresolved. A new withdrawal allowlist setting is not appearing for some users (reported by deemonrider). 📋 Clarifications 2026 Rio de Janeiro gubernatorial markets: Polymarket updated rules for all related markets (Douglas Ruas margin bands, Eduardo Paes, and "Another Candidate"). If no second round is held, or results are not definitively known by June 30, 2027 at 11:59 PM ET, all markets resolve to "Other." Valorant – Bonkers vs MeatZn: The referenced Upper Bracket Final never took place (MeatZn lost to CECIL in the semis). The subsequent Lower Bracket Final between the same teams does not count. Market considered canceled; all underlying markets resolve 50-50. Call of Duty – FaZe Vegas vs M80 Boston: The referenced Monster Launch Invitational Group B match was not part of the official Group B schedule. The teams met instead in a Group B Elimination Match, which is a separate event and does not count. All related markets (BO5, Game 1–4 winners, total games O/U 3.5 and 4.5) resolve 50-50. ⚡ Disputes Miami lowest temperature market (72–73°F vs 74–75°F): A dispute is ongoing over a METAR reading of 72°F at Miami Airport on November 7, which would place the result in the 72–73°F bucket. One side (suooshi, error403kabaaperror, energetic_raccoon_69364) argues the METAR data is the official resolution source and was not revised, so 72–73°F should stand. They contend a 1°C variation is within normal range and not "clearly erroneous," and that overriding it without a source correction makes the rules arbitrary. The other side (sam46, beefslayer__, modali1, maskache07) argues the 72°F reading was an operational error: all other qualifying observations for that date — including minute-by-minute NOAA/Iowa State University records — show the low never dropped below 74°F, with a 75°F reading at 3:53 AM. Per market rules, if the resolution source publishes clearly erroneous data, the market may remain open up to 7 days awaiting correction; if no correction is made, it resolves based on other qualifying observations, pointing to 74–75°F. Market prices are currently reflecting the 74–75°F outcome. The 7-day correction window is still active. Given the conflicting temperature data and ongoing dispute, do you think METAR readings should remain the ultimate authority for weather markets even when other data sources suggest they're wrong?

UMA DIGEST — 10 NOVEMBER 2026 📋 Clarifications Two NBA prop markets from the DEN vs HOU game (2026-11-09) are under discussion: Jokic Assists market: A dispute was filed after the box score initially showed 8 assists, then updated to 9. zjeed filed the dispute believing the final total would be 9; rex416 also disputed. The game book confirmed 9 assists. zjeed acknowledged it may have been premature if the book updated on its own. Sengun Rebounds market (11.5 line): A more contentious situation. The NBA.com box score showed 11 rebounds at the buzzer but corrected to 12 over an hour later. im.the.wizard noted his logs captured 11 at game end, while the official NBA game book PDF shows 12. rex416 argued the resolution source (NBA.com box score) read 11, while im.the.wizard and alexchunus maintained that stat corrections count and the official scorer's report (game book PDF) showing 12 is the authoritative source. im.the.wizard noted he asked the UMA team, who responded they were "looking." alexchunus pointed out there is no "no updates considered" clause in the market rules. The market was approaching settlement with no final ruling posted yet. If stat corrections happen after the initial box score closes, should markets resolve to what was published at game end or to the official final count in the game book?

POLYMARKET DIGEST — 9 NOVEMBER 2026 ⚠️ Bugs & Issues Protocol V2 migration delayed: The WebSocket migration to Protocol V2, originally scheduled for November 9, was delayed with no new timeline announced. blunkoed noted the lack of any official announcement from the team. Canary V2 markets (polyv2-*) are live but have essentially no liquidity, making integration testing difficult. Developers are advised to consult the official migration docs for now. Ghost fills / phantom liquidity: An ongoing matching engine issue is generating significant discussion. moonshotnft reported that a single entity operating 150+ wallets is flooding order books with orders unbacked by sufficient capital, disrupting the matching process for legitimate fully-funded orders. The debate centers on whether capital reservation per-order would help or hurt real liquidity. diggeryay confirmed the team is aware of the problem. Some users expect the upcoming V2 (Rust-based CLOB) to address it, though hellbot632 argued the root cause — the gap between off-chain matching and on-chain settlement on Polygon — won't be fixed by the new engine alone. Market sort order broken: david_ev reported that market brackets (Musk tweet, oil, etc.) are now sorted by descending price instead of the previous default sort order. Missing "Other" option: fulegods flagged that at least one market references resolving as "Other" if no specific outcome occurs, but that option does not exist in the market. 📋 Clarifications Puffpaw (VAPE) FDV markets: Polymarket posted bulletin board updates for all five Puffpaw FDV threshold markets ($50M, $100M, $200M, $300M, $400M). VAPE became transferable on November 6, 2026, making "1 day after launch" = 4:00 PM ET on November 7. The most liquid source was the VAPE/USDC Uniswap V2 pool; at Ethereum block 26365528, VAPE was priced at ~$0.361, giving an FDV of ~$361M. No minimum liquidity requirement applies. This means markets set above $361M resolve No, those at or below $361M resolve Yes. Miami lowest temperature (November 7) — active dispute: Polymarket invoked the Erroneous Data provision and ruled that the 22.4°C (72°F) reading in the 0853Z METAR for KMIA will not qualify for resolution. The 1153Z METAR's 6-hour minimum (23.3°C) and the November 8 0453Z METAR's 24-hour minimum (also 23.3°C) both contradict the 72°F reading. The affected markets ("lowest temp 72–73°F" and "74–75°F") will remain open until November 14, 2026, 3:53 AM ET to allow AWC to publish a correction; if no correction appears, resolution will be based on the other qualifying observations. Houthis entering Saudi Arabia: Polymarket clarified that mere announcements, threats, or repeated claims without independent verification do not constitute entry. As of the ambiguity period end (November 3, 11:59 PM ET), credible reporting did not establish a qualifying Houthi entry for the "by October 31" market. The "by December 31" market remains open with the same standard applied. Bundesliga player props (HSV vs. Mönchengladbach, Nov 6): Bundesliga published official match data within 2 hours of the final whistle, confirming it as the primary resolution source for all related player prop markets (Joe Scally assists/goalscorer, Robin Hack shots/goals+assists/goalscorer, Daniel Fernandes saves). ⚡ Disputes Miami lowest temperature — 72°F METAR reading: This is an active community dispute that preceded Polymarket's clarification. Disputing the reading (beefslayer__, maskache07): The 0853Z METAR value of 22.4°C is physically inconsistent — the AWC source itself reports a 6-hour minimum of 23.3°C covering that period, and Iowa Mesonet 1-minute ASOS data never recorded a temperature below 74°F at KMIA that day. The initial METAR at that time showed 75°F before being replaced with the anomalous 22.4°C value 20 minutes later. Defending the reading (suooshi, modali1): A 2–3°F discrepancy between observation sources is within normal meteorological variation for Miami and has occurred previously without dispute; Wunderground and PWS sensors near the airport also recorded 72°F; only the AWC T-group data should be used for resolution; and disputing such small differences would destabilize weather market liquidity. Polymarket sided with the disputers, ruling the value erroneous. An UMA vote has also been filed on the matter. If ghost fills are truly the matching engine's core issue, can Protocol V2's Rust-based CLOB actually solve it, or will the Polygon settlement gap still cripple legitimate traders?

UMA DIGEST — 9 NOVEMBER 2026 🔥 News & Announcements The Puffpaw token launch market has resolved. infinity_d sent the proposal with the answer directly and stated it would not be extended — users note this was done in coordination with Polymarket. The P4 dispute by car_poly's followers failed; multiple users (mebeim, sam46, abhiz69) note infinity_d had repeatedly signaled the alert/proposal was correct, and car_poly did not spend his own money disputing. The token's VAPE launch was ruled valid: it is not an LST, not a synthetic token, and not a memecoin of itself under the rules. Riga FC vs RFS was cancelled after Riga FC failed to show up. Some markets were proposed (apparently by the UMA/Poly wallet). abhiz69 clarified that because the Y bracket was already settled in a negrisk group, the other brackets are contractually forced to N and cannot be disputed post-settlement. infinity_d reminded users that if they spot something wrong, they should still dispute regardless of whether the proposer appears to be the UMA team. COD (Call of Duty) P3 proposals have been extended for over 28 hours according to rex416., who noted this may be a record. ⚠️ Bugs & Issues The Faze Vegas vs M80 market remains stuck with an unusually long extension, with no resolution yet. No technical explanation was provided. ⚡ Disputes KMIA Miami weather dispute (72°F reading): gum5683 disputed a Miami weather market where the resolution source recorded 72°F, while other sources showed 74°F. beefslayer__ laid out five independent lines of evidence that the 72°F METAR reading is a clear technical error: 1. The resolution source's own 6-hour min/max (20233 group in the 1153Z METAR) shows the minimum was 23.3°C = 74°F, making 72°F impossible. 2. The AWC cache file, NWS API, and IEM archive all retain the original 75°F reading; only AWC and NWS timeseries were updated to 72°F, with no COR indicator. 3. The CLI daily minimum is 74°F at 3:45 AM, computed from every minute of the day. 4. The T-group encodes 22.4°C, which is not a value an ASOS station like KMIA can produce (ASOS works in whole °F). 5. 5-minute ASOS data shows 75°F at 3:50 AM and 3:55 AM, making a 3°F drop and recovery inside the same 5-minute window physically implausible. modali1 countered that the team previously accepted a 1–2°F METAR discrepancy as not impactful enough to trigger the technical error clause, and that the CLI report had already been ruled out as a resolution source. The dispute invokes the rule allowing markets to stay open up to 7 days when the resolution source publishes clearly erroneous data due to technical error — the same rule applied in the Cape Town error on October 18. Early soccer proposal dispute (im.the.wizard): A proposal by im.the.wizard was disputed on the grounds it was submitted 1 second before the official resolution source timestamp. im.the.wizard argued the timestamp actually supported his proposal but was not visible in the UI, and that nobody argued in the thread. protinam1632 noted they were not allowed to post in the thread at the time and said they would accept the bond loss, but pointed out other proposers have been more egregiously early. alexchunus confirmed early-proposing cheating is widespread in soccer markets but only catchable via timestamps. 📋 Clarifications Negrisk settled brackets: alexchunus clarified that once a Y bracket settles in a negrisk group, all other brackets are contractually forced to N — this is enforced by the smart contract and cannot be overridden by a clarification. A proposal made after Y settles is always correct and not P4. A proposal made before Y settles but disputed after is P4, judged at the time of proposal. Early proposals and resolution sources: alexchunus explained that for block timestamp purposes, a proposer must submit a transaction approximately 1.75–2.25 seconds before the block timestamp to be included, meaning a proposal appearing 1 second early by block timestamp was likely 3+ seconds early in real time. The organizer's official social media posts (not individual team accounts) can qualify as a valid resolution source trigger, though rulings vary. Which is more problematic in prediction markets: technical errors in the data itself, or people gaming the system by knowing the exact timing rules?

POLYMARKET DIGEST — 8 NOVEMBER 2026 ⚠️ Bugs & Issues A persistent sorting bug remains unresolved, with users still reporting issues. Separately, several traders are experiencing significantly degraded CLOB performance: berth6833 reported an unusually high number of timeouts, and 001_raghav noted median round-trip times nearly doubling since the weekend (307ms on weekdays vs. 568ms on weekends). A bot developer (iantaw) reported taker orders taking up to 2.5 seconds to fill despite only 15ms ping to Polymarket servers hosted in Ireland; jungle_jo noted the 150ms taker delay and that the matching engine slows on bursts, while hellbot632 suggested the issue may be on the bot's side. A UI bug was also reported where a user nearly accidentally placed offsetting +1/-1 positions in a market. stefo9260 escalated a support ticket open since October 24 — itself a follow-up to a previously "resolved" ticket — with no response from the team despite contacting a moderator. A mod eventually offered to help via DM, but stefo9260 reported the DM could not be delivered. 📋 Clarifications Two Houthis/Saudi Arabia markets ("by October 31" and "by December 31") have active disputes. Polymarket announced that any clarification would be issued at 5 PM ET on November 7, and that order books would be cleared at that time regardless of whether a clarification was made. Multiple UFC Fight Night markets (Jonny Parsons vs. Jose Henrique) had their titles corrected: "Jose Henrique" has been updated to "Jose Souza" across all related markets. Regarding KMIA weather data: a disputed METAR reading appeared at 3:53 AM showing an anomalously low temperature (72°F), issued without a correction (COR) flag just two minutes after the original. hermie_28217_08100 explained the sequence of events, noting that no other data source agreed with the reading. ak504111 ruled that AWC remains the sole resolution source and that uncorrected replacements still count: "The report the resolution source shows for a given observation time is the one that counts, whether or not it is marked as a correction." The case has been flagged to the team. beefslayer__ later argued the METAR was erroneous, citing the CLI report for MIA showing a daily low of 74°F — meaning no legitimate observation could have been lower. Users are pressing for a clearer definition of what constitutes a "technical error" in weather data (e.g., whether a 5°C anomaly would qualify), but no firm threshold has been established. 🔥 News & Announcements chickenwing_14999 flagged an upcoming fee hike on Polymarket's US platform. blunkoed urged the team not to raise fees until the new CLOB is delivered, noting poor platform reliability over the past year. There is also unconfirmed community chatter that roughly 30% of Polymarket staff may have been laid off, which some users are linking to delays in the new CLOB rollout. With CLOB performance crashing and support tickets stuck for weeks, is a fee hike really the right move before fixing the infrastructure?

POLYMARKET DIGEST — 7 NOVEMBER 2026 ⚠️ Bugs & Issues A widely reported bug caused market outcome brackets to be sorted by probability/price instead of their natural order. This affected ordinal markets (like temperature ranges) the most, with users reporting accidental wrong purchases due to shifting positions. kurwamach. escalated feedback to the markets team and ak504111 confirmed a fix is in progress. The fix appeared briefly for some users then reverted. A workaround was shared: open the market in a new tab, leave it for ~5 minutes, then return — brackets should reorder correctly. A separate issue was reported with CS2 IEM matches: some games show live score data via grid.gg while others do not, leaving scores invisible for affected matches. walem flagged that a queue-jump / tiebreak exploit in the CLOB — previously patched around August — appears to have resurfaced, apparently reintroduced by a recent CLOB upgrade. This was observed on NBA sports markets. The "Save" button is missing for some users, and the Home button fails to redirect to the homepage. lamp_ai suggested clearing cache as a workaround. mcxboi raised a broader infrastructure complaint: Polymarket's developer changelog is unreliable and inconsistent. Specific examples cited: the Data API v1 retirement was listed as Nov 2 in the changelog but actually broke on Oct 24; Protocol V2 market rollout dates were only found in third-party crypto news, not official docs; and a rule change announced on Discord by Suhail on Oct 2 never appeared in any official changelog. blunkoed agreed this is a real problem and tagged a staff member requesting the changelog be kept up to date. 🔥 News & Announcements The new CLOB (v2) is currently expected to enter market-maker testing later in November, with a broader release estimated for late December or early January — though berth6833 and others are skeptical, citing slow past delivery. blunkoed noted it will roll out in two phases, starting with a small group of participants. Tornado daily weather markets have been removed due to insufficient trading volume, confirmed by ak504111. 📋 Clarifications Ongoing discussion in #devs confirmed that Exchange V2 / Protocol V2 markets have not yet been rolled out to crypto markets as of Nov 6 — all 134 open crypto markets on Gamma remain on v1. The originally stated target of Nov 2 appears to have slipped with no official updated timeline. Colocation latency remains a persistent issue. Users from Dublin report p50 HTTP response times of 600–700ms for order placement, while up0rabn1k reports 40–50ms from the same location. The consensus is that the current CLOB performance will not meaningfully improve until the new CLOB releases, as CloudFlare cannot be bypassed. How many markets have you accidentally bought the wrong outcome on due to the bracket sorting bug before finding the workaround?

UMA DIGEST — 7 NOVEMBER 2026 🔥 News & Announcements infinity_d clarified that the Puffpaw token launch (Dec 31 2026 / Mar 31 2027 markets) appears valid: the token contract is live on Ethereum, a Uniswap V2 pool was created at 4:07 PM ET by a wallet funded directly from the token contract, and user claims opened at 4:28 PM ET. infinity_d stressed this was not a dispute request and tagged proposers, not disputers. However, several users raised red flags — scriptlin_55968 noted Puffpaw has a dedicated "polymarket-mission" Discord channel, suggesting coordinated manipulation, and cercoo confirmed the project airdropped tokens to users who bet the FDV would exceed $50M on Polymarket. mebeim declined to propose, citing scam concerns. ⚠️ Bugs & Issues im.the.wizard flagged that NBA proposals are being submitted early — specifically before final reviews at the end of games are completed. In the Jazz vs. Mavericks game, a proposal was made while the final play was still under review. The game book ultimately supported the proposal since the call was not reversed and no timestamp was adjusted, so no dispute was filed this time. im.the.wizard warned this will eventually cause problems if added time is reflected in the book. 📋 Clarifications A dispute is ongoing over a Bundesliga goalscorer market (HSV vs. Moe, Nov 6). ivaaansiito argues the goal was scored by Robin Hack, not Joe Scally as listed in the resolution source. abhiz69 countered that the resolution source lists Scally, making it difficult to dispute. ivaaansiito requested an extension or a dispute. An earlier incident involved a proposer who submitted an earnings-related proposal ~9 minutes before the official release, apparently by guessing/scraping a publicly accessible URL containing the earnings document. alexchunus noted the stock market did not react to the early document — only to the official release — and that the proposal was therefore premature. enormouz noted the stock was illiquid and the proposer likely could not have profited anyway, but called the early proposal "quite stupid." ⚡ Disputes A geopolitical market concerning Saudi Arabia / Yemen (Houthi) border activity is contested. raskell1 proposed YES, arguing that late-October entry claims are corroborated by Houthi sources, STC Yemenis, and Western and Arab officials, and that Saudi Arabia routinely avoids confirming such incidents for political reasons. armanh01 and mebeim questioned whether there is sufficient media consensus, with mebeim noting a lack of broad reporting. rex416. called for a clarification. alexchunus noted price arguments have historically been used in UMA and voters factor them in. raskell1 requested an official clarification to resolve the dispute. Given the Puffpaw token launch showing multiple red flags — dedicated Discord coordination, airdrop incentives for specific predictions, and proposer hesitation — do you think markets with this kind of pre-coordinated community backing should require additional verification steps before resolution?

POLYMARKET DIGEST — 6 NOVEMBER 2026 🔥 News & Announcements Security Warning: chrund1e posted an official security reminder warning users about active malicious campaigns on Discord, Telegram, X, and other platforms. Threats include fake trading bots, wallet-recovery tools, malicious bookmarklets, Polymarket clone sites, and fraudulent GitHub repositories. Users are reminded never to paste code into their browser, share seed phrases, or install unverified tools. Full advisory pinned in #announcements. Earlier, a reported "active hack siphoning funds" (musuc_00947 / petatechsolution) was investigated by pmkeaton, who confirmed there was no threat — just a misunderstanding. ⚠️ Bugs & Issues Market sorting broken: A UI change caused all market brackets (temperature, tweet, and others) to be sorted by price instead of their natural order. hans32312 confirmed this affects all market types. Multiple users have complained it is confusing and potentially misleading. ak504111 flagged the issue internally but noted it is not their decision to revert. Users are requesting a rollback or a toggle option. Perps UI not updating positions: cenas5780 reported that the perps interface fails to update position values when adding to an existing position, leaving orders only controllable via stop-loss or take-profit. gamma-api TLS reset (~50% failure rate from India): mind_boss reported that gamma-api.polymarket.com resets TLS connections right after ClientHello with curl error 35, affecting ~50% of requests from India. clob.polymarket.com on the same IP works fine. Dota 2 market unresolved for 3+ days: .fomo flagged that a Dota 2 Game 2 market remains unresolved and pinged moderators. News tab bug still unresolved; viniipaquete expressed frustration, and kurwamach. confirmed they have pinged the team again. KYC/colocation delays: Multiple users (petatechsolution, exuberant_lynx_38171) report waiting 2+ months for co-location KYC approvals with no response. 📋 Clarifications Trump / Ken Paxton insult market resolved YES. Polymarket ruled that Trump's comment — "he can be a pain in the ass sometimes. I'll be honest." — qualifies as a public insult under the market rules (mocking or disparaging an individual personally or professionally). Order book was cleared at 4:00 PM ET on November 5. Buenos Aires temperature markets (Nov 5): The anomalous 17:00Z SAEZ METAR reading 2710 (missing slash, no valid temperature) was ruled not erroneous data and disregarded entirely. All Buenos Aires temperature bracket markets (22°C–32°C+) will resolve based on the remaining valid METAR observations. Subsequent valid 27°C readings were confirmed. AHL: Wilkes-Barre/Scranton Penguins vs. Charlotte Checkers market was archived and resolved immediately to Charlotte Checkers. Net losing positions at the time of the clarification will be refunded. ⚡ Disputes Buenos Aires METAR typo edge case (ongoing discussion): A missing slash in the 17:00Z SAEZ observation (2710 instead of 27/10) sparked debate about whether such typos should be excluded, treated as erroneous data (triggering a 7-day wait), or resolved via clarification. hans32312 argued airports' mistakes should simply be excluded under the rules. ak504111 cited the rule that observations reporting no temperature are disregarded, and that corrections remain valid until the first datapoint of the following day. The practical impact was moot since later valid 27°C readings were published — but participants flagged it as an unresolved edge case for future markets. With market sorting broken and multiple critical bugs piling up, is Polymarket's technical team stretched too thin, or are priorities just misaligned?

UMA DIGEST — 6 NOVEMBER 2026 ⚠️ Bugs & Issues A user raised a potential issue with UMA markets related to a "Victor Jensen" player: im.the.wizard initially flagged that Victor Jensen did not appear on either roster and suggested markets should resolve 50-50, but later self-corrected — the player is listed as Victor Bak Jensen, causing the confusion. There also happens to be a separate Victor Jensen (Danish) on Utrecht, which added to the mix-up. No dispute was ultimately filed. 📋 Clarifications A question was raised about how Polymarket handles users who took positions before market rules were changed. The general sentiment from users was that Polymarket rarely compensates affected users, though refunds have occurred in some specific cases. A timing dispute around the Israel-Iran ceasefire market (potential P4) was briefly raised but dismissed — it did not meet P4 criteria. The Putin meets Iranian officials by November 15 Polymarket market was flagged for potential dispute since no meeting had yet occurred, but yura.w1 linked a Reuters report confirming Putin met with Iranian Security Council chief Rezaei in Moscow on November 5, apparently settling the question. ⚡ Disputes An active debate is ongoing over whether Trump calling Ken Paxton a "pain in the ass" qualifies as an insult for resolution purposes. wang02272 argued it clearly does, drawing a parallel to the Netanyahu case where Polymarket's own clarification counted similar language as an insult despite surrounding praise. aenews and victogut agreed "pain in the ass" is unambiguously negative. emeraldedge_ argued context makes it non-insulting, comparing it to "difficult" (which was previously ruled not an insult). jenia_13 stated they lost $2,000 on the market and that only Polymarket's clarification interpreted the language as an insult. No formal dispute has been filed, partly because laurleo noted it needs 75% odds to be profitable. jenia_13 sought a co-disputer to split the bond cost. If "pain in the ass" counts as an insult in one market, should the same language resolve the same way across all similar markets, or does context matter every time?

POLYMARKET DIGEST — 5 NOVEMBER 2026 ⚠️ Bugs & Issues Site performance degradation: fab5780 reported that from ~00:00 UTC, Polymarket became significantly slower — order response times rose from 70–110 ms to 143–284 ms (p90), 2–4% of orders failed with "order timed out", and only ~20% of quotes actually landed on the book (vs. ~50% normally). aryankhaunte confirmed the slowdown. A separate user also reported deposits stuck as "in progress." Notification delays: holographd flagged a long-standing unresolved issue where limit order fill notifications arrive minutes to over an hour late. Co-location 403 errors: xi_vint reported that their eu-west-2 co-location was approved on Oct 29 and whitelisted Oct 30, but orders from that server are still rejected with a 403. No staff response was provided. makmed1337 and fackkito noted their co-location requests submitted in September and October have also received no response. FOK order latency spikes: becksinc described a detailed issue where FOK orders via CLOB API take 1.5–1.8 s during volatile periods and are killed as unfilled, despite WebSocket book data showing sufficient liquidity at the limit price for ~1.4 s. Other takers were filling at those prices during that window. habitual_revers (staff) confirmed that taker delays start only when the order is picked up by the matching engine, that queues can back up, and that deeper timing metrics are not currently exposed. New undocumented error message: floaty_boi noticed a new error — "order {orderId} crosses the book" — appearing without prior notice, breaking bot logic. Community consensus settled on it being a self-trade prevention trigger. Maker rebates not received: dicer6216 reported not receiving maker rebates for Monday and Tuesday despite hundreds of executed post-only orders on midterm and CS2 markets. hft_pro noted rebates are paid once daily at UTC 00:00 +15–45 min and suggested checking via the /rebates/current endpoint. Chainlink API keys deactivated: artex6666 reported receiving 401 user disabled on Chainlink keys. sloiner confirmed the issue and suggested switching to Polybolt as an alternative. Impersonation scam: A scammer using the name gasuajax was spotted impersonating a staff member (gasuajex) in DMs. dontoverfit flagged it to moderators. 🔥 News & Announcements A rules update for Champions League matches scheduled on or after November 24, 2026 was posted, applying to all full-match, half markets, corners, and player props. No details on what changed were provided in the announcement, drawing complaints from users. There is ongoing community discussion about a CLOB v2 launch with no confirmed timeline communicated by staff. 📋 Clarifications LA-05 House seat markets: Multiple individual candidate markets (candidates A, B, C, D, E) were resolved No immediately after those candidates were eliminated from the election. Markets for the Democratic Party, Republican Party, and "another party" winning the seat remain open pending final results. With order latency spiking to 1.8s during volatility and fill notifications delayed by hours, how much edge are these performance issues actually costing active traders on Polymarket right now?

UMA DIGEST — 5 NOVEMBER 2026 ⚠️ Bugs & Issues An automated bot (likely im.the.wizard's) appears to have incorrectly proposed some House election markets, triggering disputes. im.the.wizard acknowledged the possibility, noting he may have been asleep when it happened. 📋 Clarifications Placeholder resolution rule changed: Polymarket issued a clarification ruling that placeholder outcomes (candidates not listed) can resolve No without waiting for a Yes to be proposed first. This reverses a long-standing precedent ("Jessica precedent") that had been used to P4-dispute placeholder proposals. Disputers who challenged placeholder proposals on these grounds lost their disputes. im.the.wizard called it a "good clarification overturning nonsensical Jessica precedent," while mebeim cautioned against treating it as a universal rule change, noting PM might issue a reverse-clarification if tested further. stradiveri noted this contradicts months of prior successful P4 disputes on the same basis. LaLiga suspended match (CD Tenerife vs FC Andorra): A market on this match was proposed as "Over" after the game was abandoned following a player being seriously injured (he died in hospital hours later, as infinity_d clarified). dyanreel initially requested a dispute citing the game was not complete per resolution rules. However, abhiz69 confirmed the match status on the resolution source was subsequently updated to "Full Time," and the dispute request was dropped. The market was advised to settle normally. ⚡ Disputes Player prop proposals mid-game: A debate emerged over whether player prop markets can be proposed mid-game (e.g., if a player is substituted out). im.the.wizard argued yes, citing MLB precedent where similar markets were ruled P1, and noting these prop markets lack a clause requiring resolution only at game's end. tenacious_mango_59265 and savagefin1252 pushed back, with savagefin1252 pointing out that MLB games cannot be cancelled past the 7th inning, making the parallel invalid. No resolution reached. Los Angeles mayoral runoff placeholders: Following the placeholder clarification, mebeim and others debated whether placeholder candidates in the LA mayoral runoff (a two-candidate runoff already voted on) are now freely proposable. mebeim declined to propose or dispute, citing the $750 cost and uncertainty about PM's consistency. alexchunus argued any dispute on such placeholders is now deeply negative-EV given the new clarification. 🔥 News & Announcements im.the.wizard confirmed that UMA V2 is launching within approximately 4–5 days, at which point placeholder mechanics will become largely irrelevant as all markets migrate to V2. Does the Jessica precedent reversal mean disputers should stop challenging placeholder proposals altogether, or is this clarification too fragile to rely on before V2 launches?

POLYMARKET DIGEST — 4 NOVEMBER 2026 🔥 News & Announcements Private Market Valuation Rules Update — Polymarket issued a large-scale bulk rules clarification across all private company valuation markets. Resolution language was standardized: markets resolve YES if the company's NPM Price (Nasdaq Private Market) hits the listed threshold at any point between market creation and the deadline (≥ for HIGH, ≤ for LOW valuations). Companies affected include OpenAI, Anthropic, Databricks, ByteDance, Stripe, Kraken, Anduril, Neuralink, Perplexity, Revolut, Glean, Lambda, Canva, and Epic Games, with Nov 30 and Dec 31, 2026 deadlines. This is a clarity-only update with no substantive change to resolution criteria. Additionally, U.S. 30-year Fixed-Rate Mortgage markets were clarified to use Freddie Mac weekly PMMS data, with a resolution deadline extended to January 14, 2027 if final-week data is delayed. Recent Resolutions: - Gemini Carbon top 10/5/3/1 debut in Text Arena leaderboard by June 30, 2027 → YES - Gemini Carbon debut score ≥1520, ≥1530, ≥1540 → YES; ≥1550, ≥1560 → NO - Jay Z performs at 2027 Big Game halftime show → YES - Kanye West, Drake, Morgan Wallen, Taylor Swift, and numerous other artists performing at 2027 Big Game halftime show → all NO - Denver, CO snow by Nov 15 and Nov 30 → YES; by Oct 31 → NO - Gävle Goat burns in 2026 → NO - "Will NATO countries clash with each other before 2028?" → Voided/refunded to cost basis ⚠️ Bugs & Issues - Infinite scroll bug: polymarket.com/new loads only 20 markets instead of infinite scrolling. Partially acknowledged as fixed but still reported by users. - Elevated 429 errors on /v2/positions endpoint: Root cause is a rate-limit quirk that groups all callers sharing the default User-Agent: node header under a shared limit. Workaround: set a custom User-Agent header. Flagged to the team, not yet fixed. - Data API v1 retired: Callers receiving HTTP 410. Fix: migrate to API v2. - WebSocket Error 1013: Suggested fix is to switch to the beta WebSocket. - API tick size desync: API updates tick size before the CLOB actually changes, causing order rejections ($0.001 increment errors). Recommended workaround: use fixed tick size tables. - Profit display change: Redeemed positions no longer show profit in the position section. Unclear if intentional or a bug. - KDEN snowfall market: To be refunded due to missing/inconsistent data from the KDEN station (confirmed by staff). Note: NOAA stopped providing weather data, forcing a resolution source change for weather markets. No reliable source currently exists for international city rain/precipitation markets. - Account lockout: One user reported being locked out due to a Google Authenticator 2FA issue, with support case pending and unresolved. - Colocation KYC/KYB delays: Multiple users reported slow approvals; staff confirmed turnaround can be "a few business days." - Ireland/Dublin geoblock: UI trading from Ireland is blocked, but API trading is permitted. 📋 Clarifications US × Iran Ceasefire Markets ("through Oct 31" and "through Nov 2"): A clarification was issued Nov 3, 2026 at 5:30 PM ET. Reports of US strikes on Qeshm Island surfaced Oct 30 (Iran Standard Time), but the consensus of credible reporting placed the strikes in the early hours of November 3 IST — after both market deadlines. No qualifying military action was established before either cutoff, so both markets resolved as ceasefire continuing. Taker delay & matching lock (confirmed by staff): The 1-second taker delay runs concurrently across orders, so 10 simultaneous orders do not accumulate 10 seconds of delay. However, orders are still processed one at a time per account/market (risk re-check → matching lock → match). Matching-lock wait is p99 ~50ms under normal load, up to a few hundred ms at peak. On crypto markets, clients waiting for each response before sending the next order will accumulate delays — recommendation is to send bursts concurrently. Staff noted performance improvements are coming. Polybolt / RTDS latency: The paid Chainlink stream vs. Polymarket RTDS shows approximately 300ms difference. Polybolt websocket cuts latency roughly in half but does not resolve other RTDS gaps. v2 onchain fee cap: There is currently no onchain cap on principal plus fees. maxSpend sizes orders to fit the fee budget but is not enforced onchain. No plans for an onchain fee ceiling at this time. ⚡ Disputes - Esports market wrong resolution: User dikipiki reported a potentially incorrect resolution on an esports market and was seeking contact to file a dispute. No resolution recorded. - US × Iran Ceasefire: Disputed resolution period addressed via the clarification above; order books cleared at 5:30 PM ET Nov 3 regardless of outcome. If the private company valuations on NPM were to spike dramatically in the final weeks before the Dec 31 deadline, would you be positioning for YES or holding back to see if it's sustainable?

UMA DIGEST — 4 NOVEMBER 2026 🔥 News & Announcements The F1 champion market was settled, sparking debate. eip15942 argued the settlement was improper ("Earlier it was 'follow the rules,' and now suddenly the rules don't need to be followed"), while laurleo maintained that P4 (too early / unable to determine) remains the most reasonable outcome under the rules since the award has not been announced. The market remains disputable. ⚠️ Bugs & Issues A user (tt_tt00) reported losing their UMA balance due to missing votes without receiving a notification, contrasting with the existing notification for missed reveals. infinity_d responded that slash notifications are visible in results and documented, and directed the user to open a support ticket for a separate gas estimation error they encountered. 📋 Clarifications Somali pirates / commercial ship market: A dispute arose over whether a seized fishing vessel (the Azini) qualifies as a "commercial ship." utoya352 noted that sources such as MSCI/EUNAVFOR, AFP, and IMB consistently classify the Azini as a fishing vessel, a category separate from commercial/merchant ships, and called for a market clarification. armanh01 confirmed the same question applies to the Nov 30 bracket. US strikes on Iran (Oct 31 & Nov 2 brackets): usernamethr33 laid out the dispute in detail. US officials confirmed a strike on Iran on Nov 3 (Iran time), which does not qualify for the Oct 31 or Nov 2 brackets on its own. The crux is a "recent weeks" statement from officials. The Oct 31 Y side argues the 3-day waiting clause (triggered Oct 29 by an OSINT post later refuted) expired on Nov 1, meaning the bracket should have closed before the WSJ article appeared. The Nov 2 Y side argues the "recent weeks" language is too vague to attribute a strike to their window. The Nov 3–Nov 7 brackets are disputed on timing grounds only. ⚡ Disputes Portsmouth vs. Swansea City (EFL, final score 3–1): Several proposals were made at a 2–1 scoreline. savagefin1252 and jarmax provided backend data from the EFL's public Firestore feed showing Portsmouth's third goal (Waddingham) was recorded at 21:42:03 UTC and full-time at 21:43:27 UTC, with the site updating at 21:43:31 UTC. Any proposal made before 21:42:03 UTC therefore preceded the final goal. exquisite_wolf_79651 posted Wayback Machine archives of the raw EFL backend records as corroborating evidence. flame80887 began disputing the early proposals, stating he believes every EFL game in question was proposed on bad data. im.the.wizard countered that there are "a lot of bad disputes here" and suggested flame80887 may end up net negative. The dispute is active and ongoing. Russia targeting Kyiv (Nov 3): jduckyj proposed P4, citing insufficient evidence. With multiple markets hinging on precise timestamps and data sources, how much should settlement depend on backend records versus official announcements?

POLYMARKET DIGEST — 3 NOVEMBER 2026 🔥 News & Announcements Polymarket has launched its first Perps Trading Competition: $50K paid out to the top 50 traders on Polymarket Perps, with 3× boosted scoring on Anthropic pre-IPO ($ANT). The competition runs live through Nov 16. Join at: polymarket.com/r/perps-comp Several 2026 election markets have had their placeholder candidates replaced with real names, including races for Alaska Governor, California Governor, California Lt. Governor, Alaska Senate, Idaho Senate, Nebraska Senate, South Dakota Senate, Montana Senate, Rhode Island Governor, Michigan Governor, Los Angeles Mayor, and AK-AL House. Notably, the "Will Dick Durbin be the next Senate Majority Leader?" market was clarified: it actually refers to Chris Van Hollen, and references to Durbin in the oracle question should be read as Van Hollen. In climate markets, ak504111 confirmed that New York, Chicago, Seattle, and Boston have been intentionally removed from rain markets as the platform prepares to launch snowfall markets for those cities soon. ⚠️ Bugs & Issues Multiple users report being unable to initiate deposits via card or Google Pay. The refresh/recharge interface is also broken for some users. A bug limiting the new markets view to only 10 markets was reported; kurwamach confirmed it has been reported to the team. Users running WebSocket connections are encountering ConnectionClosedError (code=1013, slow consumer: send buffer full) errors even on healthy VPS infrastructure in unrestricted regions. This appears to be a server-side issue. Sponsored Chainlink API keys have expired; blunkoed requested the team begin reviewing forms to issue new keys. habitual_revers confirmed a significant CLOB infrastructure issue: the current engine has a per-account matching lock, meaning order submissions during high-activity bursts (e.g. BTC 5-minute markets) can see POST /order latencies of 150–260 ms median and p90 exceeding 1 second, even for post-only orders. There is currently no direct/colocation submission path available. This is expected to improve with the new engine. Cancel latency tail can also reach multiple seconds, making it mathematically difficult for makers to cancel in time. A separate issue was raised: when one wallet in a batch has insufficient funds, the entire transaction reverts rather than skipping the underfunded order. No fix has been announced. diggeryay flagged yet another taker delay bypass has appeared. 📋 Clarifications An ongoing #devs discussion centered on the 1-second taker delay. The consensus among active traders is that 1s is too high and is killing sports market volume — walem noted that markets which previously had 500K volume now sit at ~40K. Suggested alternatives ranged from 50ms to 300ms. laucyph3r argued that makers cannot be blamed for lack of skill when cancel latency spikes can themselves reach multiple seconds, making timely cancellation mathematically impossible regardless of strategy. No official change has been announced. On CTFExchangeV2: lynx038696 confirmed there is currently no documented hard per-order BUY spending cap covering principal plus all fees. Whether a nonzero getMaxFeeRate() ceiling will be restored has not been officially addressed. With the taker delay killing sports market volume, would dropping it to 50ms actually bring traders back, or is the infrastructure latency problem the real villain here?

UMA DIGEST — 3 NOVEMBER 2026 🔥 News & Announcements Polymarket issued a clarification resolving all Dota 2 markets related to the potn9ki vs HellNight- (EPC Season 3) match at 50-50 (P3), treating the match as not having started. This followed the Esports Pro Circuit disqualifying HellNight- from Season 3 and voiding all their Group Stage results. The decision is confirmed as irreversible by nik4456 and enormouz. Map 1 was separately noted as misresolved. A related ETH price market clarification was flagged as erroneous — one of the two required prices was missing from the text — and needs to be reissued. ⚠️ Bugs & Issues Multiple data sources (Dotabuff, Polymarket scoreboard, Valve API) showed conflicting or erroneous results for the Dota 2 match. No VOD was publicly available. Bonders reportedly had approximately $400–500k in shares at risk for roughly $500 in potential gain, and lost funds despite acting in good faith based on published results prior to the post-match DQ announcement. 📋 Clarifications User holymoses7 was granted access to dispute threads by admin infinity_d after reaching Discord Level 5. Dispute thread rules were posted: one message per thread per user, no replies, no personal attacks, good faith participation only, and no reposting. ⚡ Disputes Dota 2 / CS2 Post-Match DQ Dispute: The core disagreement is whether a post-match disqualification voiding all results should be treated identically to a mid-match DQ. effpwnz and stimeronis argued market rules explicitly state that if a match begins but is not completed and one team wins due to the opponent's disqualification, the market resolves to the winning team — and game logs confirmed an in-game admin message at 39:48 halted the match, awarding potn9ki a technical victory. mebeim, syrupfund, and gum5683 countered that the previous CS2 precedent (P3) involved a DQ during a live match, not after full completion on Dotabuff. Polymarket's 50-50 clarification stands regardless. Broader community concern was raised that proposers acting correctly are losing bonds due to post-match organizational decisions entirely outside their control, with some calling for Polymarket to reimburse Game 1 bets. F1 2026 World Championship Market Dispute: Kimi Antonelli was declared champion after the Mexico City race per FIA sources, and a "Yes" resolution was proposed before the final scheduled race of the season. eip15942 and gum5683 disputed this as premature (P4). Market rules explicitly require waiting for the final scheduled race result before resolving "Yes," though early "No" resolutions are permitted — a distinction 7h0nk3r and abhiz69 called inconsistent. laurleo, mebeim, and enormouz cited IndyCar precedent and the existence of an "Other" bracket for edge cases, supporting P4. The market is now double-disputed with placeholder and Other outcomes also proposed; resolution is expected after the final race next month. When markets resolve based on organizational decisions made after competition ends, should the rules protect bettors who acted on real-time game data, or stick strictly to final official outcomes?

POLYMARKET DIGEST — 2 NOVEMBER 2026 ⚠️ Bugs & Issues Several users reported platform problems over the past 24 hours. The Polymarket website was briefly non-responsive early on November 1. data40. reported that the Watchlist button has disappeared from the homepage on the web version; clearing cache and cookies did not resolve it. ak477777. was unable to place orders, darko5586 could not deposit crypto (no deposit address shown), and stefo9260 reported that wallets previously "approved for colocation" are no longer working — tsmultra asked them to send details via DM. Users noted that order matching latency has been elevated, with pepesong reporting 150–170ms averages from a colo box; 001_raghav noted latency has been above 300ms for the past week. 🔥 News & Announcements The V2 migration has been postponed to November 9, according to a link shared by blunkoed pointing to the official @polymarketdevs Twitter post. Questions remain open about whether existing markets will be migrated to V2 or only new markets launched on V2. A user (exquisite_puppy_15167_76707) was promoting an unofficial affiliate rebate scheme in #devs, claiming to offer 10–18% additional rebates on top of existing taker rates via a "personal connection" to Polymarket. The offer attracted skepticism from other users. Treat this as a likely scam — ransom0669 also warned others that scammers were DMing them immediately after posting. With the V2 migration delayed to November 9, do you think the platform will have fixed the wallet approval and deposit issues by then, or could launch day be chaotic?

UMA DIGEST — 2 NOVEMBER 2026 🔥 News & Announcements Multiple disputes were active simultaneously, raising concerns about "block proposing" — where users submit several related markets at once, making it financially prohibitive to dispute all of them given the $750 bond per market. armanh01 suggested reducing the bond, while 7h0nk3r criticized the broader pattern of rushing proposals before resolution conditions are clearly met. UMA.Rocks governance concerns were also raised: armanh01 noted its influence has diminished following recent clarifications, and 7h0nk3r alleged paid voting by a specific member. Bribery allegations were described by armanh01 as "blown out of proportion." ⚠️ Bugs & Issues - holymoses7 was unable to post in the UMA disputes channel due to insufficient server level (requires level 5+) and requested moderator access. They also reported being targeted by an impersonator/scammer via DMs. - Some proposers (e.g., flame) have been submitting NFL total TD markets immediately after games, before the official gamebook is posted. Rules require the gamebook as the source; the issue is expected to stop now that it has been flagged. - The MrBeast video views market was flagged by marydavis552 as having been proposed approximately one hour early. 📋 Clarifications NBA "Other" option: daring_otter_72707 incorrectly claimed there was no "Other" resolution option in the Zach LaVine/Fred VanVleet markets. laurleo clarified that "Other" exists but is invisible to traders unless Polymarket makes it tradable. Post-roll procedure: jenia_13 raised concern that allowing a second comment after a rolled vote is prone to manipulation; armanh01 confirmed this is standard post-roll procedure. ⚡ Disputes Trump "Burger" Market — Did Trump say "burger" in October? Proposed No; disputed twice (including by aenews). Evidence surfaced of Trump saying "HAMburger" with audible stress on "ham." The core question is whether "hamburger" counts as saying "burger." The YES side argues Oxford/Merriam-Webster recognize "burger" as a productive morpheme (as in cheeseburger, portobello burger) and cites a precedent where "transgender" counted for "trans." The NO side counters that "hamburger" etymologically derives from Hamburg+er (German city), and that under current rules, closed compounds only qualify if the target word is a distinct component — derivations and alterations are excluded. 7h0nk3r argued that even under a rebracketing account, "-burger" would be a bound morpheme, explicitly excluded by rules. emeraldedge_ noted a prior MrBeast market listed "Burger/Hamburger" separately, suggesting Polymarket itself distinguishes them. ovr claimed to have evidence for YES but refused to share it, drawing widespread criticism. The market had already been extended once; trading volume is low (~1.6K), suggesting consensus leans No. Zach LaVine (Kings) & Fred VanVleet (Rockets) NBA Markets Both markets were proposed to resolve to the players' current teams. A template clause stated: "If the player does not officially join a new team, this market will resolve to 'Other.'" The dispute argument holds that neither player joined a "new" team — both exercised existing contract options — so resolution should be "Other." The counter-argument is that exercising a player option constitutes joining a team, and precedent supports YES for players who re-signed. Both markets remain contested. Benny Gantz Israeli PM Mandate Market jenia_13 proposed No, arguing Israeli Basic Law requires the president to assign the mandate to a Knesset member, and Gantz is not one. A dispute was filed on the grounds that the president has not yet assigned the mandate to anyone, meaning low-probability scenarios remain open and resolution is premature. 7h0nk3r agreed the proposal was too early. General community consensus: bad proposal. US Sanctions on China by October 31 Proposed YES based on an Oct 27 Federal Register notice suspending visa-free travel to CNMI for PRC nationals, effective Oct 30, citing national security. The NO side argues revoking visa-free status is not a travel ban or visa restriction, was not announced by OFAC, and no publication calls it a sanction. 7h0nk3r (bonded YES side) counters that the rules explicitly include "travel bans and visa restrictions," this was an affirmative government action targeting PRC nationals for national security reasons. liquidateddegen and rex416 were seeking co-disputants to split the $750 bond. BOS vs ORL Q3 End Time Q3 appeared to end at ~5:28 per the NBA gamebook, but the live scoreboard briefly showed "end Q3" then reverted; substitutions occurred after 3 free throws with 1.3s remaining, and the Magic had time for a half-court heave. Disputed via UMA v2 (2-hour window) with evidence posted in the dispute thread. laurleo separately lost $750 on a mistaken dispute related to Pacific Time / Daylight Saving Time confusion, having proposed a market believing midnight PT had not yet passed when clocks had already changed. If "hamburger" contains "burger" as a morpheme, should every word with a productive component count toward resolution — or does the distinction between standalone words and compounds matter?

POLYMARKET DIGEST — 1 NOVEMBER 2026 ⚠️ Bugs & Issues Chainlink price feed jitter: Multiple users reported severe jitter/fluctuation in Chainlink crypto price streams throughout October 31. floaty_boi shared a visual comparison showing the anomaly. pmkeaton confirmed: "we've made the Chainlink team aware of the jitters." The issue appeared to improve on its own around 21:50 UTC, per ca1138. CLOB/WebSocket performance degradation: Widespread complaints about CLOB reliability — users reported 300ms–2s order matching latency, frequent cancel timeouts, and WebSocket error 1013 (slow consumer: send buffer full). berth6833 noted the situation is worse than during the World Cup period despite lower current volume. The last day of a fee promo was cited as a contributing factor to congestion. The Beta WebSocket connection limit of 10 was flagged as insufficient for production use; habitual_revers asked for more specific feedback on what limits would work. Crypto Up/Down markets skipped around US DST change: fly33499 flagged that Polymarket skipped BTC Up/Down markets (5m, 15m, 1h, 4h, daily) around the November 1 US daylight saving time change, as the 1:00–2:00 AM ET hour occurred twice. Bot operators are advised to handle missing market slugs with a skip-and-backoff strategy rather than tight retry loops, and to align 4h/daily schedules to ET. Saved markets icon missing: taimoor789 reported that the save/bookmark icon for markets has disappeared from the home page. 2FA login issue: haroon22 reported being locked out due to Google Authenticator codes being rejected and no recovery code available. tsmultra asked for a DM with the profile address to investigate, and reminded users he will not DM first. Did the Chainlink jitter and CLOB latency issues impact your trading decisions on October 31, or did you manage to avoid the worst of it?

UMA DIGEST — 1 NOVEMBER 2026 🔥 News & Announcements A proposer suffered significant losses after proposing the wrong match for Rangers FC vs. Aberdeen FC Scottish Premiership markets — the game referenced was not the correct league fixture (it was for the November 24 match, not the cup game played on Oct 31). The proposal attracted around 49–72 disputes, effectively wiping out the proposer's PnL. ⚠️ Bugs & Issues A Phoenix, AZ rainfall market appears to have misresolved to "No" despite METAR and NWS climate data showing rain and thunderstorms on October 30. The CLI report showed "MM" (missing data) for that date. sam46 noted this is an edge case not previously encountered, suggesting Polymarket may need a fallback source when primary CLI data is missing. A CS2 map market (DM2 SSins, Oct 31) was proposed 50/50 despite no official result on HLTV or Liquipedia. kripkripochek3922 reported the stream went offline due to connectivity issues, but contacted a team manager and player who confirmed the game was completed. No official tournament result has been published. 📋 Clarifications Corners market (QPR vs Preston, ELC): eip15942 disputed a corners total market, arguing that Polymarket's own rules state "corners taken" (not "awarded") should count, and that QPR's official data API shows 12 corners taken vs. 13 awarded. Other users (mawyoo, nopsuke, gum5683, tenacious_mango_59265) countered that the binding resolution source is the EFL's official match centre, which reports 13, and that the QPR API endpoint is not the designated resolution source. The consensus view is that the EFL page showing 13 corners controls, regardless of the taken/awarded distinction in the rules, unless the official source itself separates those figures. Anti-cartel operation market (October, Colombia): kefoboss argued a US anti-cartel operation market should resolve Yes based on a Colombian CTI operation conducted "with the backing of DEA and IRS-CI." goldenhelmetxd cited the resolution criteria requiring physical US presence at the target site, not merely support or advisory roles, pointing to P1 No. The August version of the same market already resolved No despite SOUTHCOM and DEA involvement, establishing precedent. ⚡ Disputes Israeli legislative election winner market: jenia_13 and armanh01 are in an ongoing dispute. armanh01 disputes the resolution, claiming the market was proposed before final counts were confirmed and that there was genuine ambiguity. jenia_13 counters that the ambiguity was "inside your head" and that the party in question received fewer than 9,000 votes, making the result clear. armanh01 acknowledged jenia_13 will "likely win" given the market's high volume. The Israeli election winner market (linked to Polymarket) has reportedly misresolved according to armanh01, who intends to set precedent with the current dispute first. Venezuela election historical grievance: rhinosaur_ reiterated that a prior Venezuela election market resolved in favor of Edmundo Gonzalez due to alleged manipulation by a whale ("Domer") who accumulated cheap Maduro No shares and influenced UMA voters — a resolution described as a "scam" both inside and outside the ecosystem, and covered by rekt.news. When resolution sources conflict—like the QPR corners taken vs. awarded debate—should the official league page always win over team API data, or does the distinction matter?

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?