Resolution criteria on PolyGram: This market refers to the tennis match between Francesco Forti and Reilly Opelka in the Perugia, originally scheduled for June 2, 2026 at 10:00AM ET. This market will resolve to 'Francesco Forti' if Francesco Forti advances against Reilly Opelka. This market will resolve to 'Reilly Opelka' if Reilly Opelka advances against Francesco Forti. If the match is canceled (not played at all), ends in a tie, or is delayed beyond 7 days from the scheduled date without a winner determined, this market will resolve to 50-50.
PolyGram is an on-chain prediction market where you trade YES or NO outcome shares with real USDC on Polygon. For this market, buy YES if you believe the event will happen, or NO if you think it won't. Your maximum loss is your stake — winning shares pay $1.00 each at resolution. Unlike sportsbooks, there is no house edge: prices are set by supply and demand from other traders and reflect the crowd's real-time probability.
Market outcomes
| Perugia: Francesco Forti vs Reilly Opelka Set 1 O/U 8.5 | 50% YES | 50% NO |
| Perugia: Francesco Forti vs Reilly Opelka Set 1 O/U 9.5 | 50% YES | 51% NO |
| Perugia: Francesco Forti vs Reilly Opelka Set 1 O/U 10.5 | 50% YES | 50% NO |
| Perugia: Francesco Forti vs Reilly Opelka Total Sets: O/U 2.5 | 50% YES | 50% NO |
| Perugia: Francesco Forti vs Reilly Opelka Set 1 Winner | 50% YES | 50% NO |
| Perugia: Francesco Forti vs Reilly Opelka Match O/U 21.5 | 50% YES | 50% NO |
| Perugia: Francesco Forti vs Reilly Opelka Match O/U 22.5 | 50% YES | 50% NO |
| Perugia: Francesco Forti vs Reilly Opelka Match O/U 23.5 | 50% YES | 50% NO |
Francesco Forti and Reilly Opelka are scheduled to meet in the opening round of the ATP Challenger event in Perugia on 2 June 2026. The market currently reflects a 50–50 split on Polymarket's order book, indicating genuine uncertainty between the two competitors. Settlement occurs at 14:00 UTC on 9 June, allowing a one-week window for the match to conclude.
Opelka, a former top-20 player with a career-high ranking of 17, has competed primarily on the ATP Tour and brings substantial experience to Challenger-level competition. Forti, an Italian player competing on home soil, typically operates within the Challenger circuit and lower-ranked tournaments. Historical precedent suggests that established ATP-level players often carry an edge in Challenger events, though home-court advantage and surface familiarity can materially shift outcomes. The even split on the order book reflects traders pricing in these competing factors without a clear consensus.
Key variables include Opelka's current fitness and recent match activity—his participation in Perugia represents a deliberate scheduling choice that warrants monitoring. Surface conditions at the Perugia venue, typically clay, favour baseline consistency over Opelka's serve-dominant game. Any withdrawal announcements, injury updates, or schedule changes affecting either player before 2 June will influence the probability distribution. Weather disruptions in early June could trigger the seven-day delay clause, which would resolve the market to 50–50 regardless of eventual outcome.
This market settles from the official outcome published at https://www.atptour.com/en/scores/current. A proposer submits the final result to the UMA optimistic oracle on Polygon; the two-hour dispute window closes and payouts clear in USDC.
The mechanics for trading "Perugia: Francesco Forti vs Reilly Opelka" are the same as any other PolyGram event contract. Each YES share resolves to $1 if the event happens, or $0 if it doesn't. The current price between 0¢ and 100¢ is the market's probability estimate, set live by the order book.
$32K in lifetime turnover and $50K of resting liquidity puts this market in the around the median by volume for tennis contracts on PolyGram. Order-book depth is strong — order books support five-figure trades with single-cent slippage.
Last 24 hours alone saw $32K in turnover, well above the lifetime daily-average for this market — a clear sign of news catalysing trader activity right now.
The market has been open for under a month — fresh enough that information asymmetry remains a real factor.
Higher-volume markets tend to have tighter spreads and faster price discovery — meaning the displayed YES/NO percentages are more likely to reflect the true crowd-implied probability rather than a single trader's directional view.
Resolution is sourced from https://www.atptour.com/en/scores/current. Settlement is executed by the UMA optimistic oracle on Polygon, with a 2-hour dispute window before payouts clear.
This prediction market is scheduled to close on 9 June 2026. After the resolving event occurs, settlement typically clears within 24 hours once the UMA optimistic oracle confirms the outcome. All payouts are in USDC on the Polygon network.
To trade on this prediction market, create a free PolyGram account at polygram.ink, deposit USDC via Polygon, and place a YES or NO order on the outcome you believe in. You can learn more on our how-it-works page. Your maximum loss is limited to your stake — there is no leverage or margin.
When the outcome is determined, winning YES shares pay out $1.00 each in USDC, while losing shares pay $0. Settlement is handled by the UMA optimistic oracle on Polygon — a proposer submits the result, a two-hour dispute window opens, and if uncontested, payouts are distributed automatically. You can withdraw your winnings to any Polygon wallet.
Prediction-market positions can lose 100% of staked capital. Outcomes are uncertain by definition — historical accuracy of crowd-implied probabilities is high in aggregate but not for any single market. PolyGram does not provide investment advice. Trade only with capital you can afford to lose.
Regulatory status varies by jurisdiction. Germany, the United States, and most EU countries treat Polymarket-style event contracts under one of three frameworks: financial derivative, gambling product, or unregulated novel asset. Consult local counsel before trading.
Explore more prediction market odds and trading opportunities on PolyGram: