purrpLaunch
Protocol documentation

Stonk fees power a protected perps flywheel.

Each launch keeps its original vault while a capped slice can route through Zeta Markets. Principal and realized PnL return to the same coin economy.

Overview

Purrp constructs the standard Raydium LaunchLab create transaction with Stonk's platform config and names a deterministic per-coin router wallet as the pool creator. Proceeds that reach that wallet are verified, converted to USDC, and credited to the creator, strategy-vault and insurance ledgers.

01
Launch
Create the coin through Stonk. The fee router is bound at creation.
02
Collect
Creator proceeds reach the per-coin router wallet and are converted to USDC.
03
Vault
75% to the strategy vault, 15% to insurance, 10% to you.
04
Route
At most 25% of the vault enters a 2× position on Zeta Markets.
05
Settle
Realized profit queues 40 / 30 / 30 as burn, buyback and liquidity.

Launch flow

  1. Connect a Solana wallet and choose a live Stonk quote pair (a LaunchLab config).
  2. Upload token metadata. The image and JSON are pinned before the transaction is built.
  3. The server derives the coin's router wallet, builds the create instruction with platform 4E876qZT…, and partially signs with the mint and the router.
  4. You review and sign as fee payer. Purrp never receives your private key.
  5. After confirmation the launch is indexed and fee monitoring begins.

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

Fee routing

Stonk's platform config charges 1% on every curve trade and sets the on-curve creator fee to zero. Creator proceeds therefore begin at graduation, when the pool migrates to a Raydium CPMM pool and the creator fee share on that pool accrues to the router wallet. 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%.

Each beta conversion is capped at $100 of output. Uncertain outcomes are quarantined instead of retried, and confirmed balance deltas are verified before any ledger is credited.

Protected vault

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. Principal returns to the vault when a position closes. Creator and insurance allocations are never counted as strategy collateral.

Perps strategy

Once a coin's vault can supply at least $5 of deployable margin, the worker creates a strategy intent for the market and side chosen at launch. Leverage is capped at 2×, collateral at the lower of 25% of vault capital or $25, and routing slippage at 1%. Before submission the engine requires a fresh mark from Zeta Markets, checks the vault covers the full cash ledger, and runs a side-effect-free preflight. Positions 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. Burn and buyback amounts remain queued until the custody wallet signs their on-chain settlement. The interface never labels a queued allocation as a completed transaction.

Risk controls

  • 25% maximum vault deployment, $25 collateral cap and 75% reserve floor.
  • 2× maximum leverage with ±10% exits and a 24-hour maximum hold.
  • One live routed strategy per coin at a time.
  • Separate launch, fee-sweep, conversion, router and strategy approvals.
  • Ambiguous submissions are quarantined and never blindly retried.

Deployment status

Capped mainnet beta. Launch, indexing and the fee ledger are live. Fee conversion, routing and closes run through the engine worker and are reported on each coin's flywheel page with their signatures. Burn and buyback settlement requires a custody signature and is reported as queued until then. The engine is unaudited.