Zircuit USDC Batch Sender

WHAT IT DOES

This tool enables you to batch send USDC from your wallet to multiple recipients in a single transaction on Zircuit. Instead of sending USDC 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 USDC balance, allowance, and the current gas price before submitting the transaction. You specify the USDC contract address, the decimals (usually 6), and a list of recipient addresses with per-recipient amounts. The tool computes the total USDC to send, checks your balance, verifies you have sufficient allowance for the sender contract, and submits one transaction that distributes USDC to all recipients atomically. If allowance is insufficient, the tool automatically requests approval before sending. This is a true push distribution — recipients receive USDC directly without any claim action required.

HOW TO USE

Connect your EVM wallet via the BotGentz wallet bridge. Select Zircuit from the network dropdown (or choose the appropriate chain where Zircuit is deployed). Enter the USDC contract address for the current chain. Set the USDC decimals (6 for standard USDC, 18 for bridged variants — check your contract). In the text area, list each recipient on a separate line with their address and the amount of USDC to send, separated by a comma. Amounts should be in base units (e.g., 100 = 100.00 USDC with 6 decimals). Click "Review batch" to see your USDC 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 USDC 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 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. 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 USDC contract using the ERC-20 ABI and checks `balanceOf()`, `allowance()`, and `decimals()` for your wallet. The tool computes the total USDC amount from the recipient list and verifies both your USDC balance and native balance (for gas fees) 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 USDC atomically within the same transaction using `transferFrom` from your wallet. After confirmation, it logs gas usage using `receipt.effectiveGasPrice`.

WHAT IT CANNOT SEE

This tool cannot verify whether the USDC contract address you provided is the correct canonical USDC for Zircuit — if you enter a bridged or fake USDC address, the tool will send that token instead of real USDC. It cannot verify USDC peg stability or confirm that 1 USDC on Zircuit maintains its $1 value. 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 Zircuit 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 USDC 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 both the fee and gas costs. This is a push distribution — the sender pays all gas, recipients receive USDC without any action.