ERC-4626 Vault Share Batch Distributor

WHAT IT DOES

ERC-4626 Vault Share Batch Distributor lets you distribute vault shares (yield-bearing tokenized positions) from any ERC-4626 compliant vault to many recipient addresses in a single batched transaction. You provide the vault contract address, and the tool reads the vault share balance, underlying asset balance, total assets, total supply, conversion rates, vault decimals, share decimals, and recipient addresses directly from the connected wallet. The tool calculates the total share amount required (transfers + network fee) and handles the ERC-4626 approval and batched transfer execution through the BotGentz sender contract, significantly reducing transaction costs compared to sending shares 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 ERC-4626 vault contract address you wish to distribute shares from (the tool will fetch the vault's asset address, decimals, symbol, and conversion rates automatically). Paste your recipient list in the format "address,amount" (one per line, where amount is in vault shares) and click parse to validate entries and compute the total. Review the contract details, current fee, owner, your share balance, and the approximate asset value of the shares being distributed. Click "Approve exact amount" to authorize the batch sender contract to spend the total shares 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 shares 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 (shares + 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 shares. The tool also fetches and displays the current asset-to-share conversion rate, giving users visibility into the underlying value being distributed. The vault address is provided by the user, allowing support for any ERC-4626 vault 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 vault shares or have hooks that may revert. It cannot detect or prevent failures due to vault-specific mechanisms including fee-on-transfer, rebasing, pausing, custom share transfer logic, or deposit/withdrawal limits. It cannot simulate or prevent reverts from custom recipient contract logic. It cannot verify the vault contract is a legitimate ERC-4626 implementation. It cannot guarantee the vault's asset-to-share conversion rate is accurate at the time of execution, as the rate may change between transaction submission and confirmation due to yield accrual or market activity. Additionally, it cannot detect if the vault has been paused or if transfers are restricted.

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 vault contract address must be provided manually by the user. Always review the contract address, fee, share price, and total amount displayed before signing any transaction. Users are responsible for ensuring recipient addresses are correct and that they have sufficient share balance to cover the total amount plus the network fee. Be especially cautious with vaults that have dynamic share prices due to yield accrual, as the value of shares may change between when you approve and when the transaction is executed.