PROTOCOLFour public functions

How a coin ends up holding a perp.

Four moves, each a public function. The keeper picks when they run; the contract decides everything else.

  1. 01requestLaunch

    Launch

    A creator names the coin, picks a perp, a direction and a leverage, and writes the mission. The coin opens single-sided at ≈$5.5k FDV with 100% of supply in a HyperSwap pool its vault owns — and cannot withdraw from.

  2. 02harvest · bridge

    Fees become margin

    Every buy pays 1% in HYPE: 80% bridges into the coin's own Hyperliquid account as margin, 20% goes to the protocol. The coin-side fee that sellers pay is burned rather than sold.

  3. 03open · fund

    The vault trades

    Once the account clears the threshold the vault opens the position itself through CoreWriter. Later fees top it up at the same leverage setting, which pushes the liquidation price further away.

  4. 04close · settle

    Close and roll

    The creator closes only by naming the next position. 60% of the profit stays on the venue with the principal as margin, so a coin compounds instead of restarting; 30% buys the coin back and burns it, 10% goes to the creator. A loss resets the baseline and the coin rebuilds from fees.

Coins
Margin deployed
on HyperCore
Fees to margin
Paid to creators
STATE MACHINE

Every transition is someone’s transaction.

01 · waiting
IDLE
open
02 · order sent
OPENING
confirm
03 · live
OPEN
close(next)
04 · next named
CLOSING
confirm
05 · profit out
SETTLING
no fill in 30 L1 blocks
→ back to IDLE
TAKINGautomatic
25% over its watermark, the vault takes 10% off the table by itself, then returns to OPEN.
distribute
60%
30%
10%
margin · burn · creator
settled → IDLE · a loss, or profit below the floor, resets the baseline
PARAMETERS

Protocol parameters

Fee split
80% margin · 20% protocol
Profit split
60% stays as margin · 30% buyback-and-burn · 10% creator
Automatic take-profit
10% of profit at +25%
Open threshold
$12
Settlement floor
$12
Launch FDV
$5,500
Launch fee
0 HYPE
Order slippage
1%
Buyback impact guard
5%
Open confirmation timeout
30 L1 blocks
Chain
HyperEVM · 999

Read from the factory on 25 Sep 2026, not live — the API is not responding. The owner can change forward-looking config, so check the contract before relying on these.

The owner can still change forward-looking configuration and pause new launches — today from a single key. What that key cannot touch, and what it should become, is written out in the paper.

Trust surface · §11