No House
Your counterparty is the other side of the pool. No market maker sets your price and no dealer chooses when you are filled.
The rules below describe what the points beta runs today, and what changes when contracts launch on 15 December 2026.
Your counterparty is the other side of the pool. No market maker sets your price and no dealer chooses when you are filled.
The strike is read on a window that opens only after staking closes. Being faster, closer or better connected buys nothing.
Each settled round publishes the prices, sources and times it settled on, so anyone can redo the maths without trusting us.
All three are contract rules from 15 December 2026. Today this is a points beta running the same rules with practice liquidity in the pools.
Staking closes before the strike is read. Once locked, a stake is final and cannot be reduced, cancelled or withdrawn.
Settles on the median of five exchange prices, read after staking closes. At least two sources must respond and agree within 0.5%, otherwise the round voids and every stake is refunded with zero rake.
The engine takes 2% of the pot, never more than the losing pool, so a winner is never paid back less than their stake. With a full losing pool that works out at 0.98 of the gross payout. Losing positions receive nothing. Exact ties, one-sided rounds and oracle failures refund stakes in full with zero rake.
The contract planned for 15 December 2026 runs the same capped rule on chain, with settlement and payment handled by the contract rather than by this server.
A connected wallet can stake at most 2,000 points in one round. Points are free, have no cash value, cannot be bought and cannot be withdrawn.
These are the prices, sources and times this round settled on. From 15 December, rounds settle on-chain and this receipt also carries the transaction and the signed price data, so anyone can recompute the result without trusting us.
Receipts show the round ID, open, lock and settle times, quote-read times, strike, close, winner, pools, rake, multiplier and each recorded source price. Older rounds identify fields that were not recorded.
A database status guard lets each round settle only once.
Too few fresh sources, excessive disagreement, an exact tie or a one-sided pool voids the round automatically.
The current interface has no control that lets an operator choose a winner or rewrite a settled result.