Raffle Winner Batch Payout Tool (Any L2)

WHAT IT DOES

This tool enables raffle organizers, charity fundraisers, and contest administrators to distribute prizes to raffle winners 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 winner addresses and prize amounts, 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 prize pool 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 raffle prize distributions—covering charity raffles, community fundraisers, promotional giveaways, event raffles, and NFT raffles—but it works for any bulk payment need. Whether you run a small community raffle or a large-scale charity event with hundreds of winners, this tool simplifies prize distribution.

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 winner list as one address and prize amount per line. Click "Parse list" to validate addresses and preview the total prize pool. The review panel shows the number of winners, total prize pool, token address, and the contract fee in native currency. 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 tool handles raffles with multiple prize tiers, making mass payouts practical and efficient for both organizers and winners.

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 prize pool. 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 to handle tokens with different precision correctly, and supports NFT distributions where winners receive unique digital collectibles or exclusive raffle prizes. The batch size is limited only by block gas limits, suitable for raffles with hundreds of winners.

WHAT IT CANNOT SEE

This tool cannot verify off-chain raffle draw randomness, ticket purchase validity, or winner eligibility. It cannot prove that recipient addresses are correct, that winners are legitimate, or that the same person is not receiving multiple prizes via different identities. It cannot detect Sybil attacks or duplicate participant identities. It cannot access private winner payment preferences, raffle rules, or ticketing systems. 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 prize list. It does not store any data; all state is in-memory and lost on reload. It cannot verify that the raffle draw was fair, that the random number generation was unbiased, or that tickets were properly recorded. It cannot enforce ticket purchase requirements, handle refunds for unclaimed prizes, or manage multi-tiered raffle structures beyond what you manually enter. It cannot automatically import winner lists from raffle platforms or calculate prize distributions based on ticket sales. It cannot verify that winners actually purchased tickets, that they didn't use bots or exploits, or that they are eligible based on geographic restrictions or age requirements. It cannot verify that the raffle was compliant with local gambling laws or that proper disclosures were made. It cannot handle situations where a winner declines the prize or where a prize needs to be redrawn.

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, prize amounts, and winner eligibility before signing any transaction. For raffles with significant prize pools, consider using a multi-signature wallet or implementing a community review process before distributing prizes to ensure the raffle was conducted fairly and transparently.