NFT-Gated Conditional Batch Sender (Ethereum L1)

WHAT IT DOES

This tool enables you to send ERC-20 tokens to multiple recipients in a single batch transaction, but only to those who satisfy an NFT-gating condition on Ethereum mainnet. It reads your connected wallet address, the chain ID (must be 1), ERC-20 token balances and decimals, NFT ownership status for specified ERC-721 or ERC-1155 tokens and token IDs, recipient addresses, and amounts. The tool checks each recipient's ownership of the specified NFT at execution time and includes only eligible recipients in the batch. You configure the recurring distribution parameters—amount per recipient, frequency, and duration—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, charging a small fee in ETH for each batch. You must approve the sender contract for the exact total amount of tokens intended for eligible recipients before the batch can be executed.

HOW TO USE

Connect your wallet (Ethereum mainnet only), enter the ERC-20 token contract address, specify the NFT gating condition (format: "erc721, contract_address, tokenId" or "erc1155, contract_address, tokenId"), and list recipients with their amounts (one per line). The tool will parse the list, check each recipient's NFT ownership, show you the eligible count, total amount including the contract fee, and display your token balance. You first approve the sender contract to spend the total token amount for eligible recipients, 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 sendERC20Batch(address token, address[] calldata recipients, uint256[] calldata amounts) on the BotGentz sender contract. Before constructing the batch, the tool queries the NFT contract for each recipient using either ownerOf(uint256) for ERC-721 or balanceOf(address, uint256) for ERC-1155. Only recipients with a positive ownership check are included in the final batch arrays. 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 your token balance and allowance against the total required (sum of eligible amounts plus fee) before signing, preventing partial failures. All transfers are sequential within the contract, ensuring atomicity—if any transfer fails, the entire batch reverts. The tool does not cache NFT ownership or fee data; it reads them fresh each time to avoid stale values.

WHAT IT CANNOT SEE

The tool cannot send native ETH or any token standard other than ERC-20. It cannot detect token tax or fee-on-transfer dynamics for non-standard tokens; if your token deducts a fee on each transfer, the amount received by eligible 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 NFTs are not soulbound or transfer-restricted—ownership checks assume standard ERC-721 or ERC-1155 behavior. Conditional checks are performed at execution time only and do not track historical ownership; recipients must hold the NFT at the moment of sending. NFT ownership is checked for each recipient individually, which may increase gas costs. It does not automatically execute recurring distributions; each execution is a separate batch transaction that you manually trigger. 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. This tool is provided as-is; you are responsible for verifying recipient addresses, amounts, and the NFT gating condition.