L1-to-Optimism Bridge-and-Batch-Send Tool

WHAT IT DOES

This tool enables you to bridge ERC-20 tokens from Ethereum mainnet to Optimism and distribute them to multiple recipients in a coordinated two-step process. It reads your connected wallet address, the chain ID (must be 1), L1 token balances and decimals, recipient addresses on Optimism, and amounts. You configure the distribution parameters—amount per recipient, frequency, and duration—and the tool guides you through the sequence: first approving the L1 BotGentz sender contract, then bridging the total token amount to Optimism via the Optimism bridge, and finally sending the batch on L2. The tool uses the L1 BotGentz sender contract (0xE0F4E170C434071b167ABA0e64DC3689536f2E07) for the L1 batch send to the bridge, and the L2 BotGentz sender contract (0x956D760F8665358Ea1a9F11b82913020e5479376) for the L2 distribution. Each step is a separate transaction; the tool coordinates them but does not execute them atomically.

HOW TO USE

Connect your wallet (Ethereum mainnet only), enter the L1 token contract address, and list your L2 recipient addresses with amounts (one per line). The tool will parse the list, show you the total amount including the contract fee, and display your L1 balance. You first approve the L1 sender contract to spend the total token amount. Then, you bridge the tokens to Optimism by sending them to the Optimism L2 gateway address—this is an L1 transaction that deposits your tokens into the bridge. After the L1 transaction is confirmed and the bridge finalizes (which may take some time), you switch your wallet to Optimism and use the L2 batch sender tool to distribute the tokens to your recipients. The tool does not automate scheduling—you decide when to execute each step.

TECHNICAL MECHANISM

The L1 portion of the process uses the sendERC20Batch function on the BotGentz sender contract. The tool sends the entire batch of tokens to the Optimism bridge gateway address in a single L1 transaction, paying the contract fee in ETH. The bridge then mints the equivalent tokens on L2. The tool checks your L1 balance and allowance against the total required (sum of amounts plus fee) before signing, preventing partial failures. On the L2 side, the BotGentz sender contract (0x956D760F8665358Ea1a9F11b82913020e5479376) is used to batch send the bridged tokens to the recipients. The tool does not hardcode the bridge gateway address; instead, it relies on the user to provide the correct gateway address as part of the recipient list or to use the L2 batch sender after bridging. This approach keeps the tool generic and avoids hardcoded bridge addresses that may change or vary.

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 token deducts a fee on transfer, the amount received on L2 or 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 bridge routes or canonical L2 token addresses; you must ensure the token is supported by the Optimism bridge. The bridge deposit and L2 batch send are separate transactions—the tool coordinates them but does not execute them atomically; you must wait for L1 confirmation before sending on L2. It does not automatically execute recurring sends—each execution is a separate sequence of transactions. The tool is limited to Ethereum mainnet for the bridge step and Optimism for the L2 step.

PLEASE NOTE

This tool works exclusively with Ethereum mainnet (chainId 1) for the bridge step and Optimism (chainId 10) for the L2 distribution. The BotGentz sender contracts are hardcoded and verified; you can review their source code on Etherscan and Optimistic Etherscan. Always confirm the fee and contract address before signing any transaction. You must have the L2 token address ready for the L2 batch send step. This tool is provided as-is; you are responsible for verifying recipient addresses, amounts, and that your token is supported by the Optimism bridge.