Ethereum L1 ERC-1155 Multi-Edition Batch Sender

WHAT IT DOES

This tool enables you to batch send multiple ERC-1155 editions (different token IDs representing different editions, variants, or collectible types) from your wallet to multiple recipients in a single transaction on Ethereum mainnet. It reads your connected wallet address, the chain ID (must be 1), the ERC-1155 contract address, recipient addresses, edition IDs (token IDs), and quantities to distribute per recipient. You configure the distribution parameters—which editions and quantities go to which recipients—and each execution is a separate batch transaction that you sign and send. The tool uses the shared BotGentz sender contract (0xE0F4E170C434071b167ABA0e64DC3689536f2E07) to perform the batch transfer via sendERC1155Batch, charging a small fee in ETH for each batch. You must setApprovalForAll for the sender contract before the batch can be executed. This is ideal for artists, creators, and projects distributing multiple editions of a collectible, such as different rarities, variants, or series, to a community or set of collectors in one go.

HOW TO USE

Connect your wallet (Ethereum mainnet only), enter the ERC-1155 contract address, and list each transfer as "editionId, recipient, quantity" (one per line). A single recipient can appear on multiple lines to receive different editions. The tool will parse the list and show you the total number of transfers. You must first setApprovalForAll for the sender contract, 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 sendERC1155Batch(address token, address[] calldata recipients, uint256[] calldata tokenIds, uint256[] calldata amounts) on the BotGentz sender contract. The contract iterates through the arrays and transfers the specified quantities of each edition ID 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 that the sender contract has been approved via isApprovedForAll before sending. All transfers are sequential within the contract, ensuring atomicity—if any transfer fails, the entire batch reverts. The tool does not cache fee or approval data; it reads them fresh each time to avoid stale values. This approach efficiently handles multiple editions in a single transaction, saving gas compared to individual transfers.

WHAT IT CANNOT SEE

The tool cannot send native ETH or any token standard other than ERC-1155. It cannot detect token tax or fee-on-transfer dynamics for non-standard tokens; if your edition 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 that the sender actually owns the tokens being distributed—you must ensure you own the editions before sending. It does not automatically execute recurring distributions; each execution is a separate batch transaction that you manually trigger. It does not check if recipients already hold the tokens—this is a push distribution. Gas costs for large batches may be high. 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. You must setApprovalForAll for the sender contract before sending editions. This tool is provided as-is; you are responsible for verifying recipient addresses, edition IDs, quantities, and token ownership.