Tasks
Tasks are how you prepare and run mint-related work across many wallets. Everything lives inside task groups. Each group is tied to one wallet group and carries the contract and module context for the mint you are targeting.
Task groups
A task group is a named container. It stores the contract address (when applicable) and the module you chose when the group was created. Individual tasks inside the group inherit that context.
Create a task group
Go to Tasks in the sidebar.
Click New Task Group in the header.
Enter a name you will recognize later.
Enter the contract address when the workflow asks for it. Some modules fill or lock this field after you fetch collection data.
Choose how to drive the group:
Manual (default) if you will use ABI or raw calldata when adding tasks.
OpenSea if you are minting from an OpenSea collection. Paste the collection URL or slug, then click Fetch and confirm the chain and stages.
Rarible / Merkle Proof for the allowlist flow that needs an RPC and Fetch to detect phases.
Finish creating the group.
If you pick a module, the Add Task dialog hides the manual ABI and HEX paths and shows module fields such as stage and quantity instead.
Supported mint modules
Manual
Contract address
No fetch step
ABI or HEX calldata, value, gas and execution mode
Use this when you know the contract function or already have calldata.
OpenSea
Collection slug or URL
Loads collection chain, contract and mint stages
Stage and quantity
Public stages can use direct on-chain encoding; API-based stages may resolve proof or signature data at runtime.
Rarible / Merkle Proof
Contract plus RPC selection
Detects allowlist phases through the selected RPC
Phase and quantity
Proof data is prepared per wallet. Use Refresh Phases for fresh data when creating tasks.
Open a group
Click a task group card to open its detail view. From there you add tasks, run them and review status.
Adding tasks (quick steps)
Open the task group.
Click Add Task.
Pick wallets from the selector (groups expand, each wallet has a checkbox).
Fill the left column for your group type (manual ABI or HEX or module stage and quantity).
Fill the right column for Transaction and gas, then Additional settings (execution mode, optional schedule, optional nonce).
Click Create Task.
The next section explains every important field in that dialog.
Add Task dialog reference
The dialog is split into two main columns. The left side is about who signs and what data goes on chain. The right side is which RPC, how much ETH, fees and gas and how the app should run the task.
Wallet selection
The wallet button shows how many wallets are selected. Open it to see all groups. Expand a group, use Select all on the header row if you need everyone in that group, then tick individual wallets. Only checked wallets receive a task row when you create.
Manual groups: ABI or HEX
When the group is manual, you choose an input method:
ABI: Paste the contract ABI as JSON. The app parses it so you can pick a function and fill parameters. Some parameters support a wallet placeholder so each task uses the correct signer address. You can switch to raw JSON editing when needed.
HEX: Paste a full calldata string that starts with
0x. No function picker appears.
Validation errors call out missing RPC, bad hex length, invalid ABI JSON, empty parameters and similar issues before the task is created.
Module groups: stage and quantity
When the group uses OpenSea or Rarible / Merkle Proof, the left column shows module controls instead of ABI and HEX. Typical pieces are stage or phase and quantity. Value (ETH) on the right may show (Auto) when the price comes from the selected stage and quantity.
For OpenSea groups, public stages can be encoded directly while API-based or allowlist stages may resolve proof or signature data at runtime. For Rarible / Merkle Proof groups, the app builds per-wallet proof data; if you need a different phase after task creation, create fresh tasks for that phase.
Transaction and gas (right column, top card)
RPC endpoint Pick the endpoint for the chain this contract lives on. Wrong chain means failed simulations and failed sends.
Value (ETH) ETH sent with the transaction, often the mint price. Leave it as the app sets it when (Auto) appears for a paid module stage.
Auto gas This toggle only appears when Execution mode is Simulation. Turn it on to let the app pull max fee and priority fee from the selected RPC. Manual fee inputs are hidden while Auto gas is on. Turn it off to type your own Gwei values in Simulation mode.
Gas Multiplier
This field appears when Auto gas is on. It adds a buffer to the fees pulled from the network. The default and minimum are 1.15, which means a 15% buffer, and the UI allows values up to 10. Increase it carefully because higher multipliers can raise transaction cost.
Max fee (Gwei) and Priority fee (Gwei) These are EIP-1559 fields. Max fee is the most you agree to pay per unit of gas. Priority fee is the tip that encourages validators to include you sooner. The UI keeps priority from exceeding max when both are manual. In Trigger mode these fields are only required when Trigger Gas Strategy is User Defined.
Gas limit This is how many gas units the transaction may consume. In Simulation mode the box is disabled because the pipeline derives a limit from simulation. In Direct, Spam and Trigger modes you must set a positive gas limit yourself. Too low and the transaction reverts out of gas. Too high still caps spend by what the contract actually uses, but you should not treat a huge limit as harmless if you also set aggressive fees.
Additional settings (right column, lower card)
Execution mode
The label in the app is Execution mode. It has four options:
Direct No simulation step before broadcast. Auto gas is not available. You enter max fee, priority fee and gas limit yourself. Use this when you already trust your gas numbers or your workflow does not rely on a dry run.
Simulation The app can simulate before sending so gas and limits can follow real contract behavior. Auto gas is allowed here. Simulation delay (ms) adds spacing between simulation related steps when you want to avoid hammering the RPC. If Auto gas is off, you still type fees manually, but gas limit behavior stays tied to simulation rather than a fully manual Direct send.
Spam The app can submit Spam count separate attempts (from 1 up to 100 in the UI) with Spam delay (ms) between them. Auto gas is off and you must set fees and gas limit yourself. This mode exists for aggressive mint conditions where multiple transactions might be fired in sequence. The yellow warning is serious: Spam mode can drain your wallet. Use small counts and delays until you understand cost.
Trigger
The app watches pending transactions over a WSS RPC, then broadcasts your grouped wallets when it sees a matching transaction. Use a wss://... endpoint in Trigger WSS RPC. Fill Method Selector or Signature with an 8-character selector such as a9059cbb or a function signature such as mint(). Use Sender Filter (Optional) when you only want to react to transactions from one 0x... address.
Trigger Gas Strategy controls how the app prices the triggered send:
Slightly Below Pending uses fees just below the pending transaction.
Match Pending matches the pending transaction fees.
User Defined uses the manual max fee and priority fee you enter.
Trigger mode is powerful and sensitive to filters. Test with a small wallet set first and avoid broad selectors or aggressive gas settings unless you understand the cost.
Schedule
Turn Schedule on to pick a time with seconds. There is no separate date control in this dialog. The app interprets your time in local hours and minutes and schedules the next moment that matches. If you choose 14:00:00 and it is already 15:00 today, the run targets 14:00 tomorrow. If the chosen time is in the past relative to validation rules, the app rejects the task and asks for a valid schedule.
Nonce override (optional)
Advanced use only. Leave this empty unless you intentionally manage nonces for replacement or ordering. Wrong nonces cause stuck or dropped transactions.
Footer
Create Task saves after validation passes. You can edit tasks later by selecting rows and using Edit selected tasks (pencil icon) in the group toolbar or delete multiple tasks with the trash icon when you need a clean slate.
Running tasks
One task: use the play icon on that row. When the state allows it, the same control switches to a stop action.
Whole group: inside the open group, use the green Start all tasks control (play icon) in the toolbar beside the group title. The orange Stop all tasks control (stop icon) cancels queued work or tasks that are safe to interrupt.
Preparation steps can take time while the app builds calldata and resolves allowlist proofs per wallet depending on the module.
Task status
Statuses move in a rough pipeline. Exact labels match what you see in the app.
Ready
Configured and waiting to start
Preparing
Fetching collection data or building calldata per wallet
Simulating
Running a simulation before send (when that mode applies)
Scheduled
Queued to broadcast
Sending
Transaction in flight or being submitted
Success
Finished successfully on the paths the app tracks
Failed
Validation, RPC or chain error (see logs or error text)
Cancelled
Stopped from the UI or orchestration
Stopping tasks
You can stop individual tasks when the UI allows it or use Stop all tasks for the group. Cancellations do not reverse transactions that already landed on chain. Spam style runs may still complete a send if timing overlaps with your stop action.
Practical tips
Match the RPC chain to the contract you mint against.
Use
wss://endpoints only for Trigger mode; normal task setup still uses the selected HTTP RPC.Test Trigger with one or two wallets before you run a full group.
Click Fetch and confirm chain, contract and stage before creating module tasks.
For Rarible / Merkle Proof groups, create fresh tasks if you need to switch to a different phase after task creation.
Dry run small quantities or cheap networks before you scale up.
Double check contract addresses, stages and wallet selection before you execute.
Keep extra native token in wallets for gas spikes.
Related
Last updated