IPO binaries
A binary market asks one yes-or-no question with a deadline: "Will COMPANY IPO by 2027-11-28?". One Yes share pays $1 if the answer is yes and $0 if it isn't. It trades on the order book like any market, priced in tenths of a cent (the tick is $0.001) from $0.001 to $0.999: 0.1¢ to 99.9¢. An order priced outside that range is refused.
Each company expiry has one, {BASE}Y{YYMM}-USD, and an IPO event listed on its own has
{BASE}-USD. A binary can also be listed alone (MsgCreateBinaryMarket, ticker NAME-USD).
Positions and backing
Buying Yes is a long; selling Yes you don't hold is a short, which is the same as holding No. Every position is fully backed by its owner's own USDC, so each long and short pair holds exactly $1 a share:
| Position | Locked per share | Yes: paid per share | No: paid per share |
|---|---|---|---|
| Long Yes, bought at p | p | $1 (profit 1 − p) | $0 (loss p) |
| Short Yes (No), sold at p | 1 − p | $0 (loss 1 − p) | $1 (profit p) |
So there is no leverage, no borrowing, no liquidation and no funding. Unrealized gains can't be withdrawn before resolution; only USDC above what the position locks can. Closing early is a trade at the market price. The market is isolated: a subaccount trading it holds nothing else.
Price
A binary's oracle price is its own last trade, written by the chain after each block with trades, held within 0.1¢ and 99.9¢. No outside feed is used. It marks positions for display only: nobody's solvency depends on it, and stop orders don't watch it.
For a company expiry, the binary's price p that the implied market cap and the company index read is not the last trade: it is the binary book's 60-block average of long-term quotes, moving at most 2¢ a block and within 10¢ of a slow reference (the implied market cap).
Stop orders
A binary that is part of an IPO event takes stop-loss and take-profit orders. A stop doesn't watch the last trade: it watches the event's slow binary price reference, which follows p slowly and which no trade moves. A trigger outside 0.1¢ to 99.9¢ is refused. Halting the market cancels every stop on it. A standalone binary has no slow reference and takes no stop orders (stop orders).
Resolution
Each market names, at listing, a resolution time (an event's deadline), an admin
address, where its rules are written (rules_url), and a resolve delay. Resolving takes
two steps:
- Halt (
MsgHaltBinaryMarket, orMsgHaltEventfor an event): trading stops. Every open order is cancelled, and the book takes no more orders or matches. The halt doesn't name an outcome. - Resolve (
MsgResolveBinaryMarket, orMsgResolveEvent), at the earliest from the block after the halt:- Yes can be resolved at any time after the halt (the event happened);
- No can be resolved only from the resolution time (it didn't happen by then);
- signed by the admin, only once the resolve delay has passed since the halt, by block time.
A market resolves once. Each position is then paid $1 a Yes share on Yes, $0 on No, from the matching shorts' locked USDC.
A halt can't be undone. A halted book never trades again, and No is refused before the resolution time, so a halt before the resolution time commits the market to Yes (or to waiting, positions locked, until the resolution time). For a company expiry it is also the IPO: the perpetual and every trading expiry halt with it (settlement).
Delays
| Resolve delay | |
|---|---|
| Standalone binary or event | 300 s to 2,592,000 s (30 days), set at listing |
| Company expiry | At least 3,600 s, from the company's template |
| Company expiry, admin Yes that would settle the perpetual | After x/gov's expedited voting period + 1 hour, or the delay if longer |
| Governance | None: from the block after the halt |
The delay is what lets governance step in when an admin key is stolen: it can replace the admin before the thief can resolve.
Governance as the fallback
Halting and resolving can be done by the market's admin or by governance:
- the admin can hand its role to a new address, and governance can replace a lost or stolen
admin key, until the market resolves (
MsgUpdateBinaryMarketAdmin,MsgUpdateEventAdmin,MsgUpdateCompanyAdmin); - governance may halt, and may resolve from the block after the halt, with no resolve delay;
- governance is otherwise held to the same rules: halt first, resolve a block later, and No only from the resolution time.
To recover from a stolen key, governance sends one proposal that first replaces the admin and then, if the market still trades, halts it. A halt in a proposal of its own would start the delay for whoever holds the key.
Payouts
Payouts run at the end of each block, at most 500 holders a block, shared evenly among the
markets being paid out: with k markets resolving, each gets at least ⌊500/k⌋ payouts a block,
or all it still needs. Until its last holder is paid a market shows
MARKET_STATUS_RESOLVING, then MARKET_STATUS_RESOLVED_YES or MARKET_STATUS_RESOLVED_NO.
Before it marks a market resolved the chain checks that the payouts sum to zero and that the
shares paid, long and short, equal the shares open at the halt; otherwise the market stays
resolving and the shortfall is reported. A payout that fails is reported and tried again the
next block.
What can be seen coming
- Nobody can trade on the resolve transaction: once a market is halted its book executes no matches.
- The halt can give the outcome away: a halt before the resolution time means Yes. The testnet's public RPC doesn't show pending transactions, so a halt can't be seen before it is in a block. Within its block the halt executes after that block's matches.
Reading it
GET /dydxprotocol/binary/market lists every binary-market record (binaries, options and the
perpetuals use the same record), GET /dydxprotocol/binary/market/{perpetual_id} one, and
GET /dydxprotocol/binary/event/{id} an event (x/binary reference).