{"slug":"polymarket-resolution-delay","title":"Polymarket resolution time, measured onchain","subtitle":"Seconds from the first onchain outcome proposal to UMA resolution, measured per category from Polygon logs, with dispute rate and the live backlog of unresolved markets.","category":"Trading","metric":"Resolution delay","unit":"s","status":"live","higherIsBetter":false,"value":696.494,"leader":{"name":"Crypto","slug":"crypto","value":696.494},"rankings":[{"name":"Crypto","slug":"crypto","ms":{"p50":696.494,"p90":1784.33,"p99":13556.2,"mean":1431.68},"successRate":91.4672,"sampleSize":12364},{"name":"All markets","slug":"all-markets","ms":{"p50":2670.41,"p90":12248.6,"p99":14365.5,"mean":3559.42},"successRate":68.53620000000001,"sampleSize":82978},{"name":"Other","slug":"other","ms":{"p50":2770.44,"p90":12251.1,"p99":14377.7,"mean":3671.72},"successRate":68.6233,"sampleSize":24072},{"name":"Sports","slug":"sports","ms":{"p50":3062.28,"p90":12589.8,"p99":15897.6,"mean":4003.07},"successRate":63.3656,"sampleSize":45804},{"name":"Politics","slug":"politics","ms":{"p50":10744.5,"p90":13725.4,"p99":14396.2,"mean":8007.41},"successRate":2.43902,"sampleSize":738}],"sparkline":[697.207,697.242,697.118,697.533,697.533,697.533,698.218,698.218,700.983,700.828,700.828,700.476,700.755,700.755,700.592,701.066,701.066,701.066,702.492,702.492,702.007,702.007,702.007,701.679,701.757,701.757,701.28,701.28,701.28,701.28,700.808,700.808,700.545,700.34,700.34,699.876,699.876,699.876,699.517,699.296,699.285,698.843,698.832,698.899,698.591,698.449,698.449,698.004,698.004,698.004,698.004,697.553,697.553,697.094,697.094,697.094,696.662,696.662,696.662,696.285,696.447,696.447,696.021,696.021,696.021,696.021,697.347,697.347,697.347,696.919,696.919,696.919,696.494],"sampleSize":165956,"asOf":"2026-06-16T15:33:26.631Z","headline":"Crypto leads resolution delay at 0.7 s (p50, 24h) on Polymarket resolution time, measured onchain.","quote":"Crypto leads resolution delay at 0.7 s (p50, 24h) on Polymarket resolution time, measured onchain. Source: OpenChainBench (https://openchainbench.com/benchmarks/polymarket-resolution-delay).","pageUrl":"https://openchainbench.com/benchmarks/polymarket-resolution-delay","ogImage":"https://openchainbench.com/api/og/polymarket-resolution-delay","source":"https://github.com/MobulaFi/mobula-monorepo/tree/main/miniapps/pm-resolution-delay","methodology":["Anchor: the first OO ProposePrice block timestamp, not Gamma fields. Verified live: Gamma closedTime equals the QuestionResolved block timestamp to the second (circular by construction) and endDate is a scheduled buffer that a majority of markets resolve before. Any 'resolves within X' claim computed from those fields is unfalsifiable.","Sources: Polygon logs of the post-migration UMA CTF adapters (binary 0x65070BE9..., neg-risk 0x69c47De9...) and their Optimistic Oracle (0x2c0367a9...), all address-configurable. Gamma supplies the market catalogue and category tags.","Join: questionID = keccak256 of the proposal ancillary data, verified against QuestionInitialized events. Neg-risk markets expose a different Gamma questionID; categories fall back to keyword classification for those, the delay itself is unaffected.","Categories: sports, politics, crypto, other, classified from Gamma tags plus keyword fallback. Categories run different UMA verification windows, so per category rows are the honest unit of comparison.","Disputes: a DisputePrice before resolution marks the market disputed and its delay lands in the disputed series. QuestionReset events are tracked so re-proposals do not create duplicate joins.","Pending backlog: markets past their scheduled endDate with no onchain resolution, polled from Gamma every cycle. This includes markets whose underlying event has not happened yet despite the date passing, so it is an upper bound.","Listener: 45s incremental Polygon log polling with a 7 day chunked backfill on restart, two public RPC endpoints with rotation and backoff. Counters re-count the backfill window after a restart; quantiles are computed on the cumulative histogram, which the backfill repopulates within minutes.","Delays are measured between block timestamps, so the resolution granularity is Polygon's block time (~2s), negligible against delays measured in minutes and hours.","What this does not measure: the gap between the real world event ending and someone submitting the first proposal. That interval is not observable onchain; the proposal is the first onchain signal that the outcome is known. Reported delays are therefore a lower bound on the total wait."],"license":"CC-BY-4.0"}