Samsun: Constantin Bittoun Kouzmine vs Manoj Dhamne Manas

Platform comparison

Market context

The Samsun Challenger quarter-final between Constantin Bittoun Kouzmine and Manas Dhamne has already been played, with Kouzmine winning 6-4, 7-5 on outdoor hard courts in Turkey.[1][4][8] For a market already showing 100% YES, the cleanest read is that the event outcome is no longer a live pricing problem; if your tooling still shows exposure, the practical task is to check whether the contract has updated from in-play status to final settlement and whether any data feed lag is keeping stale probability on screen.[1][17]

Comparable cases in Challenger tennis suggest the pre-match gap was modest rather than decisive. Dhamne entered as the higher-ranked player, around ATP No. 372 versus Kouzmine’s No. 507, while both sites also noted no meaningful head-to-head history before this meeting.[4][14] That combination usually supports a live market that can move quickly on a single break of serve, especially in best-of-three format where one tight set can flip implied win rates sharply; the published 6-4, 7-5 scoreline fits a competitive match rather than a routine blowout.[1][8]

For a trader running this programmatically, the main catalysts to monitor are the official match status, court assignment, and any schedule changes around the stated 10:30 UTC start, because challenger events can be delayed, rescheduled, or completed before third-party feeds refresh.[4][6][10] In a rules-based workflow, the key dependency is whether the match is marked completed within the settlement window ending 2026-08-07T10:30:00Z; if a feed shows no winner despite a completed scoreline, the likely issue is reconciliation delay rather than event uncertainty.[1][17]

Sources: 1 · 2 · 3 · 4 · 5

Methodology

We track Samsun: Constantin Bittoun Kouzmine vs Manoj Dhamne Manas across the five venues with material prediction-market liquidity. The probability shown is the live Polymarket mid; the comparison rows summarise how each venue treats the underlying contract — fees, KYC thresholds, settlement currency, deposit options. The highlighted row marks the cheapest route into Polymarket's order book.

Resolution & payout

Settlement runs on-chain. Polymarket's contract logic separates YES and NO shares as conditional tokens; at resolution the winning share lifts to $1.00 and the losing one to $0. The outcome input comes from the UMA Optimistic Oracle, which secures against bad resolution with a bond + dispute window.

Once finalised, the smart contract pays USDC to the holders' wallets within minutes — no withdrawal fees beyond Polygon network gas. Kalshi settles in USD via CFTC clearance, Betfair in account currency net of commission, Manifold in play-money mana with no cash-out.

FAQ

Is this market available outside the US?

Polymarket itself is geo-blocked in the US/UK/EU. Always check the legal status of prediction markets in your jurisdiction before trading.

How does resolution work?

Through the UMA Optimistic Oracle on Polygon: a proposer submits the outcome, a two-hour challenge window opens, and USDC payouts settle automatically once the result is final.

What's the difference between YES and NO shares?

A YES share pays $1.00 if the event happens, $0 otherwise. A NO share pays $1.00 if the event doesn't happen. The market price between 0¢ and 100¢ is the implied probability.

Do I need to KYC for this market?

On Polymarket directly, no — it's wallet-based. Intermediary brokers like Kalshi Fees trigger KYC only above $1,500 of lifetime trading volume; under that you trade pseudonymously with a single wallet address.

How reliable are the quoted odds?

The YES/NO percentages are the live mid-prices of the Polymarket order book. On deep markets they move every few seconds; on thinner ones you'll see short plateaus.