USDC Recurring Payroll Batch Sender (Any L2)

WHAT IT DOES

This tool enables you to send USDC (ERC-20) payments to multiple recipients in a single batch transaction across supported L2 networks. It reads your connected wallet address, the chain ID (must be one of the L2 chains in the BULKSEND registry where USDC is deployed), USDC balances and decimals (6), and a list of recipient addresses with amounts. You configure the recurring payroll 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 L2 chain from the BULKSEND registry 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 USDC you intend to send before the batch can be executed.

HOW TO USE

Connect your wallet (supported L2 only), enter the USDC token contract address for that chain, and list recipients with their amounts (one per line). The tool will parse the list, show you the total amount including the contract fee, and display your USDC balance. You first approve the sender contract to spend the total USDC amount, then you send the batch. Each batch is a single signed transaction; for recurring payroll, 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 send is performed by calling sendERC20Batch(address token, address[] calldata recipients, uint256[] calldata amounts) on the BotGentz sender contract for the specific L2 chain. The contract iterates through the arrays and transfers the specified amounts from the caller to each recipient. 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 USDC balance and allowance against the total required (sum of 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 owner data; it reads them fresh each time to avoid stale values that could cause revert. USDC uses 6 decimals, and the tool automatically detects and uses the token's decimals.

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 USDC variant 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). It does not validate payroll parameters (amount, frequency, duration) against token or contract constraints; you must ensure amounts are within your balance and allowance. It does not automatically execute recurring payments; each execution is a separate batch transaction that you manually trigger. The tool assumes the user-provided token address is a standard USDC contract with 6 decimals; it does not validate that the entered address is the canonical USDC bridge for that L2.

PLEASE NOTE

This tool works on any L2 chain in the BULKSEND registry where USDC is deployed: 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 and amounts.