Cross-Chain Airdrop Deployer

WHAT IT DOES

This tool deploys a cross-chain airdrop distributor contract that restricts claims to holders of a specific NFT collection (ERC721 or ERC1155) on one EVM chain, while the airdrop tokens are claimed on a different EVM chain. You specify the source chain where the NFT resides, the target chain where the airdrop will be claimed, the NFT contract address, the token address on the target chain, and the total amount. The deployed contract on the target chain verifies NFT ownership on the source chain either through a Merkle proof (if you supply a root generated from source-chain data) or via a cross-chain oracle/bridge that relays ownership proofs. The tool also handles token transfers from your wallet to the new distributor contract, optionally routing through a bridge if tokens need to move across chains.

HOW TO USE

Connect your EVM wallet and select the source chain (where your NFT is deployed) and the target chain (where the airdrop will be claimed). Enter the NFT contract address, choose the standard (ERC721 or ERC1155), and specify the ERC20 token address on the target chain. Input the total amount in human-readable units and the token's decimals. Optionally provide a Merkle root for proof-based claims; if left empty, the contract will use direct cross-chain NFT balance verification via an oracle. Set claim amount per NFT or leave it to be proportional to balance. Configure start and end timestamps to time-gate the claims. If you need to bridge tokens across chains, enable bridge mode and provide the bridge contract address and target chain ID. Review the deployment summary, then click Deploy. The tool will deploy the distributor on the target chain, transfer tokens (bridging if needed), and display the contract address and transaction hashes.

TECHNICAL MECHANISM

The tool deploys a cross-chain distributor contract on the target chain that implements a dual-mode claim system. For Merkle mode, claims are verified against a root generated off-chain from source-chain NFT holdings, using keccak256 hashing and Merkle proof verification to validate each claim without requiring on-chain source-chain reads. For direct mode, the contract uses a cross-chain oracle (such as Chainlink CCIP or Axelar) to request and verify NFT balance proofs from the source chain, with the oracle returning a signed attestation that is validated on-chain. The deployment uses a factory pattern with CREATE2 for predictable addresses across chains. If bridge mode is enabled, the tool approves the bridge contract to transfer the total token amount, initiates the bridge transaction, and waits for finality before deploying the distributor. All token transfers use safe ERC20 calls with return value validation. The contract includes start/end timestamps and a claimed mapping to prevent double-claims, with replay protection across chains using chain ID and nonce hashing.

WHAT IT CANNOT SEE

This tool cannot verify off-chain NFT holdings or prove sybil resistance across chains. It cannot detect if an NFT was acquired solely to claim the airdrop and then immediately sold. It cannot guarantee bridge reliability, finality, or security—bridges have their own trust assumptions and risks. It cannot see tokens held on other chains without a bridge or oracle, nor can it monitor cross-chain transaction status after initiation. The correctness of Merkle proofs and the fairness of allocations depend entirely on the user's off-chain generation. The tool does not validate the bridge contract's security or the oracle's attestation mechanism—these are external dependencies with their own risks.

PLEASE NOTE

EVM chains only. This tool works with any EVM-compatible network (Ethereum, Goerli, Sepolia, BSC, Polygon, Arbitrum, Optimism, etc.) but requires that your wallet supports switching between chains. Bridge mode is experimental and requires you to provide the bridge contract address—the tool does not hardcode any bridge addresses. Always test on testnets first with small amounts. The tool does not store any data; all state is on-chain. Gas costs vary by network, and bridging adds additional fees and latency. For production use, generate Merkle trees off-chain and thoroughly audit the deployed contract.