Tips & Best Practices

Get the most out of the bot safely.

Security

• The bot auto-deletes private key messages after saving. Still — never paste keys in group chats. The bot only responds in private DMs.
• Your session config (CA, gwei, toggles) is Fernet-encrypted and stored on disk. It survives bot restarts.

Gas Strategy

• No Gas Limit is safer.Each wallet's own estimation catches reverts before gas is burned.
• Set gwei before Gas Limit. Priority gwei auto-clears if you lower the base gwei below it.
• For competitive mints, use ETH-FLASHBOT to avoid front-running.
• Use /simulate to test your config before firing — it shows whether the tx would succeed or revert, plus the gas used, without spending real gas.

Trigger Strategy

• Estimate trigger is the safest auto-trigger. It only fires when the contract is live, and each wallet still estimates at broadcast time when Gas Limit is not set.
• Timestamp trigger is the fastest. No estimation at fire time — raw broadcast the instant the clock hits. Gas Limit is required — if the contract reverts, gas is burned on every wallet.
• ETH-FLASHBOT + Timestamp: Set the timestamp 50–100 seconds before the actual drop time. Flashbots targets the next ~25 blocks (~5 min window), so the tx must be submitted early. Sending at the exact drop time means your tx lands too late.
• For OpenSea drops, use /opensea to auto-fill everything, then just set Gas Limit and gwei.

Multiple Tasks

• You can run multiple auto-trigger tasks simultaneously. Each has its own config snapshot taken at creation time.
• Changing your session config after creating a task does not affect that task — it uses the config from when it was created.
• Per-contract wallet cap is 25 by default (cumulative across tasks for the same CA + chain).

Custom RPC

• Bring your own RPC nodes via RPC : Defaulton the main menu. The bot validates each URL's chain ID before saving.
• Using custom RPCs removes the 25-wallet per-contract limit— since you're not using shared infrastructure.
• Use Test Latency to check your endpoints. Dead nodes slow down your transactions.

Templates

Templates are pre-made configs created by the bot owner. Use /template to browse available templates.

• Tap a template to see its full config — chain, CA, method, params, payable, gas limit, and trigger settings.
• Tap Apply Template to load the config. A confirmation prompt appears before applying.
• Templates set chain, CA, method, params, payable, gas limit, and trigger settings. Gwei is not included — you always set your own gas price.
• Applying a template overwrites your current config but nothing is locked — you can edit any field after applying.