DeepBook Predict does not issue a token of its own. DEEP, USDC and $PBAY are three different things, and only one of them decides whether your position pays.
Predict Bay ·
No. The protocol does not issue a token of its own, and there is nothing you have to buy in order to open a position on it. The query collapses three separate things into one word. DEEP is the ecosystem token of DeepBook, the on-chain order book that DeepBook Predict sits alongside on Sui. USDC — Circle's dollar stablecoin on Sui — is the settlement asset on the mainnet deployment — the unit a binary position is priced, collateralised and redeemed in. $PBAY is Predict Bay's platform token, live since 8 Oct 2026, and is not a DeepBook protocol token.
ROUND CLOSES IN
--:--
LAST PRICE
—
STRIKE
—
NO POSITIONS YET THIS ROUND — BE THE FIRST
Practice mode · no wallet, no deposit, free to start
One scope note before anything else, because it is the kind of thing most pages leave out. Everything below describes the DeepBook Predict deployment on Sui mainnet — the one Predict Bay's integration actually targets, and the one we can trace claim by claim. Where a detail is protocol-level and published, we say so; where it is deployment-specific, we name the deployment.
Those three roles are not interchangeable, and the difference is the whole answer. The asset that determines whether a position pays you is the settlement asset. A protocol token like DEEP pays for and governs the order book's own machinery. A platform token like $PBAY belongs to an application built on top and carries none of the protocol's guarantees. If someone is offering you a tradeable "DeepBook Predict token", they are describing something that does not exist. For how the protocol itself works, see our reference page on DeepBook Predict; this post is about the money.
Crypto uses one word for three jobs, and most confusion about "the Predict token" dissolves once you separate them.
| Category | Example | What it does | Needed to hold a Predict position? |
|---|---|---|---|
| Settlement asset | USDC (mainnet deployment) | The unit a position is priced, collateralised and redeemed in | Yes — it is the collateral and the payout |
| Protocol token | DEEP (DeepBook) | Pays and discounts order-book trading fees; stakes into pools; votes on pool fee parameters | No — it is the order book's fee and governance token |
| Platform token | $PBAY (Predict Bay) | Intended to sit at the application layer: platform fees, rewards, platform governance | No — $PBAY is Predict Bay's token, not issued by DeepBook or Sui |
Two errors follow from mixing these up. The first is assuming you must acquire DEEP before you can take a directional view on BTC through a binary contract. You do not. The second is assuming $PBAY is a DeepBook asset, and therefore that its behaviour is underwritten by DeepBook or by Sui. It is not, and no honest page should let you believe otherwise.
DeepBook is Sui's native central limit order book. It runs as Move packages, and the book itself lives in on-chain objects rather than in an operator's database — accounts are BalanceManager objects that custody funds and authorise trades on the owner's behalf. DEEP is the ecosystem token attached to that order book, and its utility is specific and mechanical rather than aspirational.
DeepBook's fee model lets trading fees be paid in DEEP, or alternatively in the input coin of the trade at a less favourable rate. That asymmetry is the demand mechanism: active traders who route volume through the book have a standing reason to hold and spend the token, and traders who would rather not deal with it can still trade by paying more in the asset they were already using.
DEEP can also be staked against a specific pool. Staked balance, combined with traded volume, is what places an account in a fee tier, and stakers in a pool can propose and vote on that pool's taker and maker fee parameters within bounds the protocol enforces, with changes taking effect on epoch boundaries. Governance is scoped to the pool, not to the whole exchange — a decision about one market's fee schedule does not reach into another's. We go further into how that book supplies liquidity for prediction-style markets in DeepBook's CLOB and prediction market liquidity.
None of that is a gate on holding a binary option. When a DeepBook Predict position is minted on the mainnet deployment Predict Bay integrates against, what leaves the account is collateral denominated in the settlement asset, and what comes back at expiry is the payout in that same asset. A contract pays a fixed one USDC — 1,000,000 micro-units at six decimals — if it finishes in the money, and nothing if it does not, which is why the per-contract premium behaves like the implied probability of that outcome. Predict Bay previews that premium off-chain and then passes a maximum-cost guard into the mint transaction, because the exact all-in cost is computed and enforced on-chain rather than by us. There is no separate ticket token anywhere in that path.
A binary option pays a fixed amount if the underlying settles on one side of a strike at expiry, and nothing otherwise. That fixed amount has to be denominated in something. On the DeepBook Predict mainnet deployment, that something is USDC — Circle's dollar stablecoin on Sui, and real money. It is the collateral, the quote unit and the payout unit at once, which is precisely why it is not a protocol token: you hold it to express a position, not to own a piece of the system. The protocol's testnet deployment uses dUSDC, a test unit with no real-world value, in the same role.
How that premium is arrived at is worth spelling out, because it is where the settlement asset does its real work. Predict Bay estimates a per-contract price by reading the oracle's volatility surface for the underlying and computing the risk-neutral probability that the settlement price lands inside the contract's range — for a one-sided contract, that it finishes above or below the strike. That estimate exists to show you a number before you commit, and nothing more. The binding cost is computed on-chain when the position is minted, and the on-chain path accounts for components the off-chain preview deliberately does not model, which is exactly why the transaction carries a maximum-cost slippage guard sized off the estimate. Estimate, guard and final cost are all denominated in the settlement asset. None of them touch DEEP, and none of them touch $PBAY.
The position lifecycle makes the distinction concrete. Every stage below moves the settlement asset, and no stage requires any other token.
Define and post
You pick an expiry and a strike expressed as a price tick, then post collateral in the settlement asset. Sentinel tick values express one-sided contracts — above X, below X — while a bounded pair of ticks expresses a range contract.
Hold
The position is an on-chain object held in your account. No off-chain matching engine holds the book, so the record of what you own is the chain's rather than an operator's private ledger you have to take on trust.
Settle
At expiry the protocol settles against its on-chain oracle price. Nobody at Predict Bay decides the outcome — see oracle resolution and on-chain settlement for how that determination is made.
Redeem
You redeem the position for the fixed payout in the settlement asset if it finished in your favour, and for nothing if it did not.
Read that lifecycle back and the token question answers itself: the asset that decides whether you profit is the settlement asset, full stop. If you want the protocol-level walkthrough rather than the economics, start with what DeepBook Predict is.
Predict Bay is an application. It presents markets, handles sign-in, builds transactions and reads positions back from chain. $PBAY is the token for that application layer, live on Sui since 8 Oct 2026. We describe its intended utility in conditional language on the $PBAY token page and go into more detail in the $PBAY explainer, and it is worth being exact about what that intent covers.
Each of those is stated as intent. None of it is live, and none of it should be read as a commitment to a particular mechanism, rate or date. What $PBAY is not, on the other hand, can be stated flatly: it is not a DeepBook protocol token. It is not issued by DeepBook, it does not pay DeepBook's order-book fees, it does not vote on DeepBook pool parameters, and it is not required by the DeepBook Predict protocol for anything. Nor is it the settlement asset. That separation matters structurally — if a platform's own token also served as collateral, your payout would be denominated in an asset whose price moves with the platform's own fortunes, which is precisely the correlation a fixed-payout contract exists to remove. Anything you read that describes $PBAY as "the DeepBook Predict token" is wrong about both halves of that phrase.
Nothing token-shaped beyond the stake itself. Market pages carry a mode switch, and with EVM real-money trading paused it renders two options: Practice and Sui. Practice needs no funds at all. Sui mode stakes USDC — the settlement asset described above — and asks for no DEEP and no $PBAY. Start on the BTC market, or read the walkthrough on how it works first.
Getting in requires no seed phrase. Sign-in is Google via zkLogin, where a Sui address is derived from an ordinary OAuth sign-in plus a salt rather than from a mnemonic you have to write down and keep, and a zero-knowledge proof stands in for the credential so the sign-in itself is not published on chain. Transactions can be sponsored, so you are not required to hold SUI for gas. Connecting a Sui wallet directly is supported too, for people who prefer to bring their own keys — we cover the trade-offs in prediction markets without a seed phrase.
The live markets are short-duration price markets on BTC, ETH, SOL, SUI, DOGE and XRP, on hourly and daily rounds. A strike is set at the open, you pick whether the asset finishes above or below it, and the market resolves against an on-chain price feed. That is the whole instrument, and at no point does it ask you which tokens you hold beyond the one you are staking.
Prediction markets on a new chain attract impostor tokens, and the DeepBook Predict query is an obvious target precisely because the honest answer is "there isn't one". A few checks settle almost every case without trusting anyone's prose, including ours.
package::module::STRUCT path. A "token" advertised only as a ticker, with no type and no package ID, is not a token yet.predict or a coin struct named DEEP. The struct name proves nothing; the package it lives in is the identity.0xe68a7178ccebade5c46668747c9a066c3a35ae33a6698fa9de4eca88e58305d2::pbay::PBAY, published on predictbay.io and @PredictBay. Any other address presented as "the $PBAY contract" is not it.That is also the standard we hold ourselves to on this site: every claim about what is live traces back to the codebase, and where something is off, paused or unlaunched, we say which. More questions of this shape are answered in the general FAQ.