Base ERC-721 Batch Sender

WHAT IT DOES

This tool enables the batch distribution of multiple ERC-721 NFTs (non-fungible tokens) to different recipient addresses in a single atomic transaction on Base (Coinbase's Layer 2 network). It connects to your wallet via BGWallet, reads the NFT contract bytecode and verified source, fetches your current NFT ownership and approval status, and constructs a batched transfer that sends each NFT to its designated recipient. The batch executes through the BotGentz sender contract, ensuring all NFTs are transferred successfully or the entire transaction reverts. This is ideal for NFT airdrops, collection distribution, bulk gifting, marketplace settlements, or any scenario requiring efficient multi-recipient NFT transfers on Base's low-cost, high-speed OP Stack L2.

HOW TO USE

1. Connect your wallet using the "Connect" button (BGWallet integration).

2. Ensure you are on Base (chain ID 8453) — the tool will prompt you to switch if needed.

3. Enter the NFT contract address (any ERC-721 collection on Base).

4. Click "Load NFT details" to automatically detect the collection's name and symbol.

5. Paste your transfer list — one NFT per line with recipient address and token ID, separated by space or comma.

6. Click "Parse & preview" to validate addresses and token IDs, and see a summary table.

7. Review the sender information: your address, NFT count, approval status, batch sender contract details, and fee.

8. If not approved, click "Set approval" to authorize the sender contract to transfer your NFTs on your behalf.

9. Click "Send batch" to execute the atomic transfer. The progress bar will show transaction status.

TECHNICAL MECHANISM

The tool leverages the BotGentz multisender contract (BULKSEND registry) which implements a batched ERC-721 transfer function. It dynamically fetches the current fee and owner address from the contract (never hardcoding stale values). Unlike ERC-20 batch sends, ERC-721 transfers require per-token ownership verification — the tool checks that you own each NFT before attempting the batch transfer, preventing partial failures. The contract uses the `sendERC721` method, which takes arrays of recipient addresses and token IDs, processes each transfer via `safeTransferFrom`, and ensures all succeed before finalizing. The transaction includes the protocol fee as `msg.value`. The tool reads the NFT contract's name and symbol for clear identification, and checks `isApprovedForAll` to verify operator approval for the sender contract. If not approved, it guides you through the `setApprovalForAll` process. Base L2 gas mechanics are handled through the provider, with the tool estimating gas using the contract's `estimateGas` function and applying a 20% safety margin. Base's OP Stack architecture ensures fast finality and low transaction costs.

WHAT IT CANNOT SEE

This tool cannot guarantee recipient addresses are valid beyond basic Ethereum address format validation (0x + 40 hex characters). It does not verify if recipients are contracts that can receive NFTs, if they support the ERC-721 standard, or if they have specific receiving functions that could revert. The tool cannot recover from a failed batch — due to the atomic nature of the transaction, if any single NFT transfer fails (e.g., recipient contract rejects the NFT, token ID not owned, approval issues), the entire batch reverts and no NFTs are transferred. It cannot send to zero addresses or self, or exceed the block gas limit (which limits batch size). The tool does not simulate the transaction beforehand, so unexpected reverts may occur during execution. It relies entirely on the NFT contract behaving as expected — any changes to the contract's logic (e.g., upgrades, pausing, transfer restrictions) could cause the batch to fail. The tool cannot detect if an NFT has royalties or transfer fees that might affect the transaction, nor can it detect if the NFT is locked, staked, or has other transfer restrictions. Base-specific considerations include sequencer dependencies and varying gas prices that may affect transaction propagation, as well as the OP Stack's unique fee structure.

PLEASE NOTE

This tool is designed exclusively for Base (chain ID 8453). It reads the chain ID and uses the BULKSEND registry to locate the appropriate sender contract (the registry includes Base at 0x956D760F8665358Ea1a9F11b82913020e5479376). The sender contract charges a fee in ETH (native gas token on Base), which is displayed before signing. Always review the fee, contract address, and owner before approving or sending. This tool is provided as-is — verify all transactions carefully, especially when dealing with valuable NFTs that have complex transfer logic. Transactions on Base may have different confirmation times and gas costs compared to Ethereum L1, and may be subject to sequencer-related delays inherent to the OP Stack architecture.