Base ERC-20 Batch Sender

WHAT IT DOES

This tool enables the batch distribution of any ERC-20 token to multiple recipient addresses in a single atomic transaction on Base (Coinbase's Layer 2 network). 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 the BotGentz sender contract, ensuring all recipients receive their tokens simultaneously or the entire transaction reverts. This is a universal solution for airdrops, payroll, dividend distributions, treasury management, or any scenario requiring efficient multi-recipient token transfers across any ERC-20 standard token on Base's low-cost, high-speed OP Stack L2.

HOW TO USE

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

2. Ensure you are on Base (chain ID 8453) — the tool will prompt you to switch if needed.

3. Enter the token contract address (any ERC-20 token on Base).

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

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

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

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

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

9. 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) which implements a batched ERC-20 transfer function. 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 uses the `sendERC20` method, which 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`. The tool automatically detects the token's decimals using the `decimals()` function, ensuring accurate parsing of amounts regardless of whether the token uses 6, 8, 18, or any other decimal precision. It also fetches the token symbol for clear display. The tool validates total required funds (sum of all transfers + fee) against the sender's balance before submission, catching underfunding early. Base L2 gas mechanics are handled through the provider, with the tool estimating gas using the contract's `estimateGas` function and applying a 20% safety margin. Base's OP Stack architecture ensures fast finality and low transaction costs.

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 (many tokens have blacklist functionality). 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. Base-specific considerations include sequencer dependencies and varying gas prices that may affect transaction propagation, as well as the OP Stack's unique fee structure.

PLEASE NOTE

This tool is designed exclusively for Base (chain ID 8453). It reads the chain ID and uses the BULKSEND registry to locate the appropriate sender contract (the registry includes Base at 0x956D760F8665358Ea1a9F11b82913020e5479376). The sender contract charges a fee in ETH (native gas token on Base), which is displayed before signing. 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 tokens that have complex transfer logic or restrictions. Transactions on Base may have different confirmation times and gas costs compared to Ethereum L1, and may be subject to sequencer-related delays inherent to the OP Stack architecture.