CRO Batch Sender

WHAT IT DOES

CRO Batch Sender lets you distribute native CRO (Cronos) to many recipient addresses in a single batched transaction. It reads your CRO balance, recipient addresses, and current network fee directly from the connected wallet. The tool calculates the total amount required (transfers + network fee) and executes the batched transfer through the BotGentz sender contract, significantly reducing transaction costs compared to sending individually.

HOW TO USE

Connect your wallet using the built-in wallet connector. The tool automatically detects the current network and loads the appropriate batch sender contract address from the BotGentz registry. Paste your recipient list in the format "address,amount" (one per line) and click parse to validate entries and compute the total. Review the contract details, current fee, owner, and your balance. The fee is displayed in CRO (native currency) and is added to the total transfer amount. Click "Send batch" to execute the batched transfer. Progress is shown on a progress bar, and transaction hashes are displayed upon completion. No token approval is required since you're sending native currency.

TECHNICAL MECHANISM

The tool uses the BotGentz shared sender contracts deployed on multiple EVM chains, looked up by chain ID from the BULKSEND registry. On Cronos (chain ID 25), the contract implements a sendETH() function that accepts an array of recipient addresses and corresponding amounts, along with the total value (transfers + fee) as msg.value. The current fee is read live via sender.fee() and the owner via sender.owner(), never hardcoded. The total amount to send is summed across all rows, and the fee is added to compute the total required balance. The tool verifies that the total required balance (transfers + fee) is available in the wallet before initiating any transaction, ensuring the batch will not fail mid-way due to insufficient funds. The sender contract distributes the CRO to recipients in a single batched call, with each transfer being processed sequentially to avoid nonce conflicts.

WHAT IT CANNOT SEE

This tool cannot verify recipient addresses are valid externally owned accounts or contracts. It cannot detect if recipient contracts are payable or can receive CRO. It cannot simulate or prevent reverts from custom recipient contract logic. It cannot detect if recipients are smart contracts that may reject CRO transfers. It cannot recover CRO sent to non-payable contracts. It also cannot detect if a recipient address is a contract that does not implement the receive() or fallback() function correctly, which would cause the transfer to revert.

PLEASE NOTE

This tool works on EVM-compatible chains only. It requires the wallet to be connected and the current network to be one of the supported chains listed in the BotGentz registry. The fee is paid in the native currency of the network (CRO) and is added to the total amount deducted from your balance. Always review the contract address, fee, and total amount displayed before signing any transaction. Users are responsible for ensuring recipient addresses are correct and that they have sufficient balance to cover the total amount plus the network fee. Sending CRO to smart contracts that are not payable will result in a failed transaction and loss of gas fees.