BOUT / Docs
Both sides.
The light blade is Trader A.
PRELAUNCH · SIMULATION
One rule.
The dark blade is Trader B.
Light corner
Trader A
- Profit, selected window (USD)
- Change over the chosen round
- Share price
- A's chance in cents, shown to two decimals
- Shares outstanding
- A shares recorded in this session
- What a win pays
- 1.00 USDG per winning share
Dark corner
Trader B
- Profit, selected window (USD)
- Change over the same round
- Share price
- 100.00 cents minus Trader A's price
- Shares outstanding
- B shares recorded in this session
- What a win pays
- 1.00 USDG per winning share
The rule
Three judges.
The middle reading.
Two traders. One round.
Pick two public trading accounts. Over 24 hours or 7 days, whichever grows its profit more wins.
The middle decides.
The median of three readings at the start and at the end. A side wins if the closing reading is greater.
Flat goes to B.
A good or bad week in the market hits both and cancels out, so only the better trading decides it.
A winning share pays 1.00 USDG.
Two percent fee on winnings only. A losing share pays nothing.
No contest? Stake returned.
Either trader leaving, fewer than three eligible readings, or a reading older than twenty minutes. Every stake is returned at cost.
How a share gets its price.
Opening uses a t-4 model on the bind, clamped 15 to 85 cents. A fixed-product pool is seeded at 25,000. Fills more than 5 cents from price are refused.
Two percent fee on winnings only, split 40 / 40 / 10 / 10, with the account share halved between both accounts.
Where the numbers come from
The fight card is a public read of Hyperliquid's leaderboard at stats-data.hyperliquid.xyz/Mainnet/leaderboard, then a portfolio read for each listed account at api.hyperliquid.xyz/info. This site caches that read for five minutes and prints a SHA-256 hash of the time, the accounts and the matchups so anyone can compare.
What is published.
The calculator illustrates arithmetic and keeps only the runs you record in this session. Wallet connection reads your address and native balance. Contract-dependent values stay unpublished until configured.
What still needs a specification?
Contract rules, triggers and integrations. Wallet actions require your confirmation.