Overview
StonkPerps constructs the Stonk standard LaunchLab transaction from Stonk’s live quote-pair and pricing APIs. The connected wallet remains the payer, a fresh Token-2022 mint signs once, and a deterministic per-coin router is named as creator so Stonk can auto-forward creator fees to the market pipeline.
The wallet reviews and signs the exact LaunchLab transaction.
Creator proceeds accumulate at the coin’s fee router.
Verified conversion funds liquidity and insurance.
2× perps unlock only after every risk gate passes.
Launch flow
- Connect a Solana wallet and choose a live Stonk quote pair.
- Upload normalized token metadata.
- Fetch current LaunchLab pricing and construct the exact standard-mode Token-2022 create instruction.
- Review and sign in the wallet. StonkPerps never receives the user’s private key.
- Wait for finalization and verify the payer, mint, pricing accounts, curve rule and fee router on-chain.
- Index the launch and begin monitoring router fees.
Launching binds the fee path. It does not deploy the custom market or enable leveraged trading.
Fee routing
Stonk’s platform collects its launch-curve fee and auto-forwards the creator portion to the creator account embedded in the launch. StonkPerps makes that account a deterministic router unique to the mint.
After audited conversion to USDC, the custom program enforces an exact allocation: 35% creator, 40% market liquidity, 15% insurance and 10% platform. The liquidity allocation mints locked protocol shares before user LP deposits.
Claims and conversion
Conversion is fail-closed behind operator access, output bounds, transaction-message hashing and post-confirmation token-balance verification. It remains disabled until custody, program and audit approvals are complete.
Market activation
A launched coin is not automatically tradable with leverage. Activation requires minimum age and spot liquidity, acceptable holder distribution, funded liquidity and insurance, protected oracle validity, safe mint controls and explicit production approval.
The lifecycle is launched, collecting_fees, building_vault, oracle_pending, eligible and perpetuals_live, with pause, settlement and closure states for risk operations.
Oracle model
Oracle ingestion is disabled. The planned design prefers a supported Pyth feed and otherwise requires a protected DEX index with time-weighted samples from independent, sufficiently liquid sources. It must reject stale data, large deviations, abrupt moves and insufficient depth before it can be used for trading or liquidation.
Risk engine
The proposed initial leverage cap is 2×, with open interest bounded by usable vault and insurance liquidity and a separate per-wallet exposure cap. These controls describe the planned system; they are not live trading features.
Liquidity vaults
Vault deposits are disabled. The planned design isolates USDC by market, queues withdrawals through a cooldown and checks locked liquidity, positive trader PnL and the reserve floor before any withdrawal executes.
Deployment status
The web, indexer and Stonk integration can operate while each value-moving capability stays independently disabled. Mainnet launches require an explicit launch approval; fee conversion and the custom perpetual program require devnet lifecycle evidence, adversarial review, independent audits and separate mainnet approval.