zkSync Era ERC-1155 Batch Sender

WHAT IT DOES

This tool allows you to batch transfer multiple ERC-1155 token types and quantities on the zkSync Era network to different recipients in a single transaction. Unlike ERC-721 which sends one NFT per token ID, ERC-1155 supports both fungible and non-fungible tokens within the same contract, with each token ID representing a distinct asset type that can have a balance. This tool handles the complexity of sending multiple token IDs with varying quantities to multiple recipients, bundling everything into one operation to save gas and time. It verifies balances for each token ID and quantity before sending, and manages the approval flow automatically. You provide the ERC-1155 contract address, a list of transfers (tokenId, recipient, amount), and the tool handles the rest.

HOW TO USE

Connect your EVM wallet and ensure you are on the zkSync Era network (chainId 324). Enter the address of the ERC-1155 contract, then provide a list of transfers formatted as tokenId, recipientAddress, amount (one per line). Click "Preview batch" to see the token IDs being sent, total units, balance sufficiency checks, and approval status. The tool checks your balance for each token ID using balanceOf() and reports any insufficient balances. Once confirmed, click "Send batch" to approve the contract (if needed) and execute all transfers. The transaction status and a zkSync Era explorer link are displayed after completion. For contracts with multiple token IDs, each transfer is processed using safeTransferFrom() with the specified amount.

TECHNICAL MECHANISM

This tool uses the shared BotGentz sender contract from the BULKSEND registry, looking up the zkSync Era (chainId 324) erc1155 contract address. It reads the fee from the contract live each time using the fee() method to avoid underpayment. The tool verifies each balance using balanceOf(address, tokenId) before sending, ensuring you have sufficient quantity for every token ID. Approval is handled via setApprovalForAll() to grant the sender contract permission to transfer all token types, and is only requested if not already approved. For the actual transfers, the tool uses safeTransferFrom() from the ERC-1155 standard, which includes a safety check to ensure the recipient can receive ERC-1155 tokens. Each token ID is processed individually, with the amount specified for each recipient. Gas costs are reported using effectiveGasPrice from the transaction receipt.

WHAT IT CANNOT SEE

This tool cannot verify that the recipient addresses you provide are valid wallets capable of receiving and holding ERC-1155 tokens. Some recipient addresses may be smart contracts that do not implement the ERC-1155 receiver interface and could reject or mishandle the transfer. It cannot simulate off-chain recipient willingness to receive or guarantee delivery if a recipient contract is malicious or poorly coded. It cannot verify the authenticity or provenance of the tokens beyond checking balances. It cannot verify that the contract actually implements the ERC-1155 standard correctly — you are responsible for ensuring the contract address and token IDs are correct. It does not account for zkSync Era-specific gas fee structures beyond the submitted transaction. It cannot protect you from accidentally sending tokens to the wrong address or from sending quantities that exceed your balance.

PLEASE NOTE

This tool works exclusively on EVM-compatible chains, specifically zkSync Era (chainId 324). It requires an EVM wallet bridge (injected via BGWallet) and will not function on non-EVM networks like Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, or XRP. Always double-check the contract address, token IDs, recipient addresses, and quantities before sending, as irreversible transactions on the blockchain cannot be undone. The fee is charged in the native token (ETH on zkSync Era) and is separate from the token amounts being sent. Gas costs are also paid in ETH from your wallet balance on top of the fee.