Tiered Airdrop Deployer

WHAT IT DOES

Tiered Airdrop Deployer lets you create and deploy token airdrop contracts with tier-based allocation structures. You define multiple tiers (e.g., Gold, Silver, Bronze) with percentage allocations of the total token pool, assign recipients to each tier with their specific amounts, and the tool deploys a single claim contract where recipients can claim their tokens according to their tier assignment. This is ideal for project launches, loyalty programs, or community rewards where different groups should receive different token allocations.

HOW TO USE

Connect your wallet using the built-in wallet connector. Enter the token contract address you wish to distribute and the tiered airdrop factory contract address (you provide both — no hardcoded addresses). Configure your tiers by entering a tier name and percentage of the total pool, then clicking "Add tier" (e.g., Gold 50%, Silver 30%, Bronze 20%). For each tier, paste the recipient list in the format "address,amount" (one per line) and click "Parse & build" — the tool will aggregate all tier data and compute the total token amount. Review the contract owner, your token balance, and the tier configuration. Click "Deploy tiered airdrop" to deploy the contract via the factory. After deployment, click "Fund contract" to transfer the tokens from your wallet to the claim contract. The deployed contract address is displayed upon successful deployment.

TECHNICAL MECHANISM

The tool deploys a tiered airdrop contract via a factory pattern. The factory receives the token address, tier names, tier percentages, recipient list (addresses and amounts), tier indices (mapping each recipient to a tier), and a claim expiry. The deployed contract stores tier metadata and allocation rules. Each recipient is assigned a tier index, and the contract enforces that the total allocation per tier matches the configured percentage. Recipients call the claim() function with their index to receive their allocated tokens. The contract tracks claimed amounts per recipient to prevent double claims. The tool sums all recipient amounts across all tiers to compute the total token amount required for funding, approval, and transfer. Claim windows can be configured per tier or globally through the factory parameters.

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. It cannot detect if recipients have already claimed through other mechanisms. It cannot ensure tier allocations are correctly enforced beyond the contract's logic. It cannot verify if recipients belong to the correct tier or meet tier criteria. It cannot recover unallocated or unclaimed tokens if the contract lacks a recovery mechanism. It cannot predict future gas costs for multiple claims. It cannot verify if recipients comply with KYC or regulatory requirements.

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. The token contract address and factory address must be provided manually by the user. Always review the contract address, tier configuration, and total amount displayed before signing any transaction. Users are responsible for ensuring recipient addresses are correct, that they have sufficient balance to fund the contract, and that tier allocations are properly configured. After deployment, recipients must claim their tokens independently through the contract. The tier percentages should sum to 100%, and the total amount of tokens funded must match the sum of all recipient allocations. This tool does not provide a user interface for recipients to claim tokens; you must provide the contract address and tier information through other means.