Kickstarter-Style Reward Tier Batch Distributor (Any L2)

WHAT IT DOES

This tool enables crowdfunding campaign creators to distribute tiered rewards to backers in a single batched transaction across any EVM-compatible L2. Instead of sending 50 individual transactions and paying gas 50 times, you paste a list of backer addresses and reward amounts, optionally with tier labels, and the BotGentz bulk-sender contract distributes everything in one go. It supports ERC-20 tokens, ERC-721 NFTs, and ERC-1155 multi-tokens, plus native currency (ETH, BNB, MATIC, etc.) through the same interface. The tool reads on-chain balances, verifies that your wallet holds enough of each asset to cover the total rewards plus the contract's fee, and checks your transaction history to flag duplicates. It displays the contract's live fee, owner, and address before you sign anything so you know exactly what you are approving. This is designed specifically for Kickstarter-style crowdfunding campaigns where backers receive different rewards based on their contribution level—from early-bird specials to exclusive collector's editions—but it works for any bulk payment need with tiered structures.

HOW TO USE

Connect your EVM wallet via the BotGentz bridge. The tool automatically detects the current chain and looks up the correct bulk-sender contract from the BotGentz registry. Enter the token contract address, choose the token type (ERC-20, ERC-721, or ERC-1155), and paste your backer list as one address, reward amount, and optional tier label per line. Click "Parse list" to validate addresses and preview the total rewards. The review panel shows the number of backers, total rewards, token address, contract fee, and a breakdown of backers by tier. When you click "Send batch," the tool performs a balance check per sender, not per row, ensuring the entire batch can complete before the first transfer. It then approves the sender contract for the exact total amount, not unlimited, and sends the batched transaction. Progress is shown throughout, including transaction confirmation. All state is in-memory and lost on reload—no data is stored. The tier labels help you organize and verify distributions without affecting the on-chain transaction.

BULK SENDER CONTRACT MECHANISM

Unlike claim-based airdrops where each recipient pays their own gas to withdraw, this is a true bulk-send tool: the sender pays once for the entire batch. The BotGentz registry provides per-chain, per-standard contract addresses. The tool reads the fee() and owner() methods live from the contract each time—never hardcoding fees because the owner can change them. It uses the contract's sendERC20, sendERC721, and sendERC1155 methods, passing the recipient arrays, amounts or token IDs, and the required fee as msg.value. The fee covers the contract's operational costs and is separate from network gas. The tool checks balances comprehensively: native balance must cover the fee, and ERC-20 balance must cover the total rewards. It walks through approvals sequentially and awaits each transaction, avoiding nonce conflicts that would occur if sends were fired concurrently. Post-EIP-1559, it uses receipt.effectiveGasPrice for accurate cost reporting rather than tx.gasPrice. For chains with different log limits, it chunks reads appropriately, halving ranges on failure. The contract owner is shown so you can verify the deployer before signing. The tool also reads token decimals dynamically and supports tiered distributions where different backers receive different token amounts or different NFT token IDs based on their contribution level. The tier labels are stored locally for your reference and do not affect the on-chain transaction, allowing you to organize backers by pledge amount, reward type, or fulfillment priority.

WHAT IT CANNOT SEE

This tool cannot verify off-chain backer contribution levels, reward tier qualification, or campaign eligibility. It cannot prove that recipient addresses are correct, that backers are legitimate, or that the same person is not receiving multiple rewards via different identities. It cannot detect Sybil attacks or duplicate backer identities. It cannot access private backer payment preferences, campaign rules, or contribution history. It cannot recover funds sent to wrong addresses—the blockchain is final. It cannot see past the current block, and it cannot enforce business rules beyond what is expressed in the reward list. It does not store any data; all state is in-memory and lost on reload. It cannot verify that backers actually contributed the required amounts, that they qualified for specific reward tiers, or that they are eligible based on geographic restrictions. It cannot enforce campaign deadlines, handle refunds for unsuccessful campaigns, or manage multi-phase reward distributions beyond what you manually enter. It cannot automatically import backer lists from crowdfunding platforms or calculate rewards based on contribution levels. It cannot verify that rewards are being distributed to the correct addresses or that backers didn't use multiple wallets to exceed contribution limits. It cannot handle situations where a backer changes their address or where rewards need to be adjusted after distribution. It cannot verify that the campaign reached its funding goal or that the project is legitimate.

PLEASE NOTE

This tool works on any EVM-compatible chain with BotGentz bulk-sender contracts deployed: Ethereum mainnet, Optimism, Cronos, BNB Chain, Polygon, Fantom, zkSync Era, Base, Arbitrum, Avalanche C-chain, and Linea. Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, and XRP are not supported. Always double-check the contract address displayed in the tool against the official BotGentz registry before sending. The tool is free and open-source; the contract fee is set by the owner and displayed live. Use at your own risk—you are responsible for verifying all addresses, reward amounts, and backer eligibility before signing any transaction. For campaigns with significant reward pools, consider using a multi-signature wallet or implementing a community review process before distributing rewards to ensure the campaign was successful and backers received what they were promised.