zkSync Era Native ETH Batch Sender

WHAT IT DOES

This tool allows you to send native ETH to multiple recipients on the zkSync Era network in a single transaction. Instead of sending one transaction per recipient — which wastes gas and time — it batches all transfers into one contract call using the Disperse.app compatible multisend contract. You provide a list of recipient addresses and amounts, and the tool calculates the total ETH needed including the contract fee, verifies your balance, and executes the batch transfer in one operation. No token approvals are required since you're sending native ETH directly from your wallet. This is ideal for payroll, airdrops, or any bulk distribution of ETH on zkSync Era.

HOW TO USE

Connect your EVM wallet and ensure you are on the zkSync Era network (chainId 324). Enter a list of recipients and amounts (one per line, separated by commas). Click "Preview batch" to see the total ETH to send, the contract fee, and the grand total including gas. Your wallet balance is displayed and a progress bar shows how much of your balance will be used. The fee is charged in ETH and is added to the total amount you send. Once verified, click "Send batch" to execute the transfer. The transaction is sent with the exact total amount as the value, and the contract distributes it to all recipients automatically. The transaction status and a zkSync Era explorer link are displayed after completion.

TECHNICAL MECHANISM

This tool uses the disperseEther() method on the shared BotGentz sender contract, which is pre-deployed on zkSync Era and other EVM chains. It reads the current fee live from the contract each time using the fee() method, ensuring you never pay an outdated fee that could cause a revert. The tool calculates the total amount needed as sum(amounts) + fee, then checks your ETH balance against this total. Unlike ERC-20 transfers, native ETH sends require no approval step — the contract simply receives the ETH as value and distributes it. The contract uses disperseEther() which accepts parallel arrays of recipients and amounts, matching each recipient to their corresponding amount in order. Gas costs are reported using effectiveGasPrice from the transaction receipt, giving you the actual spend after EIP-1559 compression. The total amount displayed includes the fee, but gas is paid separately from your wallet and is not part of the contract's value. The tool also displays the contract owner so you know who controls the fee parameter.

WHAT IT CANNOT SEE

This tool cannot verify that the recipient addresses you provide are valid wallets capable of receiving ETH. Some addresses may be smart contracts that do not implement a receive() or fallback function and could reject ETH, causing the entire batch to fail. It cannot simulate off-chain recipient willingness to receive or guarantee delivery if a recipient contract is malicious or poorly coded. It cannot protect you from sending ETH to the wrong address or from sending to addresses that cannot accept ETH (e.g., some contract addresses that are not payable). It does not account for zkSync Era-specific gas fee structures beyond the submitted transaction — gas costs on zkSync Era can vary based on L1 data availability fees and network congestion. It cannot predict the final gas cost before the transaction is mined. It cannot verify that the sender contract exists on zkSync Era if the chain ID is not in the registry.

PLEASE NOTE

This tool works exclusively on EVM-compatible chains, specifically zkSync Era (chainId 324). It requires an EVM wallet bridge (injected via BGWallet) and will not function on non-EVM networks like Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, or XRP. Always double-check recipient addresses and amounts before sending, as irreversible transactions on the blockchain cannot be undone. The fee is charged in ETH and is added to the total amount you send, but gas costs are separate and paid from your wallet balance on top of the transfer amounts. On zkSync Era, gas costs can be higher during periods of network congestion or high L1 data availability fees.