Ethereum L1 ERC-721 Batch Sender

WHAT IT DOES

This tool enables you to send multiple ERC-721 NFTs (non-fungible tokens) to many recipients in a single batch transaction on Ethereum L1. Instead of transferring each NFT individually, you provide a list of recipient addresses and corresponding token IDs, and the tool packages them into one multisend call using the BotGentz sender contracts. It handles setting the necessary operator approval for the sender contract, computes the dynamic fee charged by the contract, checks your ETH balance to cover the fee, and executes the batch transfer. Batching multiple NFT transfers saves significant gas compared to processing each transfer separately and ensures all NFTs are sent in one atomic operation.

HOW TO USE

Connect your EVM wallet using the BGWallet bridge. Select the network (Ethereum L1 is the default, but other supported chains are available). Paste the ERC-721 NFT contract address into the provided field — this is the NFT collection you want to send from, not the batch contract. Then enter your recipients, one per line, in the format `0xAddress,tokenId` (e.g., `0x123...,123`). Click Validate to parse and check the addresses and token IDs. The tool will display the total number of NFTs, the current fee charged by the sender contract (in ETH), and your wallet balance. If you have sufficient funds to cover the fee, click "Send batch" to set approval for the sender contract and execute the batch transfer.

ONE TECHNICAL SECTION

The tool uses the BotGentz multisend registry, which contains known sender contract addresses per chain and standard (ERC20, ERC721, ERC1155). For ERC-721, it uses the `erc721` entry from the registry. It reads the fee live from the contract's `fee()` function — never hardcoded — and also fetches the contract owner for transparency. The tool uses `setApprovalForAll` to grant the sender contract operator permission for all NFTs in the collection, which is required for the batch send. The batch send is executed as a single transaction using the contract's `batchSendERC721` method, which takes the NFT contract address, an array of recipient addresses, and an array of token IDs. The tool checks the ETH balance before sending to ensure the fee can be paid. It uses `receipt.effectiveGasPrice` to accurately reflect post-EIP-1559 gas costs.

WHAT IT CANNOT SEE

This tool cannot verify that the recipient addresses are correct or owned by the intended parties. It cannot predict future gas price fluctuations or network congestion, so the final cost may vary from the estimated gas. It does not validate the authenticity, metadata, or ownership of the NFTs you are sending — you must ensure you own the token IDs you are transferring. The tool does not check if a token has been burned, frozen, or has any transfer restrictions. It cannot detect if the NFT contract uses a non-standard implementation that deviates from ERC-721. It cannot recover failed sends or reverse transactions once broadcast. It does not track royalty payments or creator fees that may be applied on transfer.

PLEASE NOTE

This tool is for EVM-compatible chains only. It does not support non-EVM chains like Solana, Tron, or Bitcoin. Always double-check the NFT contract address for your selected network. The batch sender contract charges a fee which is read live and displayed before you sign. Ensure you trust the contract — its address is shown in the review section. This tool requires you to set `setApprovalForAll` for the batch contract, which grants it permission to transfer all your NFTs from that collection; only use this with trusted contracts. The fee is paid in the native currency of the chain (ETH on Ethereum L1).