Mint Modes — Instant · Safe · Spam (speed & success, explained)

Minting comes down to two ideas:

• Fire once — send one transaction right at mint time.
• Keep hammering — keep sending until the mint opens and lands.

That choice is the mint mode. You pick one of three in the task editor.

🔘 The 3 mint modes

💡 The default is Spam — it wins most competitive mints (other platforms default to spam too). Switch to Instant/Safe whenever you like.

🛡️ What is Safe (Simulate)?

Simulate = a safety check that "test-runs" the mint before really sending it.

• Before sending for real, it does a dry-run (eth_call) against the chain.
• Any wallet that would fail (revert) — mint not open, not eligible, sold out, low balance — is skipped.
• Only wallets that pass actually send (once).

Why it's nice: it never sends a doomed transaction, so it doesn't waste gas.

⚠️ Important — Simulate is NOT "retry". It's a safety check, then one shot. If you start before the mint opens (e.g. 4:58 for a 5:00 mint), the dry-run fails → that wallet is skipped → the task ends. It does not wait or retry until mint time. 👉 To arm it early and catch the exact open, use Scheduled start or Spam.

🔥 What is Spam?

Spam = keep sending until the mint succeeds.

• While the mint is closed, attempts fail — but the moment it opens, it grabs the mint.
• On success (confirmed on-chain) it auto-stops — no extra gas burned.

This is the "don't know the time / it's competitive — just turn it on and it catches it" mode.

The 3 spam knobs

💡 Delay = how fast you hammer, Max tx = how many times, Guardrail = for how many seconds.

⚠️ Watch the guardrail trap! If the guardrail is set to e.g. 120s and you start a 5:00 mint at 4:55, it shuts off at 4:57 — before the mint even opens. If you start early, set the guardrail long enough or just turn it off. (It's off by default.)

⏰ Scheduled start — fire exactly at mint time

Set a start time on the task and the bot waits until then and fires precisely — even if you started it early. (Works with Instant, Safe, and Spam.)

• Example: mint is 5:00 PM sharp → set start to 5:00:00 PM, start early → the bot fires at exactly 5:00. A countdown shows on screen.
• No schedule → it fires the instant you press start. (That's why "arm it early" means Schedule or Spam.)

🏆 Winning a competitive mint (FCFS · Public)

To land a contested mint:

1. Scheduled start — fire at mint time (or Spam to arm it early)
2. Fast gas — auto (recommended) or manual-high → Gas guide
3. Spam — if it's fierce, keep hammering

💡 Simulate (Safe) is not a success booster — it's a gas saver. In a real race, dropping it can be faster (the dry-run costs a beat).

🎯 Recommended setup — "arm it and it grabs the mint" If you don't know the exact time or just want to land it, make a new task 1–2 minutes before mint and set:

1. Mint mode → Spam
2. Max tx → blank (unlimited)
3. Delay → 100–2000ms (0.1s–2s, your call)
4. Hit Start (or set a scheduled start at mint time)

Example: mint is 5:00 PM and you start the task at 4:59 → the bot fires non-stop at your chosen interval (0.1–2s) from 4:59 on. The moment it succeeds (confirmed on-chain) it auto-stops. So it keeps hammering until it lands (or you stop it).

• Easier on gas/RPC → use a larger delay (e.g. 1000–2000ms)
• More aggressive → use a smaller delay (e.g. 100–300ms)
• ⚠️ For a mint that can never succeed (sold out, not eligible) it would retry forever — stop it manually or cap it with Max tx.

👛 Minting with many wallets

Most people mint with many wallets (dozens). Two ways:

Either way, wallets fire in parallel — they don't queue one-by-one.

⚠️ Golden rule — "one wallet, one task" Don't run the same wallet in two tasks at once. Each wallet has a sequential nonce (0,1,2,3…). If two tasks use the same wallet, they grab the same nonce → only one lands and the rest fail "nonce too low", or they tangle and both just burn gas. 👉 That's why "one task per wallet" is safe (each wallet is bound to its own task). Putting different wallets in one task is fine (independent nonces).

🛡️ The app guards this for you. If a wallet is already minting in another task and you start a second task that also uses it, that one wallet is auto-skipped (a toast says "wallet 0x12…34 is already minting in another task — skipped") while the task's other wallets fire normally. The whole task doesn't stop.

🎯 Contract vs OpenSea drop — what's different

Pick in the editor's Target.

💡 OpenSea drops are much easier — ABI, args, and math are all automatic. Just paste the link and pick a phase. If ABI feels hard, prefer OpenSea drops / launchpads.

If contract arguments confuse you

Press Fetch ABI and the contract's function list loads automatically. Pick the mint function (mint, mintPublic, …) and the fields that function needs appear automatically (name + type). When filling them:

• {wallet} = auto-replaced with each wallet's address
• {tokenId} = auto-replaced with the token id
• If the function is payable, the Value (ETH) field is required (red asterisk).

⚙️ Defaults & why

🔎 See also: Public mint · Whitelist (WL) mint · Gas · Boost