Documentation Contributor Payout Batch Sender (Any L2)

WHAT IT DOES

This tool enables project maintainers to pay documentation contributors 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 contributor addresses and 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 payout 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.

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 recipient list as one address and amount per line. Click "Parse list" to validate addresses and preview the total. The review panel shows the number of recipients, total amount, 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.

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 token amount. 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.

WHAT IT CANNOT SEE

This tool cannot verify off-chain contribution work quality or validate that documentation submissions are genuine. It cannot prove that recipient addresses are correct, that contributions were legitimate, or that the same person is not receiving multiple payments via different identities. It cannot detect Sybil attacks or duplicate contributor identities. It cannot access private contributor payment preferences or off-chain agreements. 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 payout list. It does not store any data; all state is in-memory and lost on reload.

PLEASE NOTE

This tool works only on EVM-compatible chains 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.