Multi-Airdrop Batch Claimer

WHAT IT DOES

This tool enables you to claim tokens from multiple Merkle-based airdrop distributors in a single batch session. You add one or more claim entries, each with a distributor contract address, claim amount, Merkle proof, and claim function signature. The tool processes each claim sequentially, checking if you have already claimed before submitting each transaction. It supports three common claim function signatures: claim(bytes32[] proof, uint256 amount), claim(address user, bytes32[] proof, uint256 amount), and claimTokens(bytes32[] proof, uint256 amount, address token). The tool tracks the status of each claim (pending, ready, success, claimed, or failed) and provides real-time progress feedback.

HOW TO USE

Connect your EVM wallet to the network where your distributor contracts are deployed. Add claim entries by clicking "Add Claim Entry" and filling in the distributor address, claim amount, token decimals, claim function, and the Merkle proof (one hex string per line or comma-separated). Optionally specify a beneficiary address for claimMulti functions—leave blank to use your connected wallet. Review the batch summary showing total entries, total amount, and status breakdown. Click "Batch Claim All" to process all ready claims sequentially. The tool will check each claim's status, skip already-claimed entries, and submit transactions for the rest. Progress is displayed with a status bar and per-entry status badges. After completion, you'll see a summary of successes and failures.

TECHNICAL MECHANISM

The tool maintains an in-memory array of claim entries, each with its own distributor address, amount, proof text, decimals, function signature, and beneficiary. When you click "Batch Claim All", the tool filters for entries that are valid and not yet claimed. It then processes claims sequentially (PLAYBOOK-C §5 rule 6) to avoid nonce conflicts that would occur with parallel transactions. For each claim, it first performs a pre-check using claimed(), isClaimed(), or hasClaimed() view functions to detect already-claimed status and skip wasted gas. It then parses the proof text by splitting on newlines and commas, filtering for valid 32-byte hex strings. The tool dynamically encodes the appropriate function call based on the selected signature, using ethers.js to create contract instances and submit transactions. Each transaction waits for confirmation before proceeding to the next, ensuring nonce ordering and allowing the user to see per-claim progress. The tool updates entry statuses (pending → ready → success/claimed/failed) throughout the process and reflects these in the UI via status badges and a progress bar. Gas costs are reported using receipt.effectiveGasPrice for accuracy post-EIP-1559.

WHAT IT CANNOT SEE

This tool cannot generate Merkle proofs or trees off-chain—it requires pre-generated proofs from each airdrop organizer. It cannot verify the fairness or correctness of off-chain Merkle trees across multiple distributors; it trusts each organizer's tree construction. It cannot detect if the user has already claimed through other means across different contracts beyond what each contract's view function reports. It cannot recover from a failed intermediate claim if batching is not atomic—if one claim fails, the batch continues with the remaining claims, but the failed claim must be retried separately. It cannot claim on behalf of others without their private key or an authorized signature, except when using claimMulti with a specified beneficiary but the transaction must still be signed by the caller. It cannot guarantee that all distributors use the same claim function signature—you must select the correct signature for each entry. It cannot handle distributors that require different beneficiary addresses or token approvals in a single batch; each claim is a separate transaction with its own parameters.

PLEASE NOTE

EVM chains only. This tool works with any EVM-compatible network. You must have the Merkle proofs provided by each airdrop organizer—this tool does not generate proofs. The tool processes claims sequentially, not atomically; each claim is a separate transaction, so gas costs are incurred per claim. Ensure the claim amount matches the amount in each Merkle tree; mismatched amounts will cause proof verification to fail. Always test with small amounts on testnet first. The tool does not store any data; all state is on-chain. Gas costs vary by network and proof length (longer proofs = higher gas). For distributors with custom claim functions not covered by the supported signatures, you may need to use a custom script or adjust the function selection per entry.