Merkle Airdrop Deployer

WHAT IT DOES

Merkle Airdrop Deployer lets you create and deploy Merkle-based airdrop claim contracts for token distribution. You provide a list of recipient addresses and their corresponding token amounts, and the tool computes the Merkle root, deploys a claim contract, and handles funding the contract with the required tokens. Recipients can then claim their tokens by submitting a Merkle proof, paying their own gas fees, making this approach significantly more gas-efficient for large-scale distributions than sending tokens individually.

HOW TO USE

Connect your wallet using the built-in wallet connector. Enter the token contract address you wish to distribute and the Merkle airdrop factory contract address (you provide both — no hardcoded addresses). Paste your recipient list in the format "address,amount" (one per line) and click parse to compute the Merkle root and total token amount. Review the contract owner, your token balance, and the configured expiry blocks. Click "Deploy airdrop contract" to deploy the Merkle claim contract. After deployment, click "Fund contract with tokens" to transfer the tokens from your wallet to the claim contract. The deployed contract address is displayed upon successful deployment.

TECHNICAL MECHANISM

The tool computes a Merkle tree from the recipient list by hashing each (address, amount) pair and pairing them recursively until a single root hash remains. This Merkle root is passed to the factory contract during deployment, along with the token address and an expiry block number. The factory deploys a minimal proxy claim contract that stores the root, token address, and tracks claimed amounts. Recipients can call the claim() function with their index, address, amount, and a Merkle proof derived from the tree. The contract verifies the proof against the stored root and transfers the specified amount if valid. The tool uses the factory contract pattern to avoid redeploying the entire claim logic for each airdrop, saving gas and reducing deployment costs.

WHAT IT CANNOT SEE

This tool cannot verify recipient addresses are valid externally owned accounts or contracts. It cannot detect if recipient contracts support token transfers or have custom logic that might revert. It cannot detect or prevent failures due to token-specific mechanisms including rebasing, fee-on-transfer, blacklist functionality, pausing, or custom transfer logic. It cannot simulate transactions or prevent reverts from custom recipient contract logic. It also cannot verify that the provided token contract address is a legitimate token. It cannot guarantee that all recipients will successfully claim their tokens or that recipients haven't already claimed through other mechanisms. It cannot ensure the Merkle root is correctly computed from the recipient list beyond the tool's own computation. It cannot recover unclaimed tokens after the claim period expires unless the contract implements a recovery mechanism.

PLEASE NOTE

This tool works on EVM-compatible chains only. It requires the wallet to be connected and the current network to be one of the supported chains listed in the BotGentz registry. The token contract address and factory address must be provided manually by the user. Always review the contract address, Merkle root, and total amount displayed before signing any transaction. Users are responsible for ensuring recipient addresses are correct and that they have sufficient balance to fund the airdrop contract. After deployment, the airdrop is self-service — recipients must claim their tokens independently. This tool does not provide a user interface for recipients to claim tokens; you must provide the contract address and Merkle proofs to recipients through other means.