Base NFT Collection Airdrop-Push Tool

WHAT IT DOES

This tool enables you to push airdrop ERC-721 or ERC-1155 NFTs from your wallet to multiple recipients in a single batch transaction on Base. It reads your connected wallet address, the chain ID (must be 8453), the NFT contract address, the token standard (ERC-721 or ERC-1155), token IDs, and recipient addresses. You configure the airdrop parameters—which NFTs to send to which recipients—and each execution is a separate batch transaction that you sign and send. The tool uses the shared BotGentz sender contract (0x956D760F8665358Ea1a9F11b82913020e5479376) to perform the batch transfer, charging a small fee in ETH for each batch. You must setApprovalForAll for the sender contract before the batch can be executed. For ERC-721, each recipient receives one token ID; for ERC-1155, each recipient receives one token ID with an amount of 1 (configurable in the contract call). On Base, gas costs are significantly lower than Ethereum mainnet, making this tool highly cost-effective for frequent airdrop campaigns.

HOW TO USE

Connect your wallet (Base only), select the NFT standard (ERC-721 or ERC-1155), enter the NFT contract address, list the token IDs (one per line), and list recipient addresses (one per line, in the same order as token IDs). The tool will parse the list, show you the total number of recipients and NFTs, and display the contract fee. You must first setApprovalForAll for the sender contract, then you send the batch. Each batch is a single signed transaction; for recurring airdrops, 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 airdrop is performed by calling either sendERC721Batch(address token, address[] calldata recipients, uint256[] calldata tokenIds) or sendERC1155Batch(address token, address[] calldata recipients, uint256[] calldata tokenIds, uint256[] calldata amounts) on the BotGentz sender contract. 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. For ERC-1155, the amount is set to 1 per recipient, but the tool can be extended to support different amounts.

WHAT IT CANNOT SEE

The tool cannot send native ETH or any token standard other than ERC-721 and ERC-1155. It cannot detect token tax or fee-on-transfer dynamics for non-standard tokens. 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 NFTs being airdropped—you must ensure you own the NFTs before sending. It does not automatically execute recurring airdrops; each execution is a separate transaction that you manually trigger. It does not check if recipients already hold the token—this is a push airdrop, not a claim-based airdrop where recipients opt in. Gas costs for large batches may be high. The tool is limited to Base only.

PLEASE NOTE

This tool works exclusively on Base (chainId 8453). It does not support any other EVM chain. The BotGentz sender contract is hardcoded and verified; you can review its source code on Basescan. Always confirm the fee and contract address before signing any transaction. You must setApprovalForAll for the sender contract before sending NFTs. This tool is provided as-is; you are responsible for verifying recipient addresses, token IDs, and NFT ownership.