Execution workspace
Launch desk
Configure a token, coordinate bundled entries, and manage exits from one surface.
Operator session active
01
On-chain
Launch configuration
Asset, routing, and execution parameters
Launch route
Three-second opening protection
The atomic dev buy is exempt. Bundle wallets wait until ArgusPad’s 99%→0 opening tax has cleared, then enter the live V4 pool.
The atomic dev buy is exempt. Bundle wallets wait until ArgusPad’s 99%→0 opening tax has cleared, then enter the live V4 pool.
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
The selected dev wallet pays gas plus any launch fee and dev buy shown above. The selected launchpad determines whether funds use native or ERC-20 USDC.
02
Session
Execution result
Latest launch transaction
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.