Polymarket runs event markets on Polygon with an off-chain order book and an optimistic oracle. Predict Bay runs short-duration crypto price rounds resolved by an on-chain price feed, with zkLogin onboarding and a Sui settlement path that is still on testnet. Here is how the designs differ, and what is actually live on each.
Predict Bay ·
Predict Bay and Polymarket are both prediction markets, and they are not competing for the same trade. Polymarket is an event-market venue on Polygon: a central limit order book over binary outcome shares covering elections, sports, macro releases and other real-world questions, resolved by an optimistic oracle with a human dispute path. Predict Bay is a short-duration crypto price venue: hourly and daily rounds on BTC, ETH, SOL, SUI, DOGE and XRP, where a strike is set at the open, you pick above or below, and the round resolves against an on-chain price feed. Pick by the shape of the question first. "Who wins the election" and "where is BTC in an hour" are different instruments with different resolution problems, and no single venue design is good at both.
ROUND CLOSES IN
--:--
LAST PRICE
—
STRIKE
—
NO POSITIONS YET THIS ROUND — BE THE FIRST
Practice mode · no wallet, no deposit, free to start
The second difference is maturity, and it is worth stating before anything else. Polymarket is live with real money. On Predict Bay, the Sui path targets a testnet deployment of DeepBook Predict and is switched off for real funds, and EVM/Polygon real-money trading is currently paused — practice mode is what is actually tradeable on Predict Bay today. That is the same thing the DeepBook Predict reference page says, for the same reason: a comparison you cannot verify is not worth reading.
Polymarket is the venue most people mean when they say "prediction market", and it defined the shape of the event-market category. Its core asset is an outcome share priced between 0 and 1 USDC that redeems for exactly 1 USDC if its outcome is the one that happens. That design is deliberately general: any question that can be phrased as a set of mutually exclusive outcomes with a written resolution rule can be listed, whether it settles next week or next year. The hard part of that generality is resolution, because most real-world questions have no canonical number to read at expiry.
Predict Bay narrows the question type on purpose. Every market Predict Bay lists is a short-duration price market on a major crypto asset, which means the thing being asked about already has a continuously published price. That removes the adjudication problem entirely and replaces it with an oracle problem, which is a smaller and more mechanical one. The trade-off is real and runs both ways: Predict Bay cannot list "will the central bank cut rates in September", and a general event venue cannot settle an hourly BTC round in seconds without a price oracle doing the work anyway. If you want the mechanics of the binary payoff itself, binary options vs prediction markets covers the instrument shape in more detail.
| Dimension | Polymarket | Predict Bay |
|---|---|---|
| Primary market type | Event and outcome markets: elections, sports, macro, plus crypto questions | Short-duration crypto price markets on BTC, ETH, SOL, SUI, DOGE, XRP |
| Chain | Polygon | Sui, via the DeepBook Predict protocol — the integration targets that protocol's testnet deployment. A Polygon path exists in the app, but real-money trading on it is paused and the Polygon segment is not rendered while it is |
| Instrument | Binary outcome shares under a conditional-token framework, collateralised in USDC | Binary options: an expiry plus a strike expressed as a price tick. Sentinel tick values give one-sided above-X / below-X contracts; a bounded pair gives a range contract |
| Where the order book lives | Central limit order book with off-chain matching and non-custodial on-chain settlement | DeepBook, Sui's native on-chain CLOB, is the book DeepBook Predict sits alongside. Positions are minted, held and redeemed entirely on-chain, with no off-chain matching engine holding the book |
| Resolution | Optimistic oracle: a proposer asserts the outcome against a bond, a challenge window runs, disputes escalate to a token-holder vote | On-chain oracle price at expiry. Pyth feeds for the underlying, alongside spot, forward and volatility-surface feeds published on Sui |
| Typical horizon | Days to months, set by whenever the underlying event actually resolves | Minutes to a day: hourly and daily rounds |
| Onboarding | Embedded wallet created from an email login, or connect an external wallet | Google sign-in via zkLogin, so there is no seed phrase. Transactions can be sponsored, so no SUI is needed for gas. Connecting a Sui wallet directly is also supported |
| Practice mode | Not a documented part of the venue | Practice mode, which mirrors the live market structure exactly |
| Real-money status | Live | Sui integration is testnet and switched off for real funds; Polygon real-money trading is paused; practice mode is what is tradeable today |
Two rows in that table carry most of the weight — resolution, and where the book lives. They are the choices everything else follows from, so the rest of this post is mostly about them.
An optimistic oracle is a social mechanism wearing a smart contract. Someone proposes the outcome and posts a bond. A challenge window opens. If nobody disputes within the window, the proposal stands and settles. If someone does dispute, the question escalates to a vote of the oracle's token holders, and whichever side is wrong forfeits its bond. The design is elegant because it costs almost nothing in the common case — most questions are not close, nobody bothers to dispute, and settlement is effectively free. It is also the only mechanism that can settle a question no data feed publishes, which is precisely why an event venue needs one.
Its costs are the ones you would expect. Settlement is not instant, because the challenge window has to run. Ambiguity is adjudicated by people, so the exact wording of the resolution criteria matters enormously and edge cases become governance events. And the final backstop is a vote, which is a different trust assumption from reading a number.
A price-feed oracle inverts every one of those properties. DeepBook Predict settles against its on-chain oracle price at expiry: the contract reads the feed, the payoff is determined by arithmetic, and the holder redeems. Nobody proposes anything, there is no window, and there is no vote. The cost is that it only works when a canonical price exists, and it moves the entire trust question onto the feed — its update cadence, how it aggregates across the publishers contributing to it, and how the contract handles a stale or missing update at the settlement instant. That is not a smaller problem, it is a different one, and oracle resolution and on-chain settlement works through it properly.
The practical consequence for a trader is simple. An hourly round can only exist on the second design. A challenge window measured in hours cannot resolve a market measured in hours.
Neither venue prices its binaries with an automated market maker, which is the right call for this instrument — a bounded 0-to-1 payoff has a natural quoting structure that a constant-function curve fits badly. The difference is where the book is kept. Polymarket runs a hybrid design: orders are matched off-chain for speed and cost, and the resulting trades settle on-chain non-custodially, so the operator sequences the book but cannot take your collateral. That is a well-understood engineering compromise, and on a chain with block times and fees like Polygon's it is a reasonable one.
DeepBook takes the other branch. The book itself is on-chain state on Sui — resting orders, cancellations and fills are transactions against a shared object, not rows in an operator's database. This is tractable because of how Sui executes: objects are owned or shared explicitly, transactions touching only owned objects can skip consensus entirely, and transactions touching disjoint objects execute in parallel rather than queueing behind one global lock. Traffic against a shared order-book object still has to be ordered by consensus — a shared object is a sequencing point, not a free lunch — but the rest of the chain does not queue behind it. An on-chain CLOB is a bad idea on a chain that serialises everything and a workable one on a chain that does not. DeepBook Predict sits on that stack and adds the options layer: you mint a binary position, hold it on-chain until expiry, and redeem it afterwards. On the testnet deployment the settlement asset is dUSDC. DeepBook, CLOB liquidity and prediction markets goes further into what that means for depth and spreads.
The payoff profiles rhyme — both pay a fixed amount on one side and nothing on the other — but the objects differ. A conditional-token outcome share is minted as a complete set: deposit 1 USDC of collateral, receive one YES and one NO, sell whichever side you do not want, and redemption burns the winning side against the collateral pool. A DeepBook Predict position is specified instead by an expiry and a strike expressed as a price tick, with sentinel tick values encoding one-sided contracts and a bounded pair of ticks encoding a range. That representation is why one primitive expresses "above 70,000", "below 70,000" and "between 68,000 and 72,000" without three different market types.
The strike is set at the open
When a round opens, the strike is fixed from the reference price at that moment. Everyone in the round trades against the same number, and it does not move afterwards.
You take a side
Above or below. The mode switch on a market page decides where that goes — with EVM off it renders two options, Practice and Sui, and Practice is the one that accepts a trade today. Selecting Sui shows the coming-soon panel in place of the trading controls.
The round runs
Price moves, and so does the fair value of each side. A one-hour round spends most of its life with the outcome genuinely uncertain, which is what makes short-duration markets worth pricing at all.
Expiry reads the oracle
At expiry the settlement price is read from the feed and compared with the strike. No proposal, no challenge window, no vote — the comparison is arithmetic.
The winning side redeems
On the Sui path — the testnet integration, which is not open for trading on Predict Bay today — the holder redeems the position on-chain for the payout, in dUSDC on that deployment. In practice mode, which is what you can actually trade now, the equivalent credit lands in your practice balance.
Both products have worked on the same problem — that asking a new user to write down twelve words is where most of them leave — and solved it differently. Polymarket creates an embedded wallet from an email login, with an external wallet as the alternative for people who already have one. You still end up holding USDC on Polygon, so funding generally means an on-ramp or a bridge.
Predict Bay signs you in with Google through zkLogin, which is a Sui-native primitive rather than a wallet vendor. The short version: your browser holds a short-lived ephemeral key, and a zero-knowledge proof establishes that a valid OAuth credential from your provider, combined with a salt that is never published on-chain, corresponds to your Sui address — without putting the credential or your identity into a transaction. The network verifies that proof together with the ephemeral signature, so what authorises a transaction is a login plus a proof rather than a permanent key you had to write down and keep. There is no seed phrase to lose because there is no seed phrase. Transactions can also be sponsored, meaning you can transact without holding SUI for gas — a meaningful difference from any design whose first step is acquiring the chain's native token. Connecting a Sui wallet directly is supported for anyone who prefers that. Prediction markets without a seed phrase covers the mechanism and its trade-offs, including what the ephemeral key's expiry and the salt actually mean for you, and how it works walks through the flow in the product.
That box is not a disclaimer bolted on at the end; it is the honest half of this comparison. If you want to place a real-money trade on an event outcome right now, Polymarket does that and Predict Bay does not. What Predict Bay offers today is the full market structure with simulated balances — same rounds, same strikes, same on-chain resolution, no capital at risk — plus a settlement path being built in the open rather than announced as finished. You can see the structure on the BTC market page, and the Sui tab and its coming-soon panel on the Sui tab on the BTC market.
Publishing which switch is off, and where it lives, is a deliberate position rather than an oversight. Most venues in this category describe roadmap as product. We would rather cost ourselves a conversion and keep a reader who can trust the next thing we publish. The FAQ answers the same questions in the same terms, and what is DeepBook Predict covers the protocol on its own.
On the token: $PBAY is a concept at this stage. Intended utility can reasonably be described in conditional terms — the fee and reward mechanics most trading venues eventually adopt — but nothing about supply, timing or distribution has been decided or announced, and no page here will imply otherwise. The token page holds whatever is actually known, and the $PBAY explainer says the same thing at more length.
The useful summary is that these are complements more often than substitutes. An event venue and a short-duration price venue address different halves of the same instinct — putting a number on what you think will happen — and they arrive at different architectures because the questions they answer resolve differently. If what you actually wanted was a comparison of the market types rather than the brands, prediction markets explained starts from first principles.