Base Approve-and-Batch-Send Combo Tool

WHAT IT DOES

This tool combines two essential steps for batch sending ERC-20 tokens on Base: approving the BotGentz sender contract and executing the batch send. It reads your connected wallet address, the chain ID (must be 8453), ERC-20 token balances and decimals, recipient addresses, and the current allowance for the sender contract. The tool guides you through a two-step process: first, you approve the sender contract (0x956D760F8665358Ea1a9F11b82913020e5479376) to spend the exact total amount of tokens; second, you send the batch transaction to distribute the tokens to all recipients. Both transactions are coordinated by the tool but remain separate on-chain transactions. You configure the recurring distribution parameters—amount per recipient, frequency, and duration—and each execution is a separate sequence of transactions that you sign and send. On Base, gas costs are significantly lower than Ethereum mainnet, making this tool highly cost-effective for frequent distribution runs.

HOW TO USE

Connect your wallet (Base only), enter the ERC-20 token contract address, and list recipients with their amounts (one per line). The tool will parse the list, show you the total amount including the contract fee, display your token balance, and show your current allowance for the sender contract. You first click "approve" to grant the sender contract permission to spend the total token amount. After the approval transaction is confirmed, you click "send batch" to execute the batch transfer. Each step is a separate transaction that you must sign with your wallet. The tool does not automatically proceed after approval—you must verify that the approval succeeded before sending.

TECHNICAL MECHANISM

The approval step calls the standard ERC-20 approve(address spender, uint256 amount) function on the token contract, granting the BotGentz sender contract permission to spend the exact total amount of tokens. The batch send step calls sendERC20Batch(address token, address[] calldata recipients, uint256[] calldata amounts) on the sender contract. The fee is read live from the contract's fee() function and must be paid in ETH as part of the batch send transaction value. The tool checks your token balance and the current allowance against the total required before each step. If the allowance is already sufficient, the approval step can be skipped. All transfers are sequential within the contract, ensuring atomicity—if any transfer fails, the entire batch reverts. The tool does not cache fee, balance, or allowance data; it reads them fresh each time to avoid stale values.

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 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). The approve and batch-send are separate transactions—the tool coordinates them but does not execute them atomically; you must wait for the approval confirmation before sending. The tool does not handle tokens that require non-standard approval patterns (e.g., USDT requires resetting approval to 0 before setting a new amount). It does not automatically execute recurring sends; each execution is a separate sequence of transactions that you manually trigger. The tool is limited to Base only.

PLEASE NOTE

This tool works exclusively on Base (chainId 8453). It does not support any other EVM chain. The BotGentz sender contract is hardcoded and verified; you can review its source code on Basescan. Always confirm the fee, contract address, and allowance before signing any transaction. For tokens that require approval resets (e.g., USDT), you may need to manually set approval to 0 first. This tool is provided as-is; you are responsible for verifying recipient addresses and amounts.