Merkle Distributor Deployer

WHAT IT DOES

Merkle Distributor Deployer gives developers and project teams a streamlined way to deploy Merkle-based token distributor contracts using a factory pattern. It reads factory contract state, deployed distributor addresses, token configuration, deployment parameters, and chain state for gas estimation. You can deploy new distributor contracts with fully customizable parameters including token address, Merkle root (representing the list of eligible recipients and their allocations), expiry timestamp, and owner address. The tool estimates gas costs before deployment, shows you the deployed contract address after confirmation, and provides transaction explorer links. Instead of manually writing and deploying distributor contracts for each airdrop, you use a factory that handles the deployment logic, reducing errors and saving time.

HOW TO USE

Connect your EVM wallet. Enter the Merkle distributor factory contract address and token address you want to use. Provide the Merkle root (hex string) that represents your list of eligible recipients and their claim amounts. Optionally set an expiry timestamp (Unix seconds) after which claims are disabled, and an owner address (defaults to your wallet). Use "Estimate gas" to see the expected gas cost before committing. Click "Deploy distributor" to deploy a new distributor contract—this requires the factory to have sufficient allowance for the token amount to be distributed. After confirmation, the tool displays the deployed contract address and links to the explorer. The generated distributor supports claiming via Merkle proofs, setting expiry, and withdrawing remaining tokens.

TECHNICAL APPROACH

This tool uses a factory contract pattern to deploy Merkle distributor contracts, avoiding the need to write and deploy each contract individually. It calls deployDistributor() on the factory with all parameters—token address, Merkle root (bytes32), expiry (uint256), and owner address—which deploys a new distributor instance via CREATE2 or standard deployment. The tool queries the factory's state using ethers v5.7.2, reads deployed distributor addresses from events, and estimates gas using estimateGas.deployDistributor() to provide cost transparency before transaction submission. All RPC calls are wrapped in a robust error handler that extracts the actual failure reason from Ethers error objects, digging three levels deep to avoid showing "[object Object]" when a transaction reverts. For transaction costing, it uses receipt.effectiveGasPrice post-EIP-1559 rather than tx.gasPrice, which overstates actual spend. The tool also checks token allowance before deployment, providing clear error messages for insufficient approvals, and displays the deployed address by parsing the DistributorDeployed event from the transaction logs.

WHAT IT CANNOT SEE

This tool cannot verify the security or correctness of the deployed distributor contract code, nor guarantee that the Merkle root or proofs will be valid. It cannot audit the factory implementation or ensure that the distributor contract follows best practices. It cannot detect whether the factory contract has been tampered with or deployed with malicious intent. It cannot generate Merkle proofs—proofs must be generated off-chain and provided to recipients separately. The tool deploys contracts based on the factory's implementation, but it does not guarantee that the factory is secure or that the deployed contracts will behave as intended. Users must verify the factory contract code, audit reports, and the correctness of the Merkle root independently.

PLEASE NOTE

This tool supports EVM‑compatible chains only (Ethereum, Goerli, Sepolia, Arbitrum, Optimism, Polygon). Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, and XRP are not supported. This is a read‑write tool that requires signing transactions—always verify the factory contract address, token address, Merkle root, and expiry before approving. No contract addresses are hardcoded; you paste the factory contract you are using, so you are responsible for verifying its safety and ensuring it implements the expected distributor deployment interface. The tool is free and open under the BotGentz PLAYBOOK‑C specification.