Skip to main content

woosh heatup

The heatup module simulates token market activity using worker wallets. It performs slow-paced buy/sell operations on each wallet to make them appear active prior to an actual token launch. This helps avoid labeling the wallets as bot-controlled by creating realistic on-chain interaction history.

Note: This module uses Jupiter API and introduces intentional delays of 3–5 seconds per transaction. It is designed to run before the token distribution, ideally a day prior to launch.

Usage:

woosh heatup <option>

🔹 woosh heatup buy​

This command simulates token buy transactions from each worker wallet using the configuration provided in woosh.config. Usage:

woosh heatup buy

Required Config Section:​

"heatup_settings": {
  "heatup_token_a": "So11111111111111111111111111111111111111112",
  "heatup_token_b": "6p6xgHyF7AeE6TZkSmFsko444wqoP15icUSqi2jfGiPN",
  "buy_amount_a": 0.001,
  "slippage": 50,
  "delay_in_sec": 1
}

Field Descriptions:​

  • heatup_token_a: The token address to spend while buying. By default, this is the wrapped SOL (WSOL) address. You may change this only if you're confident about what you're doing.

  • heatup_token_b: The token address to purchase with each worker wallet. This is typically your token's mint address.

  • buy_amount_a: Amount of heatup_token_a (usually SOL) each worker wallet will use to buy heatup_token_b. ⚠️ Must be less than the wallet's SOL balance, else the command will fail.

  • slippage: The slippage in basis points (bps). For example, 50 means 0.5% slippage. 🔸 Recommended value: 50.

  • delay_in_sec: Artificial delay between each buy operation. Use 1 for minimal delay. Useful for simulating human-like interaction timing.

🔹 woosh heatup sell​

This command simulates token sell transactions from the worker wallets and closes any token accounts created in the process. It is typically used after heatup buy to complete the simulation loop. Usage:

woosh heatup sell

No additional config fields are required beyond heatup_settings.