Getting StartedWalletsContract SetupGas SettingsCustom RPCMinting & TriggersMint ModulesOpenSea SeadropFunds ManagementCommandsTips

Mint Modules

Pre-configured flows for complex mints like Merkle proofs, signature mints, and dynamic pricing.

What Are Modules?

Some contracts require more than a Method ID and Params — they need Merkle proofs from an API, signed vouchers, on-chain price lookups, or data from a local file. Mint modules handle all of that automatically.

Modules are created and managed by the bot admin. If you need a module for a specific mint, reach out to the admin — they can add one without restarting the bot.

How to Use

On the main menu, tap Module : None. This opens the module list showing all available modules.

  1. Tap a module to see its details — contract address, chain, method, and what steps it runs.
  2. Tap Use This Module to activate it. The module auto-fills your CA, Method ID, Payable, and Gas.
  3. If the module needs input from you (like mint quantity), the bot prompts for each value before activating.
  4. If the module specifies a chain, your chain is auto-switched to match.
  5. Set your Gwei, configure your trigger, and fire.

When a module is active, the main menu shows Module : <name> and the config summary includes the module name. To deactivate, open the module menu and tap Deactivate Module.

What Modules Can Do

Each module defines a series of steps that run automatically for every wallet before broadcasting. Common patterns:

  • Merkle proof mints— fetches your wallet's proof from the project's API and injects it into the transaction.
  • Signature mints — calls an API to get a signed voucher for your wallet, then includes it in the mint call.
  • Dynamic pricing — reads the current price from the contract and calculates the exact payable amount.
  • Local proof files— reads proofs from a file on the server when the data isn't available via API.

Pre-fetching

By default, when you create an auto-trigger task with a module, all steps run immediately at task creation time for every wallet. The results are cached so that when the trigger fires, transactions broadcast instantly with zero API delay.

If a wallet isn't on the allowlist, you'll know right away at task creation — not mid-broadcast.

Some modules may have pre-fetching disabled (the admin configures this) when the proof or signature expires quickly. In that case, steps run at broadcast time instead.

User Inputs

Some modules prompt you for values when activating — like mint quantity, tier selection, or a referral code. These are shown as text prompts in order. Your inputs are saved until you deactivate the module.

How It Works with Triggers

  • Estimate trigger— the module's resolved calldata is used for gas estimation. Once the contract stops reverting, transactions fire instantly.
  • Timestamp trigger — pre-fetched data is cached at task creation. At the exact timestamp, transactions broadcast with no API round-trip.
  • Instant (Fire Tx) — steps run per wallet right before broadcast.
Your gwei, Gas Limit, and trigger settings still apply normally when a module is active. The module only handles the calldata and payable — everything else is up to you.

Simulating with Modules

/simulate works with modules. It runs the module steps for your first wallet and simulates with the resolved calldata — so you get an accurate result even for proof or signature mints.

Proxies

Some modules require proxies to avoid API rate limiting. The module menu shows your proxy status: Default, Custom (N), or None.

  • Default proxy — provided by the bot admin. Limited to 2 wallets per task.
  • Custom proxies — add your own via the module menu. No wallet limit. Supports HTTP, HTTPS, and SOCKS5.
  • Tap Test Latency to check proxy response times.
Proxy-required modules will not activate without at least a default or custom proxy configured.

OpenSea WL

The OpenSea WL module is a built-in module for whitelisted OpenSea drops. It appears at the top of the module list.

  1. Enter the collection slug (from the OpenSea URL).
  2. Tap Select Phase to choose which WL phase to mint.
  3. Set your quantity.
  4. Tap Use OpenSea WL to activate.

The bot handles everything automatically — wallet authentication, fetching mint data, and broadcasting. Proxies are required.

Locked Fields

When a module is active, certain fields are locked to prevent accidental changes:

  • CA, Method ID, Params — always locked
  • Payable — locked only if the module sets it
  • Chain — locked only if the module specifies a chain

Deactivate the module first to edit these fields manually.