Ethereum L1 Mixed-Standard Batch Sender

WHAT IT DOES

This tool enables you to send a mix of ERC-20 tokens, ERC-721 NFTs, and ERC-1155 NFTs to multiple recipients in a single signed transaction on Ethereum mainnet. It reads your connected wallet address, the chain ID (must be 1), balances and token IDs for each standard, recipient addresses, and the token standard selection per transfer. You configure the transfers—each entry specifies the standard (erc20, erc721, or erc1155), the token contract address, the recipient, and the amount or token ID. The tool groups transfers by standard and calls the appropriate batch function on the BotGentz sender contract (sendERC20Batch, sendERC721Batch, or sendERC1155Batch) for each group, all within one transaction. You must approve the sender contract for the total ERC-20 amount (if any) before execution.

HOW TO USE

Connect your wallet (Ethereum mainnet only), and enter each transfer on a new line with the format: standard, token_address, recipient, [id/amount]. For ERC-20: use "erc20, 0x..., 0x..., amount". For ERC-721: use "erc721, 0x..., 0x..., tokenId". For ERC-1155: use "erc1155, 0x..., 0x..., tokenId, amount". The tool will parse the list, group transfers by standard, and show you the total number of transfers. If ERC-20 transfers are included, you must approve the sender contract for the total amount before sending. Each execution is a single signed transaction; for recurring sends, you repeat the process manually. The tool does not automate scheduling—you decide when to execute each batch.

TECHNICAL MECHANISM

The tool parses the input, groups transfers by token standard, and for each group constructs the appropriate batch arrays. It then sequentially calls sendERC20Batch, sendERC721Batch, and sendERC1155Batch on the BotGentz sender contract (0xE0F4E170C434071b167ABA0e64DC3689536f2E07), all within the same transaction. The fee is read live from the contract's fee() function and paid once in ETH for the entire transaction. The tool checks ERC-20 allowance against the total ERC-20 amount before sending, preventing partial failures. Each batch call is atomic for its standard—if any transfer within a batch fails, that entire batch reverts. The tool does not cache fee or owner data; it reads them fresh each time to avoid stale values. This approach allows you to send multiple standards in one transaction without needing to sign separate transactions for each standard.

WHAT IT CANNOT SEE

The tool cannot send native ETH or any token standard other than ERC-20, ERC-721, and ERC-1155. It cannot detect token tax or fee-on-transfer dynamics for non-standard tokens; if your token deducts a fee on transfer, the amount received 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). Each transfer type must be submitted as a separate batch call within the transaction; the tool cannot mix different token standards in a single batch call. The tool does not validate that the user has ownership or approval for the NFTs being sent—you must ensure you own the NFTs and have approved the sender contract if required (for ERC-721 and ERC-1155, the sender contract must be approved to transfer on your behalf via setApprovalForAll). It does not automatically execute recurring sends—each execution is a separate transaction that you manually trigger. The tool is limited to Ethereum mainnet only.

PLEASE NOTE

This tool works exclusively on Ethereum mainnet (chainId 1). It does not support any other EVM chain. The BotGentz sender contract is hardcoded and verified; you can review its source code on Etherscan. Always confirm the fee and contract address before signing any transaction. For ERC-721 and ERC-1155 transfers, you must have setApprovalForAll for the sender contract. This tool is provided as-is; you are responsible for verifying recipient addresses, amounts, and token IDs.