Features Reference

<aside> ⚡

MintDash brings drop preparation, multi-wallet execution, routing, live observability, history, and PnL into one browser-operated mint workspace.

</aside>

Product map

Area	Main purpose	Important capabilities
Overview	Operational health	Upcoming drops, active runs, recent results, execution status
Wallets	Mint-wallet management	Import, generate, label, fund/distribute, archive
Drops	Collection and stage tracking	Contract resolution, stage discovery, pricing, timing, floor override
Tasks	Mint configuration	Wallet selection, quantity, gas, route, schedule, spend confirmation
Delegation	Supported delegated execution	SeaDrop/delegation setup and batch-oriented routes where compatible
History	Audit trail	Runs, per-wallet results, errors, hashes, timing
PnL	Portfolio measurement	Cost basis, floors, unrealized and realized PnL
Settings	Execution defaults	RPC, alerts, gas defaults, blast/prewarm controls where enabled
Admin	Platform operations	Global controls and platform-wide reporting for authorized admins

Multi-wallet execution

A single task can target several user-owned wallets. MintDash keeps results separated per wallet so one failure does not hide the outcome of the others.

Each wallet uses its own nonce and signature.
Wallet-bound allowlist proofs cannot be copied to another address.
Per-wallet limits still apply.
Total cost grows with wallet count and quantity.

Drop resolver

MintDash uses the contract, chain, and supported marketplace data to identify sale stages and prepare mint calldata.

Calldata confidence grades

Grade	Source	Meaning
A	Local/native adapter	Deterministic, directly supported encoding
B	Known custom ABI	Prepared from a configured contract method
C	Cached marketplace data	Previously resolved, should be refreshed near launch
D	Live marketplace dependency	Most exposed to rate limits or last-minute failure

Preflight and simulation

Preflight is the safety gate before money is sent. It checks known task inputs, eligibility, balances, calldata, nonce state, and simulation. A task should not be considered ready merely because it was saved.

Scheduling and arming

Scheduled tasks prepare work before the launch moment. Armed means the task is waiting for its fire condition; it does not mean a transaction is already on-chain.

FCFS/public execution

The PUBLIC route is designed for public FCFS competition where fast propagation matters. Warm/prepared tasks can reduce application-side delay, but block inclusion still depends on network state, fees, validators/builders, and supply.