Predict Bay™

Sub-second event trading on Sui, powered by DeepBook Predict. Practice mode live today.

XTelegramDiscord
ProductMarketsDeepBook PredictHow to Buy $PBAYRoadmapWhitepaper (draft)TeamFAQBlog
ComparePrediction Market on SuiKalshi Alternative on SuiPolymarket Alternative on Sui
LegalTerms of ServicePrivacy PolicyDisclaimerSupport
© 2026 PredictBay Pte. Ltd.Practice mode uses points · Sui mode settles in real USDC on mainnet · rounds settle against on-chain price feeds
strike
← Research
MECHANICS10 min read

One-Minute Up/Down Markets on Sui with DeepBook Predict

A market that opens and settles inside sixty seconds has nowhere to hide a slow step. Here is what has to be true on-chain for that to work — the frozen reference tick everyone shares, odds read from the chain rather than estimated, and why the smallest on-chain stake is $2 rather than $1.

Predict Bay · September 29, 2026

The shortest round Predict Bay offers on Sui is one minute. A strike is fixed at the open, you take above or below, and sixty seconds later an on-chain oracle price decides it. There are also five-minute and one-hour cadences on the same rail, but the one-minute round is the interesting one, because it is the one where every piece of slowness in the design becomes visible at once.

LIVEBTC/USD · 3-MIN ROUND

ROUND CLOSES IN

--:--

LAST PRICE

—

STRIKE

—

NO POSITIONS YET THIS ROUND — BE THE FIRST

▲ ABOVE
▼ BELOW
Start trading now→

Practice mode · no wallet, no deposit, free to start

A one-minute market has no room for a settlement path measured in minutes, a dispute window measured in hours, or a price that arrives when it arrives. It also has no room for a strike that each user computes locally, because two users disagreeing by one tick over a sixty-second horizon is not a rounding difference — it is a different bet. Most of what follows is about how those constraints get met.

Note

What is live, and how this differs from the practice rail

The Sui rail is genuinely on-chain and genuinely tradeable with real money — on Sui MAINNET, settled in Circle USDC, against Mysten's DeepBook Predict mainnet deployment. A losing position loses its entire stake. The separate practice rail (three- and ten-minute rounds, simulated balances) is a different surface with a different settlement path. Real-money EVM trading on Polygon is paused.

Why the chain has to be fast, specifically

Settlement latency sets the shortest round a venue can honestly offer. That is not a slogan; it is an arithmetic constraint. If confirming a transaction takes ten seconds, then a sixty-second round spends a sixth of its life in a state where the user has committed but the chain has not agreed, and the last ten seconds before expiry become unusable — you cannot accept an order you cannot confirm before the thing it is betting on has already happened.

Sui finalises in well under a second, which is what moves a sixty-second round from a race against confirmation time into an ordinary instrument. The same property is why the position lifecycle can be fully on-chain rather than matched off-chain and settled later: you mint a position, it sits in your on-chain account, and you redeem it after expiry. There is no off-chain matching engine holding the book, which DeepBook, Sui's on-chain CLOB covers in more detail.

The reference tick: one strike, frozen, shared

The strike of a round is not a number the app picks. It is the reference tick — the oracle price captured on-chain when the round opens, snapped to the market's tick size, and stored on the market object itself. Every participant in that round reads the same value from the same place, because there is only one place.

It is worth being precise about why that matters more at one minute than at one hour. Over an hour, a strike computed client-side from a live feed might differ between two users by a few dollars, which is small relative to an hour of movement. Over sixty seconds it can easily be the entire range of the round. A shared, frozen, on-chain strike is what makes "above or below" a question two people can meaningfully disagree about rather than two people answering slightly different questions.

The strike itself is expressed as a price tick rather than a dollar amount, and the direction is encoded by the tick range you take. A one-sided contract uses a sentinel bound — everything above the strike, or everything below it — while a bounded pair of ticks expresses a range contract. Binary options vs prediction markets covers what that payoff shape does and does not protect you from.

Status

"Baseline pending" is normal, not a fault

The reference tick is seeded shortly before a round opens for trading, not when the round object is first created — so for much of a market's visible life it is genuinely null on-chain. The interface reports that state and will not let you mint into it. A venue that filled the gap with a client-side guess would be showing you a strike the chain has not agreed to, which is precisely the failure the reference tick exists to prevent.

Odds come from the chain, not from an estimator

The multiplier shown on the Above and Below buttons is not a local approximation. It is the protocol's own pricer, queried directly: the app asks the deployed package what a given tick range costs, for both the up range and the down range, and converts the returned probabilities into payout multipliers. The two sides sum to one, as they must for a binary.

This is done as a read-only inspection of the chain rather than a transaction, so it costs nothing, requires no signature, and works before you have signed in at all — which is why the odds are populated on the page for a logged-out visitor. The alternative most venues take is an off-chain estimator that models what the chain would say. That works until the model and the chain disagree, and the moment they do, the number on the button is not the number you get filled at. Reading the pricer removes the class of problem rather than tuning it.

Why the smallest on-chain stake is $2

The on-chain minimum is $2, where the practice rail's is lower. That is not an arbitrary product decision — it falls out of three protocol constraints interacting, and it is worth understanding because it explains the shape of the fee too.

  1. 01Positions come in lots. Quantity must be a whole multiple of the market's lot size, so the requested size is rounded, not taken literally.
  2. 02There is a floor on net premium. A mint has to clear a minimum premium regardless of how the stake was arrived at, so a very small ticket cannot be expressed at all.
  3. 03The fee scales with uncertainty, and quantity scales inversely with probability. Because a stake buys roughly stake / probability in quantity, and the fee is charged on quantity, the fee as a fraction of your stake grows as the contract gets longer-odds. Sizing therefore has to be fee-aware — the quantity is computed so the all-in cost lands on your stake, not so the premium alone does.

Put together, a $1 ticket cannot reliably clear the premium floor once fees and lot-rounding are applied, so the interface refuses it up front rather than letting the chain abort the transaction. That is the general principle worth taking from this section: on-chain constraints are better enforced in the control than discovered in the failure.

Cadences
One minute, five minutes, one hour — one minute is the default
Strike
The on-chain reference tick, frozen at the round's open and identical for every participant
Direction
A tick range — a sentinel bound for one-sided above/below, a bounded pair for a range
Odds
Read from the deployed pricer as a read-only chain inspection; no off-chain estimator
Settlement asset
Circle USDC on the Sui mainnet deployment
Minimum stake
$2 on the Sui rail, set by lot size, the net-premium floor and fee-aware sizing
Status
Live on Sui mainnet. Real money

One minute on-chain versus three minutes in practice mode

Predict Bay runs two rails, and they are not two versions of the same thing. The practice rail is a centralised venue with simulated balances and three- or ten-minute rounds; the Sui rail is on-chain, settled in real Circle USDC, and goes down to one minute. The instrument feels identical because the question is identical — above or below a strike at expiry — but the settlement path, the funding, and what a filled order actually is all differ.

Practice railSui rail
Round lengthsThree minutes, ten minutesOne minute, five minutes, one hour
Where the position livesA record in Predict Bay's own systemAn on-chain object in your account, minted and redeemed on Sui
StrikeSet by the venue at the round's openThe on-chain reference tick, readable by anyone
OddsQuoted by the venueRead from the deployed protocol's own pricer
Funded withSimulated balanceCircle USDC
Real moneyNoYes — Sui mainnet
Both rails are in the same app. Only the Sui rail is real money.

The reason to run both is that they answer different objections. The practice rail is the one you can use thirty seconds after arriving, with no wallet and no funding step. The Sui rail is the one where you can verify that the strike you were given is the strike everyone was given, because it is on a public object rather than in a private database. Neither of those is a substitute for the other.

Status

This is not investment advice

Nothing here is a recommendation to trade, and none of it is a forecast. A binary can lose the full ticket price, and for an out-of-the-money contract that is the single most likely outcome. A sixty-second horizon does not reduce that; it shortens the interval over which it is decided. Availability is restricted in some jurisdictions and it is your responsibility to determine whether your use is lawful where you are.

Common questions

How does a one-minute prediction market settle?
Against an on-chain oracle price read at expiry. A strike is fixed when the round opens, you take the range above or below it, and sixty seconds later the price decides the outcome arithmetically. There is no proposer, no challenge window and no vote, because there is nothing to adjudicate — the number is published on-chain. That is what makes a sixty-second round possible at all; a proposal-and-dispute process would outlast the market many times over.
What is the reference tick?
The oracle price captured on-chain when a round opens, snapped to the market's tick size and stored on the market object. It is the round's strike, and every participant reads the same value from the same place. Over a sixty-second horizon a strike computed independently by each client could differ by more than the round's entire range, so a shared frozen strike is what makes above-or-below a question two people can genuinely disagree about.
Why does the interface sometimes say the baseline is pending?
Because the reference tick is seeded shortly before a round opens for trading rather than when the round is first created, so it is genuinely null on-chain for part of a market's visible life. Minting is gated on it. Filling that gap with a client-side estimate would mean showing a strike the chain has not agreed to, which is the exact failure the reference tick exists to prevent.
Where do the payout multipliers come from?
From the deployed protocol's own pricer, queried as a read-only inspection of the chain rather than modelled off-chain. The app asks what the up range and the down range cost and converts the returned probabilities into multipliers, which sum to one as a binary requires. Because it is a read, it needs no signature and no gas, and the odds are populated even for a logged-out visitor.
Why is the minimum stake $2 on Sui?
Three protocol constraints interact. Position quantity must be a whole multiple of the market's lot size; a mint must clear a minimum net premium; and because a stake buys roughly stake-divided-by-probability in quantity while the fee is charged on quantity, the fee as a share of stake grows for longer-odds contracts. A $1 ticket cannot reliably clear the premium floor once fees and lot-rounding apply, so the interface refuses it rather than letting the chain abort the transaction.
Can I trade the Sui one-minute market with real money?
Yes. The Sui rail runs on DeepBook Predict's Sui mainnet deployment and settles in real Circle USDC, so a losing position loses its entire stake. The separate practice rail runs three- and ten-minute rounds with simulated balances, and real-money EVM trading on Polygon is paused.

Risk notice

Prediction markets carry risk and you can lose the amount you commit to a position. Nothing on this page is financial advice. See the Terms of Service before trading.

Continue reading

  • PROTOCOL

    DeepBook Prediction Markets, Explained

  • MECHANICS

    Oracle Resolution and On-Chain Settlement

  • MECHANICS

    DeepBook, CLOB Liquidity, and Why a Native On-Chain Order Book Changes Prediction Markets

Strikes

  1. Why the chain has to be fast, specifically
  2. The reference tick: one strike, frozen, shared
  3. Odds come from the chain, not from an estimator
  4. Why the smallest on-chain stake is $2
  5. One minute on-chain versus three minutes in practice mode