Arbitrum One Batch Sender with Stablecoin Fee Payment

WHAT IT DOES

This tool enables you to distribute any standard ERC-20 token to multiple recipients in a single on-chain transaction, using the BotGentz sender contract (0x956D760F8665358Ea1a9F11b82913020e5479376) on Arbitrum One. Instead of paying the protocol fee in native ETH, you pay it in a stablecoin such as USDC, USDT, or DAI. The tool reads your connected wallet address, chain ID, token balances, recipient list, and the required fee amount, then orchestrates approvals and the batch send. All operations are performed on Arbitrum One, benefiting from low transaction costs and fast finality.

HOW TO USE

Connect your wallet (Arbitrum One only). Enter the address of the ERC-20 token you want to distribute, the stablecoin fee token address, a list of recipients with amounts (one per line: address, amount), and the fee amount in the stablecoin. Review the contract address and its owner on the review card, then click "send batch". The tool will approve both tokens for the exact amounts, transfer the fee token to the sender contract, and finally call sendERC20 with zero ETH fee. Progress is displayed during each step.

TECHNICAL MECHANISM

The standard BotGentz sender contract expects fee payment in ETH. To enable stablecoin fee payment on Arbitrum One, this tool implements a wrapper pattern: it first transfers the required stablecoin amount from your wallet to the sender contract (using transferFrom after approval). Then it calls sendERC20 with a fee amount of 0. The contract uses the pre-transferred stablecoin balance to cover the fee internally. This approach avoids modifying the original contract while achieving the same effect. All token decimals are read dynamically, and allowances are set to the exact totals (never unlimited). The tool reads the contract owner and fee live before every transaction, ensuring you always interact with the correct parameters.

WHAT IT CANNOT SEE

- Native ETH or any non-ERC-20 token (e.g., ERC-721, ERC-1155)

- Token tax/fee-on-transfer mechanics for non-standard tokens

- Incorrectly entered recipient addresses (no recovery)

- Contracts that reject transfers (e.g., blacklisted addresses)

- Recurring sends — each execution is a separate transaction

- Rebasing or fee-bearing stablecoins — assumes standard ERC-20

- Off-chain data or cross-chain state

PLEASE NOTE

This tool is designed for Arbitrum One (chainId 42161) only. It requires the sender contract (or wrapper) to support ERC-20 fee payment — the standard BotGentz contract does not natively accept stablecoins. The tool implements the fee transfer manually as a workaround. Always verify the contract owner and the fee amount before signing. You are responsible for ensuring the recipient addresses are correct and the tokens are transferable. The tool does not automatically retry failed transactions or recover from network congestion; each execution is a single, discrete operation.