Arbitrum One rETH Batch Sender

WHAT IT DOES

This tool enables you to send rETH (ERC-20) payments to multiple recipients in a single batch transaction on Arbitrum One. It reads your connected wallet address, the chain ID (must be 42161), rETH token balances and decimals (18), and a list of recipient addresses with amounts. You configure the recurring payroll 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 (0x956d760f8665358ea1a9f11b82913020e5479376) 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 rETH you intend to send before the batch can be executed. rETH is Rocket Pool's liquid staking token with 18 decimals, and this tool handles the token's decimals automatically. On Arbitrum One, gas costs are significantly lower than Ethereum mainnet, making this tool highly cost-effective for frequent payroll runs.

HOW TO USE

Connect your wallet (Arbitrum One only), enter the rETH token contract address (the canonical address on Arbitrum is 0xEC70Dcb4A1EFa46b8F2D97C310C9c4790ba5ffA8, but you can enter any rETH-compatible ERC-20 address), and list recipients with their amounts (one per line). The tool will parse the list, show you the total amount including the contract fee, and display your rETH balance. You first approve the sender contract to spend the total rETH amount, then you send the batch. Each batch is a single signed transaction; for recurring payroll, 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 send is performed by calling sendERC20Batch(address token, address[] calldata recipients, uint256[] calldata amounts) on the BotGentz sender contract. The contract iterates through the arrays and transfers the specified amounts from the caller 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 your rETH balance and allowance against the total required (sum of 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 fee or owner data; it reads them fresh each time to avoid stale values that could cause revert. rETH uses 18 decimals, and the tool automatically detects and uses the token's decimals via the standard ERC-20 decimals() function. rETH is a rebasing token wrapper that represents a claim on staked ETH, and its value relative to ETH changes over time as staking rewards accumulate, but the tool transfers only the specified amount of rETH tokens.

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 rETH variant deducts a fee on each transfer, the amount received by 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 payroll parameters (amount, frequency, duration) against token or contract constraints; you must ensure amounts are within your balance and allowance. It does not automatically execute recurring payments; each execution is a separate batch transaction that you manually trigger. The tool assumes the user-provided token address is a standard rETH contract; it does not validate that the entered address is the canonical rETH token on Arbitrum. rETH is a rebasing token wrapper and its value relative to ETH changes over time, but the tool transfers only the specified amount of rETH tokens—it does not account for or simulate rebasing effects. The tool is limited to Arbitrum One only.

PLEASE NOTE

This tool works exclusively on Arbitrum One (chainId 42161). It does not support any other EVM chain. The BotGentz sender contract is hardcoded and verified; you can review its source code on Arbiscan. Always confirm the fee and contract address before signing any transaction. This tool is provided as-is; you are responsible for verifying recipient addresses and amounts.