Base Friend.tech Key Batch Distributor

WHAT IT DOES

This tool enables you to distribute Friend.tech keys (ERC-1155 tokens) to multiple recipients in a single batch transaction on Base. It reads your connected wallet address, the chain ID (must be 8453), the Friend.tech key contract address, subject addresses (which become token IDs), recipient addresses, and the number of keys to send per recipient. You configure the recurring distribution parameters—keys 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 (0x956D760F8665358Ea1a9F11b82913020e5479376) to perform the batch transfer via sendERC1155Batch, charging a small fee in ETH for each batch. You must setApprovalForAll for the sender contract before the batch can be executed. On Base, gas costs are significantly lower than Ethereum mainnet, making this tool highly cost-effective for frequent distribution runs.

HOW TO USE

Connect your wallet (Base only), enter the Friend.tech key contract address (the canonical address is 0xCF205808Ed36593aa40a44F10c7f7C2F67d4A4d4, but you can enter any compatible ERC-1155 contract), and list each distribution as "subject_address, recipient_address, amount" (one per line). The subject address is the Friend.tech user whose keys you are distributing; it becomes the token ID in the ERC-1155 contract. The tool will parse the list and show you the total number of keys to distribute. You must first setApprovalForAll for the sender contract, 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 sendERC1155Batch(address token, address[] calldata recipients, uint256[] calldata tokenIds, uint256[] calldata amounts) on the BotGentz sender contract. The contract iterates through the arrays and transfers the specified amounts of each token ID to each recipient. 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 owner data; it reads them fresh each time to avoid stale values that could cause revert. Friend.tech keys are ERC-1155 tokens where the token ID represents the subject address, and the tool accepts subject addresses as input and converts them to token IDs automatically.

WHAT IT CANNOT SEE

The tool cannot send native ETH or any token standard other than ERC-1155. It cannot recover incorrectly entered recipient or subject addresses—invalid addresses are simply skipped. It cannot send to contracts that reject transfers (e.g., blacklisted addresses). It does not validate distribution parameters (amount, frequency, duration) against token or contract constraints; you must ensure you own the keys you are distributing. It does not automatically execute recurring distributions; each execution is a separate batch transaction that you manually trigger. The tool assumes the user-provided token address is the Friend.tech key contract; it does not validate that the entered address is the canonical Friend.tech contract. Keys are ERC-1155 tokens where the token ID represents the subject address, and the tool does not validate that the subject address is valid or that the user owns the keys being sent—you must ensure you own the keys and have approved the sender contract. 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 keys. This tool is provided as-is; you are responsible for verifying subject addresses, recipient addresses, and key amounts.