Multi-Round Airdrop Scheduler

WHAT IT DOES

This tool enables you to deploy and manage multi-round airdrop distributors with granular control over each round's parameters. You can deploy a new multi-round distributor contract, schedule new rounds with individual Merkle roots and time windows, update existing round parameters, activate or deactivate rounds, and transfer token allocations between rounds. The tool reads current round numbers, start and end timestamps, claim status per address per round, token balances, owner roles, and Merkle roots for each round. It supports complex airdrop campaigns where participants are eligible for different amounts across multiple phases, with each round having its own claim window and proof requirements.

HOW TO USE

Connect your EVM wallet to the network where you want to deploy or manage the distributor. For deploying a new multi-round distributor, enter the token address, total amount, and token decimals—the tool will deploy the contract and transfer tokens to it. For managing an existing distributor, enter the contract address and select an action: schedule a new round (provide round number, start/end timestamps, and optional Merkle root), update round parameters (modify any combination of start, end, Merkle root, or amount), activate or deactivate a round, or transfer tokens between rounds. The tool displays current round information and a preview of the action. Review the changes, then click Execute to send the transaction. The tool will confirm the transaction and display the result with gas cost.

TECHNICAL MECHANISM

The tool uses a multi-round distributor contract that implements round-specific storage using a mapping from round number to a struct containing start time, end time, Merkle root, total amount, and claimed amount. For deployment, it uses a factory pattern to create a new distributor instance with the specified token and initial parameters. For scheduling, it calls scheduleRound(uint256 round, uint256 start, uint256 end, bytes32 merkleRoot) which validates that the round does not already exist and that the timestamps are valid. For updates, it uses updateRound or setRoundAmount to modify specific parameters without affecting others. Round activation is handled through activateRound and deactivateRound functions that toggle a boolean flag, allowing the owner to pause individual rounds while keeping others active. Token transfers between rounds use transferRoundTokens(uint256 fromRound, uint256 toRound, uint256 amount) which moves unclaimed tokens from one round's allocation to another, updating the total amount for both rounds. The contract tracks per-address claims per round using a nested mapping (address => mapping(uint256 => bool)) to prevent duplicate claims. All functions include onlyOwner modifiers to ensure only the contract owner can perform administrative actions. The tool uses ethers.js to encode function calls, estimate gas, and handle transaction receipts with effectiveGasPrice for accurate cost reporting.

WHAT IT CANNOT SEE

This tool cannot verify off-chain reasons for round scheduling, such as community engagement metrics, performance milestones, or external event triggers—these must be determined by the organizer. It cannot prove that round allocations are fair across participants or that the distribution strategy is equitable. It cannot adjust claims that have already been claimed in previous rounds—once a claim is made, it is permanently recorded on-chain. It cannot guarantee that participants will claim in future rounds or predict optimal round timing for participant engagement. It cannot detect if participants are unable to claim due to external factors such as gas prices, wallet compatibility, or network congestion. It cannot automatically rebalance allocations if some rounds are under-claimed. It also cannot revert a scheduled round once the transaction is mined.

PLEASE NOTE

EVM chains only. This tool works with any EVM-compatible network. Only execute actions if you are the authorized owner or administrator of the distributor contract. Multi-round distributors are complex—thoroughly test on testnet before mainnet deployment. Ensure that round timestamps do not overlap unless intended, and that Merkle roots are correctly generated off-chain for each round. The tool does not store any data; all state is on-chain. Gas costs vary by network and contract complexity. For custom distributor implementations with non-standard function signatures, you may need to interact directly via a custom script.