Treasury Diversification Batch Sender (Base)

WHAT IT DOES

Treasury Diversification Batch Sender (Base) lets you send multiple different ERC-20 tokens to multiple recipients in a single batch transaction on Base chain. Define each transfer as recipient address, amount, and token address—or use a default token for simpler entries. The tool groups transfers by token, checks balances and allowances for each token (handling approvals automatically), reads the current fee and owner from the BotGentz bulk-sender contract, checks native balance for fee + gas, and submits batched ERC-20 transfer transactions sequentially for each token group. Perfect for treasury diversification, multi-token airdrops, payroll, or any scenario requiring multiple tokens distributed to multiple recipients.

HOW TO USE

Connect your EVM wallet using the BotGentz wallet bridge. Select Base chain (or another supported chain). Enter your recipient list—one per line with address, amount, and optional token address. If token address is omitted, the default token address is used. Review the summary showing chain, sender contract, recipient count, and a token breakdown (number of recipients and total amount per token). Click "Send batch" to submit. The tool reads the fee and owner, checks your token balances and allowances (approving the sender contract for each token as needed), checks native balance for fee + gas, and sends the batched transactions for each token group. Progress is shown per token group.

TECHNICAL MECHANISM

The tool uses the BotGentz bulk-sender contract registry (BULKSEND) keyed by chain ID and standard (erc20). It connects via BGWallet.getProvider() and BGWallet.getSigner(), then instantiates the sender contract with a minimal ABI including fee(), owner(), and sendERC20(). The fee is read live from the contract—never hardcoded. The owner address is also displayed for transparency. Recipients are parsed from user input, grouped by token address. For each token group, the tool auto-detects token decimals via the token contract's decimals() function, converts amounts to wei using ethers.utils.parseUnits(), checks token balance via balanceOf(), checks allowance via allowance(), and submits an approval transaction if needed (approving the exact total for that token group). Native balance is checked against fee + gas reserve. The transaction is submitted via the sender contract with the fee paid in native currency. The receipt is monitored for confirmation.

WHAT IT CANNOT SEE

This tool cannot detect if a recipient address is valid—it accepts any 0x address. It cannot recover from failed transactions without manual retry. It cannot verify that token contracts exist on the chain. It cannot detect if token balances change between the read and send operations. It cannot handle tokens with different decimals seamlessly without per-token configuration—decimal auto-detection may fail for some tokens. It cannot detect if the sender contract has been paused or if the fee has changed between reading and sending. It cannot verify that the token address is correct for the intended token.

PLEASE NOTE

EVM chains only—Base (8453) is the primary chain, but other EVM chains are supported via the dropdown. The BotGentz bulk-sender contracts are used for batch sending—these are shared contracts, not per-user deployments. Always verify the sender contract address, fee, and owner before signing. This tool submits real transactions—gas costs apply. Token addresses vary across chains—verify each token address for the selected chain. The tool is free to use but chain gas fees apply. Always test with a small batch on testnet before mainnet.