Metro Bank One Day Cup: Derbyshire vs Glamorgan

Platform comparison

Market context

The match is Derbyshire v Glamorgan in the Metro Bank One Day Cup group stage, with the result to be settled by the final score on ESPNcricinfo. The crowd price is at 100% YES, so the market is effectively trading as if Derbyshire are certain to be the winner, which is unusual enough that a programmatic check should first validate whether the contract label, selection, and live score feed are all aligned before assuming the probability is meaningful.

For context, this fixture has been framed publicly as a must-win Group B game, with Derbyshire still searching for a first win and Glamorgan carrying at least one victory into the round.[1] That sort of setup tends to create noisy pre-match pricing: one side can look structurally weaker on season form, while the other still has enough depth for a one-day chase or rain-shortened game to flip quickly. Coverage around the competition has also highlighted Glamorgan as recent title holders and Derbyshire as a side reliant on a few key contributors, which is the kind of split that often produces abrupt repricing when team news lands.[6][1]

A trader watching this market would normally track the published toss, confirmed XI, start delay, and any interruption risk, because those are the main catalysts that change win probability in one-day cricket. The live scorecard already shows this game in progress, with Glamorgan having won the toss and opted to bowl, which matters for any automated strategy that updates on innings state rather than pre-match sentiment.[15] For tooling, the useful approach is to poll the score feed, compare it against the market state, and alert on divergences between official match progression and the implied 100% YES price, because that is where stale liquidity or an input error is most likely to appear.[15][11]

Sources: 1 · 2 · 3 · 4 · 5

Methodology

We track Metro Bank One Day Cup: Derbyshire vs Glamorgan 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.

How fast are USDC deposits?

Polygon credits deposits after 12 confirmations — usually under 30 seconds. Withdrawals follow the same path and land back in your wallet within minutes.

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.