Configure a token, coordinate bundled entries, and manage exits from one surface.
Operator session active
01
Launch configuration
Asset, routing, and execution parameters
On-chain
Launch route
Taxed windows decay 99%→0 linearly; proceeds go to Virtuals’ vault, not the creator. Your own dev buy & bundle snipers pay it too — leave on None unless you want outside snipers punished more than you profit.
Fee directing (Bags)Recipient · %
Split the 1% creator fee across up to 100 recipients (must total 100%). Each recipient can be a wallet 0x…, a social handle — @handle or x:name, github:name, tiktok:name, instagram:name, kick:name — or dev for the launching wallet. Social handles resolve to the person’s Bags EVM wallet (they claim by logging into bags.fm). No rows = 100% to the dev wallet. Social handles need a Bags API key in .secrets/bags-api-key (from dev.bags.fm).
Token identity
Capital & address
Gives every selected sniper a different random buy in the range — breaks the equal-amount fingerprint. Edit any row afterward.
Bundle walletsBalance · Buy amount
Fee …Supply 1BMax wallet 2% / 366 blocks
Launch fee plus dev buy is settled from the selected dev wallet.
02
Execution result
Latest launch transaction
Session
No launch submitted in this session.
03
Sell cockpit
Live position monitoring and exits
Wallet holdingsExit amount · % of position
Global exitSells 100% from every non-archived managed wallet.
Portfolio intelligence
Performance
Mark-to-market launch performance and accrued creator revenue.
01
Launch portfolio
Realized proceeds plus current holdings
Live spot
MethodologyPnL = sells + creator fees earned + current holdings − dev buy, launch fee, sniper buys, and gas. Holdings use live spot price. "Earned" counts creator fees actually claimed (Virtuals USDG payouts and V3 LP fees, measured as the ETH/WETH the claiming wallet gained); fees still unclaimed show in the Fees tool, not here.
02
Creator fees
Trading revenue earned by launched tokens
Scan Noxa, Trench, Flap, and Virtuals for claimable creator fees.
SettlementNoxa and Virtuals show exact amounts. Trench and Flap settle through each pad’s creator claim flow. Claim before retiring a dev wallet.
Configuration
Settings
Defaults applied to every new launch. Change them here instead of editing the app.
01
Launch defaults
Pre-filled on the Launch desk; you can still override per launch
Treasury operations
Wallet operations
Manage signing wallets, isolated groups, and private funding routes.
Local vault available
01
Wallet inventory
Balances, roles, keys, and active execution wallet
Local vault
Createsnipers
Active walletThe active main is the default dev and funding wallet used by Launch desk.
02
Wallet groups
Isolated funder and sniper sets for each launch
Create isolated groupA new funder plus a dedicated sniper set.
⚡ Prep next group (one-click)After a launch: creates a fresh group (sniper count above), sets it active, and hop-funds it — automatically draining your richest group (the one you just launched from) as the source. Uses the amount/depth settings above.
Recovery scannerFind and reclaim residual ETH from every prior hop session.
04
Move ETH
Transfer between managed wallets
05
Consolidate
Recover capital to the active main
Sweep sniper ETHMove all available sniper ETH to main.
Direct sniper funding is disabledUse the private hop route. A direct main-to-sniper transfer creates a traceable link and clusters the entire wallet set.