Governance Token Batch Distributor

WHAT IT DOES

Governance Token Batch Distributor lets you distribute any governance token (UNI, COMP, MKR, AAVE, and other ERC-20 governance tokens) to many recipient addresses in a single batched transaction. You provide the token contract address, and the tool reads the token balance, native ETH balance, token decimals, and recipient addresses directly from the connected wallet. The tool calculates the total amount required (transfers + network fee) and handles the ERC-20 approval and batched transfer execution through the BotGentz sender contract, significantly reducing transaction costs compared to sending tokens 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. Enter the governance token contract address you wish to distribute (the tool will fetch the token's decimals and symbol automatically). 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 token balance. Click "Approve exact amount" to authorize the batch sender contract to spend the total amount needed (approval is set to the precise total, not unlimited). Then click "Send batch" to execute the batched transfer. Progress is shown on a progress bar, and transaction hashes are displayed upon completion.

TECHNICAL MECHANISM

The tool uses the BotGentz shared sender contracts deployed on multiple EVM chains, looked up by chain ID from the BULKSEND registry. 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 (in native currency) is added to compute the total required balance. The approval transaction sets the exact total (amounts + fee) for the sender contract. The sender contract receives the fee in native currency (ETH/BNB/MATIC/etc.) and executes the transfer via sendERC20() in a single batched call, with each transfer being processed sequentially to avoid nonce conflicts. 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 token address is provided by the user, allowing support for any ERC-20 governance token on the selected network.

WHAT IT CANNOT SEE

This tool cannot verify recipient addresses are valid externally owned accounts or contracts. It cannot detect if recipient contracts support governance token transfers or have custom logic that might revert. It cannot detect or prevent failures due to token-specific mechanisms including rebasing, fee-on-transfer, blacklist functionality, pausing, or custom transfer logic. It cannot simulate transactions or prevent reverts from custom recipient contract logic. It also cannot detect if a recipient address is a contract that does not implement the ERC-20 transfer standard correctly, nor can it verify that the provided token contract address is a legitimate governance token. Additionally, it cannot guarantee that recipients will retain voting power or delegation status after transfer, as some governance systems may have time locks or delegation requirements.

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 (ETH, BNB, MATIC, etc.) and is added to the total amount deducted from your balance. The token contract address must be provided manually by the user. 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. Be aware that some governance tokens may have transfer restrictions or minimum holding requirements that could affect the distribution.