Launch
Launch creates a token on the selected chain and launchpad. Select the chain and launchpad in the node inspector; the node shows only the inputs relevant to that choice. Supported launchpads are:
Every launch needs prepared Launch Data, a buy amount, tip amount, and a compatible wallet. Chain-specific inputs differ:
Launch Data contains:
- Name and ticker.
- Exactly one image source: an image URL or generated image data.
- Optional X and website URLs.
Pump.fun options
Pump.fun options
Pump.fun launches can also receive a bundle configuration, cashback setting, USDC setting, and fee-share recipients. Use Pump.fun Fee Share From Wallet for one recipient receiving the complete allocation, or Pump.fun Fee Share Make for multiple recipients and percentages that total 100. See Configure Pump.fun Fee Sharing for the exact ports.
Four.meme fanout wallets
Four.meme fanout wallets
A Four.meme launch can include optional Fanout Wallets. The graph editor accepts up to six additional BNB wallets. Each selected wallet adds the fee shown in the app.
Suggest only
Suggest only
Set Suggest Only when the graph should propose the launch instead of executing it. Add a strict suggest-only expectation to tests when this distinction is safety-critical.
Prepare Launch Images
Use Draw Ticker to turn text into a launch image. The graph value must use one of these exact styles:
Connect either the generated image URL or generated image data to Launch Data Make, not both.
Buy And Sell
Buy selects Solana or BNB and then the launchpad. It requires the token address, amount, priority fee, and a compatible wallet; minimum output is optional. BNB trades also use Gwei. Pump.fun and PumpSwap buys use the fee-vault value shown by the node. Dedicated Buy Solana, Sell Solana, Buy BNB, and Sell BNB nodes are also available for chain-specific graphs. Tests can assert chain, platform, wallet, token or mint, amounts, fees, and other relevant fields.Await A Transaction Response
Await TX Response waits for a result associated with the identifier returned by a launch or trade. Choose the response you need:- Submit signature
- Confirmed
- Failure
- Error
- Mint
- Metadata
- Four.meme token
- Simulation
Delay
Delay pauses an execution path for a number of seconds. Supply the duration as an input or set the node’s default delay. Do not use a delay as a substitute for Await TX Response when later work depends on an actual transaction result.Notify
Notify records a notification effect in the execution trace with aninfo, warning, or critical level. It does not deliver an external message or alert. Use it to annotate outcomes, rejected events, or recoverable conditions for later trace inspection.
Keep high-volume ignored events silent unless their trace needs an explicit marker.