Base ERC-1155 Batch Sender

WHAT IT DOES

This tool enables the batch distribution of ERC-1155 tokens (multi-token standard) 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 balances for each token ID and approval status, and constructs a batched transfer that sends specified amounts of multiple token types to designated recipients. The batch executes through the BotGentz sender contract, ensuring all transfers succeed or the entire transaction reverts. This is ideal for gaming asset distribution, multi-token airdrops, collection management, inventory transfers, or any scenario requiring efficient multi-token, multi-recipient transfers 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 ERC-1155 contract address (any multi-token contract on Base).

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

5. Paste your transfer list — one transfer per line with recipient address, token ID, and amount, separated by spaces or commas.

6. Click "Parse & preview" to validate addresses, token IDs, and amounts, and see a summary table.

7. Review the sender information: your address, token balances per ID, approval status, batch sender contract details, and fee.

8. If not approved, click "Set approval" to authorize the sender contract to transfer your tokens on your behalf.

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-1155 transfer function. It dynamically fetches the current fee and owner address from the contract (never hardcoding stale values). Unlike single-token standards, ERC-1155 supports multiple token types within a single contract — the tool groups transfers by recipient and uses `safeBatchTransferFrom` to send multiple token IDs and amounts in one call. The contract uses the `sendERC1155` method, which takes arrays of recipients, token IDs, and amounts, processes each batch transfer, and ensures all succeed before finalizing. The transaction includes the protocol fee as `msg.value`. The tool performs per-token balance verification using `balanceOf` before sending, checking that you have sufficient quantity of each token ID. It also reads the token name and symbol for clear identification, and checks `isApprovedForAll` to verify operator approval for the sender contract. 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 that can receive ERC-1155 tokens, if they implement the required `onERC1155Received` or `onERC1155BatchReceived` hooks, or if they will accept the token types being sent. The tool cannot recover from a failed batch — due to the atomic nature of the transaction, if any single token transfer fails (e.g., recipient contract rejects the token, insufficient balance, approval issues), the entire batch reverts and no tokens are transferred. 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 contract's logic (e.g., upgrades, pausing, transfer restrictions) could cause the batch to fail. The tool cannot detect if tokens have royalties or transfer fees that might affect the transaction, nor can it detect if specific token IDs are locked, frozen, or have other transfer restrictions. 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 multi-token contracts that have complex transfer logic or multiple token types with different properties. 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.