Choose the correct workflow

Mint type Use when Recommended route Main risk
Public FCFS Anyone can mint when stage opens PUBLIC Sellout and fee competition
Allowlist Your wallet has a proof/signature PUBLIC or supported private route Wallet-bound eligibility
Scheduled Known opening time Route chosen for the stage Wrong time, stale data, late worker
SeaDrop Supported OpenSea/SeaDrop stage Direct wallet or compatible delegation Stage/calldata resolution
Custom contract Verified ABI and mint method are known Configured adapter Wrong function or arguments
Official authorization Project requires a server-issued ticket Frontend authorization bridge Expired or wallet-mismatched ticket

Public FCFS

  1. Verify contract, chain, stage, time, and limit.
  2. Add the drop early.
  3. Create the task and select wallets.
  4. Use PUBLIC when the goal is fastest public propagation.
  5. Preflight near launch.
  6. Confirm spend and arm.
  7. Execute at go-live and watch per-wallet submission.

<aside> ⚠️

A fast submit is not a guaranteed mint. A transaction can reach the network quickly and still lose the race for block space or supply.

</aside>

Allowlist

  1. Confirm each selected wallet is on the list.
  2. Resolve the allowlist stage, price, quantity, proof, or signature.
  3. Do not move a proof/signature from a whale or another wallet into your own task.
  4. Simulate from the actual minting wallet.
  5. Fire within the stage window.

Common allowlist failures