Arbitrum Orbit L3 Batch Sender (Any Orbit Chain)

WHAT IT DOES

This tool enables batch distribution of ERC-20 tokens on any Arbitrum Orbit L3 chain (customizable L3 networks built on Arbitrum technology) to multiple recipient addresses in a single atomic transaction. It connects to your wallet via BGWallet, reads the token contract bytecode and verified source, fetches your current balance and allowance, and constructs a batched transfer that sends tokens to each address with specified amounts. The batch executes through a compatible multisender contract (either from the BULKSEND registry or a manually entered address), ensuring all recipients receive their tokens simultaneously or the entire transaction reverts. This is ideal for Orbit chain airdrops, ecosystem incentives, cross-L3 asset distributions, or any scenario requiring efficient multi-recipient token transfers on custom L3 networks with potentially different gas tokens and fee structures.

HOW TO USE

1. Connect your wallet using the "Connect" button (BGWallet integration).

2. Ensure you are connected to the target Orbit L3 chain (the tool will display the chain ID).

3. Enter the token contract address (any ERC-20 token on the target Orbit chain).

4. Click "Load token details" to automatically detect the token's symbol, name, and decimals.

5. Enter the sender/multisender contract address. If your chain is in the BULKSEND registry, you can leave this blank; otherwise, enter the address manually.

6. Paste your recipient list — one address and token amount per line, separated by space or comma.

7. Click "Parse & preview" to validate addresses and see a summary table.

8. Review the sender information: your address, token balance, required total (including network fee), current allowance, and the batch sender contract details.

9. If allowance is insufficient, click "Approve" to authorize the sender contract to spend your tokens.

10. Click "Send batch" to execute the atomic transfer. The progress bar will show transaction status.

TECHNICAL MECHANISM

The tool leverages the BotGentz multisender contract (BULKSEND registry) or any compatible ERC-20 multisender contract that implements a `sendERC20` function with fee mechanism. It dynamically fetches the current fee and owner address from the contract (never hardcoding stale values). The approval process grants exactly the required total amount — not an unlimited allowance — enhancing security. The contract's `sendERC20` method takes arrays of recipient addresses and amounts, processes each transfer in a loop, and ensures all succeed before finalizing. The transaction includes the protocol fee as `msg.value` (which may be in a custom gas token on Orbit chains). The tool automatically detects the token's decimals using the `decimals()` function, ensuring accurate parsing of amounts regardless of precision. It validates total required funds (sum of all transfers + fee) against the sender's balance before submission, catching underfunding early. For Orbit chains with custom gas tokens, the tool respects the chain's native gas mechanics through the provider.

WHAT IT CANNOT SEE

This tool cannot guarantee recipient addresses are valid beyond basic Ethereum address format validation (0x + 40 hex characters). It does not verify if recipients are contracts, if they can receive the token, or if they have been blacklisted by the token contract. The tool cannot recover from a failed batch — due to the atomic nature of the transaction, if any single transfer fails (e.g., blacklisted recipient, insufficient gas, contract revert), the entire batch reverts and no tokens are sent to anyone. It cannot send to zero addresses or self, or exceed the block gas limit (which limits batch size). The tool does not simulate the transaction beforehand, so unexpected reverts may occur during execution. It relies entirely on the token contract behaving as expected — any changes to the token's logic (e.g., upgrades, pausing, blacklisting) could cause the batch to fail. The tool cannot detect if a token is a honeypot, has hidden transfer fees, or imposes transfer restrictions that would cause the batch to fail. Orbit chain-specific limitations include custom gas tokens (the fee displayed may be in a non-ETH token), different block times, sequencer dependencies, and L3-specific mechanics that may affect transaction propagation. The tool cannot automatically discover the correct sender contract address for Orbit chains not in the BULKSEND registry — you must provide it manually.

PLEASE NOTE

This tool is designed for any Arbitrum Orbit L3 chain. It reads the chain ID and attempts to use the BULKSEND registry, but many Orbit chains are not listed — you must manually enter the sender contract address. The sender contract must implement the `sendERC20` function with a fee mechanism. The tool charges a fee in the chain's native gas token (which may be ETH, a custom token, or the chain's own currency). Always review the fee, contract address, and owner before approving or sending. This tool is provided as-is — verify all transactions carefully, especially when dealing with custom Orbit chains that may have unique mechanics, different gas tokens, or non-standard EVM behavior. Transactions on Orbit L3 chains may have different confirmation times and security guarantees compared to L2 or L1 networks.