Robinhood Chain (Arbitrum Orbit) Batch Sender

WHAT IT DOES

Robinhood Chain (Arbitrum Orbit) Batch Sender enables you to distribute native ETH or ERC-20 tokens from a single source wallet to multiple recipient addresses in one batch operation. The tool scans the source wallet balance, validates the contract fee, and executes a multi-send transaction through the BotGentz sender contract. It supports both native token transfers and ERC-20 token distributions, with flexible amount specification—you can assign exact amounts per recipient or split the total balance equally. The tool automatically detects the current chain, looks up the correct sender contract from the BULKSEND registry, and reads the live fee and owner from the contract before any transaction is signed. It works on Robinhood Chain (Arbitrum Orbit) and all other EVM chains with registered sender contracts, including Optimism, Base, Arbitrum, Polygon, BNB Chain, and more.

HOW TO USE

Connect your wallet using the built-in wallet bridge. Enter recipient addresses (one per line) with optional amounts in the format address,amount (e.g., 0xaaaa...,0.01). If amounts are omitted, the total balance is split equally among all recipients. Specify the source wallet address and the ERC-20 token contract address to send (use 0x0 for native ETH). Click "preview batch" to retrieve the source balance, compute per-recipient amounts, and verify that the total plus contract fee is covered. The review panel displays the source wallet balance, total to send, fee, contract owner, and a table of recipients with their amounts. Review the summary and click "send batch" to execute the multi-send transaction. The tool processes the batch as a single contract call, ensuring all recipients receive their designated amounts.

TECHNICAL MECHANISM

The batch send uses the BotGentz sender contracts (BULKSEND registry) specific to each chain and token standard. For native ETH sends, it calls multiSendNative with the total value (sum of all amounts plus the contract fee) in a single payable transaction. For token sends, it performs an exact approval for the total token amount before calling multiSendToken. The contract fee is read live on each session using the fee() view function and is never hardcoded—this protects against owner fee adjustments that would otherwise cause revert due to underpayment. The total required amount (sum of all transfers plus fee) is checked against the source wallet balance before the transaction is submitted, preventing partial failures. The batch is executed as a single atomic transaction—either all recipients receive their amounts or the entire transaction reverts, eliminating the risk of partial sends. The tool reads the source balance and token decimals dynamically, and computes amounts with proper decimal precision. All operations use ethers v5.7.2 with BigNumber for accurate arithmetic.

WHAT IT CANNOT SEE

This tool cannot verify off-chain ownership of recipient wallets, private key availability, or authorization to send funds. It cannot prove that recipient addresses are legitimate or that the sender has proper authority to distribute tokens. It cannot recover funds sent to wrong addresses. It cannot detect Sybil attacks or duplicate identities. It cannot access private wallet preferences or security policies. The tool does not validate recipient wallet ownership—you are responsible for ensuring that every recipient address is correct and that you have the authority to send from the source wallet. Funds sent to an incorrect or unreachable address are irrecoverable. The tool does not perform anti-Sybil analysis, identity verification, or KYC checks.

PLEASE NOTE

EVM chains only. Requires a wallet connection with BGWallet bridge. The sender contract must be registered in the BULKSEND registry for the current chain. Always verify the contract address, fee, owner, and recipient list displayed in the review panel before signing any transaction. This is a free tool provided for developer convenience—use at your own risk. For native ETH sends, the fee is deducted from the source wallet balance in addition to the total transfer amount.