Polygon zkEVM ERC-20 Batch Sender

WHAT IT DOES

This tool enables you to batch send any ERC-20 token from your wallet to multiple recipients in a single transaction on Polygon zkEVM. Instead of sending tokens to each recipient individually and paying gas for every transfer, it combines all transfers into one call to a shared batch-sender contract. The tool reads your token balance, allowance, and the current gas price before submitting the transaction. You specify the token contract address, the decimals (customizable for any ERC-20 token), and a list of recipient addresses with per-recipient amounts. The tool computes the total tokens to send, checks your balance, verifies you have sufficient allowance for the sender contract, and submits one transaction that distributes tokens to all recipients atomically. If allowance is insufficient, the tool automatically requests approval before sending. This is a true push distribution — recipients receive tokens directly without any claim action required. The tool works with any ERC-20 token on Polygon zkEVM, including custom tokens, stablecoins, governance tokens, and utility tokens. Polygon zkEVM's low transaction costs make it ideal for large-scale token distributions.

HOW TO USE

Connect your EVM wallet via the BotGentz wallet bridge. Select Polygon zkEVM (chain ID 1101) from the network dropdown (or any EVM chain where your token is deployed). Enter the token contract address. Set the token decimals (e.g., 18 for most ERC-20 tokens, 6 for USDC/USDT). Optionally enter a token symbol for display (the tool will try to read it from the contract). In the text area, list each recipient on a separate line with their address and the amount of tokens to send, separated by a comma. Amounts should be in base units (not including decimals — e.g., 100 for 100 tokens with 18 decimals). Click "Review batch" to see your token balance, allowance, the sender contract fee, and the total amount being sent. The tool will display a warning if your allowance is insufficient. If everything looks correct, click "Sign & send batch" — your wallet will first ask you to approve the token spend if needed, then to confirm the batch transaction. Once confirmed, the tool shows progress and the final transaction hash with a link to the Polygon zkEVM block explorer.

TECHNICAL MECHANISM

This tool uses the BotGentz shared bulk-sender contract registry, keyed by chain ID and ERC standard. It looks up `BULKSEND[String(chainId)].erc20` to get the sender contract address for the current chain. For Polygon zkEVM (chain 1101), the sender contract is `0x956D760F8665358Ea1a9F11b82913020e5479376` (using the same address as other L2s). The tool creates a contract instance using `BGWallet.getSigner()` connected to the current chain's provider. It calls `fee()` and `owner()` on the sender contract live — no values are cached. It also instantiates the token contract using the ERC-20 ABI and checks `balanceOf()`, `allowance()`, and `decimals()` for your wallet. The tool computes the total token amount from the recipient list and verifies both your token balance and native balance (for the sender contract fee) are sufficient. If allowance is insufficient, it sends an approval transaction for the exact total amount (not unlimited) before the batch transfer. The batch transfer uses `batchSend20(address token, address[] recipients, uint256[] amounts)` on the sender contract, sending the contract fee as `msg.value` in native tokens. The sender contract then iterates the recipient list and transfers tokens atomically within the same transaction using `transferFrom` from your wallet. After confirmation, it logs gas usage using `receipt.effectiveGasPrice`. This works for any ERC-20 token on Polygon zkEVM.

WHAT IT CANNOT SEE

This tool cannot verify whether the token contract address you provided is legitimate or is the correct token for Polygon zkEVM — if you enter a fake or malicious token address, the tool will send that token instead. It cannot verify token contract legitimacy, audit status, or any token-specific transfer restrictions (e.g., blacklists, frozen tokens, transfer fees, or paused transfers). It cannot confirm recipient wallet readiness or guarantee that recipients can receive ERC-20 tokens. The tool does not validate that the token contract implements the ERC-20 standard or has the required `transferFrom` function. It cannot detect front-running or mempool congestion. It cannot provide a cross-chain receipt or rollback mechanism. It also cannot verify that the decimals value you entered matches the actual contract decimals — the tool warns but does not automatically correct discrepancies.

PLEASE NOTE

This tool is EVM-only. It works on Polygon zkEVM and other EVM chains where the BotGentz registry has an erc20 entry. It does not support Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, or XRP. The tool requires the token contract to be deployed on the chain and for the sender contract to have an erc20 entry in the registry. Always test with a small amount and a single recipient before sending large batches. The sender contract charges a fee in native tokens — ensure you have enough native balance to cover the fee. This is a push distribution — the sender pays all gas, recipients receive tokens without any action. Check token-specific restrictions like transfer fees, blacklists, or paused transfers before sending.