Stonk fees power a protected perps flywheel.

Overview

StonkPerps constructs the standard Stonk LaunchLab transaction and names a deterministic, per-mint fee router as the creator account. Creator trading fees flow into that router, are verified and converted to USDC in the pinned Imperial profile, then credit the creator, strategy-vault and insurance ledgers.

Launch flow

1. Connect a Solana wallet and choose a live Stonk quote pair.
2. Upload normalized token metadata.
3. Fetch current LaunchLab pricing and construct the exact standard-mode Token-2022 create instruction.
4. Review and sign in the wallet. StonkPerps never receives the user's private key.
5. Wait for finalization and verify the payer, mint, pricing accounts, curve rule and fee router on-chain.
6. Index the launch and begin monitoring creator-fee proceeds.

A successful launch binds the fee path. It does not automatically authorize conversion, custody or a leveraged position.

Fee routing

After verified conversion to USDC, proceeds route 10% to the creator, 75% to the protected strategy vault and 15% to insurance. The protocol takes 0%. The vault and insurance allocations together direct the remaining 90% toward supporting the leveraged strategy and its loss buffer.

Claims and conversion

The indexer accepts only a Jupiter-sponsored transaction that requires the exact derived fee-router signature, so the router never spends SOL. It records the protected quote before submission, caps each beta conversion at $100 of output, quarantines uncertain outcomes instead of retrying and verifies the confirmed message plus input/output balance deltas before crediting any ledger. If sponsorship is unavailable, the fees remain untouched. The conversion receiver must equal the profile PDA returned by the authenticated Imperial API. Direct USDC quote pairs are excluded until a separately approved payout executor exists.

Protected vault

The vault stays in the product. The position planner calculates capacity from idle vault USDC plus already deployed collateral and never approves more than 25% of total vault capital for margin. At least 75% remains reserved. Position principal returns to the vault when a position closes.

Creator and insurance allocations are never counted as strategy collateral. A strategy loss is limited to the explicitly deployed vault slice; it must not reach those separate balances.

Perps strategy

Once a coin's vault can supply at least $5 of deployable margin, the worker automatically creates a SOL-long strategy intent. The launched token remains the owner of the isolated vault accounting; the token itself is not represented as an unsupported perp market. Mainnet beta leverage is capped at 2×, collateral at the lower of 25% of vault capital or $25, and routing slippage at 1%.

Execution uses Imperial's official Trading API. The router may select an approved self-funding Jupiter, Phoenix or GMTrade market. Before submission, StonkPerps requires a fresh venue mark, fits Imperial's required deposit and fees inside the approved vault slice, verifies that the Imperial profile USDC covers the complete cash ledger and runs Imperial's side-effect-free preflight. The worker reconciles lifecycle IDs and signatures, then requests a full close at ±10% collateral PnL or after 24 hours.

Profit flywheel

After a verified close, principal goes back to the vault. Positive realized PnL is recorded as 40% burn, 30% buyback and 30% added liquidity. The liquidity share compounds in the vault ledger. Burn and buyback amounts remain queued until the custody wallet signs their on-chain settlement; the Imperial trading JWT cannot withdraw funds. The interface does not label queued allocations as completed transactions.

Risk controls

• 25% maximum vault deployment, $25 position-collateral cap and 75% reserve floor.
• 2× maximum initial leverage with ±10% collateral-PnL exits and a 24-hour maximum hold.
• One pinned Imperial execution profile and one live routed strategy at a time.
• Separate launch, fee-sweep, conversion, router and strategy approvals.
• The unaudited mainnet-beta acknowledgement and custodial-ledger policy are explicit in service health.
• The authenticated Imperial profile PDA—not the wallet address—is the USDC conversion receiver.
• Only fresh, self-funding Jupiter, Phoenix and GMTrade routes are eligible.
• Ambiguous submissions are quarantined and never blindly retried.

Leverage can lose the full deployed margin. The reserve floor reduces exposure; it does not guarantee a profit or prevent all losses.

Deployment status

The fee-backed strategy runs as an unaudited, capped mainnet beta. StonkPerps periodically validates the wallet-scoped Imperial JWT against the pinned profile without exposing the credential or balance. Fee conversion, intent creation, order preflight, submission, lifecycle reconciliation and risk-triggered closes are automated. Burn and buyback settlement still requires a wallet signature and is reported as queued until that occurs.