Dust Token Multi-Wallet Batch Sweeper (Any L2)

WHAT IT DOES

This tool enables you to sweep ERC-20 token dust from multiple source wallet addresses to a single destination wallet in one batch transaction across supported L2 networks, but only for wallets with a balance above a user-defined minimum threshold. It reads your connected wallet address, the chain ID (must be one of the L2 chains in the BULKSEND registry), ERC-20 token balances and decimals (auto-detected) for each source wallet you provide, the destination address, and a minimum threshold amount per source wallet. The tool calculates the token balance for each source wallet, filters out any wallet with a balance below the threshold, then constructs a single batched transfer that sends only the eligible source wallets' full balances to the destination. You sign one transaction that pays gas and executes all transfers atomically. The tool uses the shared BotGentz sender contract for the detected L2 chain from the BULKSEND registry to perform the batch transfer, charging a small fee in ETH for each batch. You must approve the sender contract for the exact total amount of tokens being swept before the batch can be executed. This is ideal for consolidating small "dust" balances that would otherwise be uneconomical to sweep individually, allowing you to set a threshold to avoid wasting gas on negligible amounts.

HOW TO USE

Connect your wallet (supported L2 only), enter the ERC-20 token contract address, the destination wallet address, a minimum threshold amount (in token units), and list the source wallet addresses (one per line). The tool will automatically detect the token decimals, read the balance of each source wallet, filter out any balance below the threshold, compute the total of eligible wallets, and show you the combined amount including the contract fee. You first approve the sender contract to spend the total token amount from your connected wallet (which must hold the tokens being swept), then you execute the sweep. Each sweep is a single signed transaction; for recurring sweeps, you repeat the process manually. The tool does not manage private keys—you must have control over the source wallets, but the tool only reads their balances and constructs the transfer from the connected wallet.

TECHNICAL MECHANISM

The sweep is performed by calling sendERC20Batch(address token, address[] calldata recipients, uint256[] calldata amounts) on the BotGentz sender contract for the specific L2 chain. For each source wallet, the tool reads its current token balance using balanceOf(). It then compares each balance against the user-defined threshold (converted to wei using the token's decimals). Only wallets with a balance greater than or equal to the threshold are included. The tool builds a batch where the recipient is always the destination address, and the amount is that eligible source wallet's balance. The contract transfers tokens from the caller (your connected wallet) to each recipient, but crucially, the source wallets are not the sender—the connected wallet pays the tokens. This means your connected wallet must hold all the tokens you intend to sweep from the source addresses. The fee is read live from the contract's fee() function and must be paid in ETH as part of the transaction value. The tool checks your token balance and allowance against the total required (sum of all eligible balances plus fee) before signing, preventing partial failures. All transfers are sequential within the contract, ensuring atomicity—if any transfer fails, the entire batch reverts. The auto-detection of token decimals ensures amounts are correctly scaled regardless of the chain.

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 each transfer, the amount received by the destination will be less than the source balances. It cannot recover incorrectly entered source or destination addresses—invalid addresses are simply skipped. It cannot send to contracts that reject transfers (e.g., blacklisted addresses). It assumes your connected wallet holds all the tokens being swept; it does not pull tokens from source wallets directly. It cannot verify that you actually control the source wallets—you must ensure you have the necessary private keys or signatures to authorize the sweep. It does not automatically execute recurring sweeps; each execution is a separate transaction that you manually trigger. The user-defined minimum threshold is not validated against token decimals or gas costs; sweeping small balances may still cost more in gas than the token value and the tool does not calculate this for the user. You must set a threshold that makes economic sense for your specific token and chain.

PLEASE NOTE

This tool works on any L2 chain in the BULKSEND registry: Arbitrum, Base, Optimism, Polygon, and others. It does not support Ethereum mainnet or other non-registered chains. The connected wallet must hold the tokens being swept from the source addresses—the source wallets are read-only for balance calculation. The BotGentz sender contract is hardcoded and verified per chain; you can review its source code on the respective block explorer. Always confirm the fee, contract address, detected decimals, threshold, and total amount before signing any transaction. This tool is provided as-is; you are responsible for verifying source addresses, destination address, setting an appropriate threshold, and ensuring you have control over the source wallets.