Whitelist-Gated Conditional Batch Sender (Any L2)

WHAT IT DOES

This tool enables you to send ERC-20 tokens to multiple recipients in a single batch transaction, but only to those who appear on a user-provided whitelist. It reads your connected wallet address, chain ID (must be one of the chains in the BULKSEND registry), ERC-20 token balances and decimals, recipient addresses, and a whitelist of addresses that are allowed to receive. The tool checks each recipient against the whitelist at execution time and includes only whitelisted recipients in the batch. You configure the recurring distribution parameters—amount per recipient, frequency, and duration—and each execution is a separate batch transaction that you sign and send. The tool uses the shared BotGentz sender contract for the detected chain to perform the batch transfer, charging a small fee in ETH for each batch. You must approve the sender contract for the exact total amount of tokens intended for eligible recipients before the batch can be executed.

HOW TO USE

Connect your wallet (supported L2 only), enter the ERC-20 token contract address, paste your whitelist (one address per line) into the whitelist area, and list recipients with their amounts (one per line). The tool will parse the list, check each recipient against the whitelist, show you the eligible count, total amount including the contract fee, and display your token balance. You first approve the sender contract to spend the total token amount for eligible recipients, then you send the batch. Each batch is a single signed transaction; for recurring distributions, you repeat the process on your chosen schedule. The tool does not automate scheduling—you decide when to execute each batch.

TECHNICAL MECHANISM

The batch distribution is performed by calling sendERC20Batch(address token, address[] calldata recipients, uint256[] calldata amounts) on the BotGentz sender contract. Before constructing the batch, the tool builds a case-insensitive set of whitelist addresses and checks each recipient address against it. Only recipients whose addresses match an entry in the whitelist are included in the final batch arrays. The fee is read live from the contract's fee() function and must be paid in ETH as part of the transaction value. The tool checks your token balance and allowance against the total required (sum of eligible amounts plus fee) before signing, preventing partial failures. All transfers are sequential within the contract, ensuring atomicity—if any transfer fails, the entire batch reverts. The tool does not cache fee or whitelist data; it reads them fresh each time to avoid stale values. The whitelist is maintained entirely locally—it is not stored on-chain and is not validated against any external source.

WHAT IT CANNOT SEE

The tool cannot send native ETH or any token standard other than ERC-20. It cannot detect token tax or fee-on-transfer dynamics for non-standard tokens; if your token deducts a fee on each transfer, the amount received by eligible recipients will be less than specified. It cannot recover incorrectly entered recipient addresses—invalid addresses are simply skipped. It cannot send to contracts that reject transfers (e.g., blacklisted addresses). Whitelist validation is performed locally by matching addresses—the tool does not verify that the whitelist itself is valid or authenticated. Whitelist entries must exactly match addresses (case-insensitive but address format matters); the tool does not support wildcards or pattern matching. It does not automatically execute recurring distributions; each execution is a separate batch transaction that you manually trigger. Whitelist data is not stored on-chain and must be provided each time you run the tool. The tool is limited to supported L2 chains only.

PLEASE NOTE

This tool works on any chain in the BULKSEND registry: Arbitrum, Base, Optimism, Polygon, and others. It does not support Ethereum mainnet or other non-registered chains. The BotGentz sender contract is hardcoded and verified per chain; you can review its source code on the respective block explorer. Always confirm the fee and contract address before signing any transaction. This tool is provided as-is; you are responsible for verifying recipient addresses, amounts, and the whitelist contents.