Delayed Batch Sender (Executes at Future Block)

WHAT IT DOES

This tool enables you to schedule a batch send of ERC-20 tokens to multiple recipients on any supported EVM Layer 2 network (Arbitrum, Base, Optimism, Polygon, and more), with the transaction set to execute at a specified future block number. Instead of sending immediately, you define a target block in the future, and the tool prepares the transaction to be executed when the chain reaches that block. This is useful for coordinating token distributions with other on-chain events, avoiding peak gas times, or ensuring that a snapshot is taken before the distribution occurs. The fee is paid in the chain's native token.

HOW TO USE

Connect your wallet on any supported L2. Enter the ERC-20 token you want to distribute, a list of recipients with custom amounts, and the target future block number. The tool will display the current block number, the target block, and the number of blocks until execution. Review the details and click "schedule & send". The tool will prepare the batch transaction for execution at the specified block. Note: scheduling requires a relayer or transaction scheduling contract—in this implementation, a warning is shown and the transaction is sent immediately for demonstration purposes.

TECHNICAL MECHANISM

The tool reads the current block number from the connected provider and compares it to the user-specified target block. It validates that the target is in the future. The tool aggregates recipient addresses and amounts, reads the distribution token's decimals dynamically, and calculates the total distribution amount. It reads the current fee from the BotGentz sender contract using the fee() view function, which is set by the contract owner and may change over time. The fee is attached to the sendERC20 transaction as the value field. The tool displays the contract owner and the fee prominently before you sign. Allowances are set to the exact total distribution amount, never unlimited. In production, the transaction would be submitted to a relayer or scheduling contract that holds the transaction until the target block is reached. This tool demonstrates the user interface and preparation steps for such a scheduling system.

WHAT IT CANNOT SEE

- Native gas tokens as distribution tokens (only ERC-20 tokens are supported)

- Any non-ERC-20 token standard (e.g., ERC-721, ERC-1155)

- Token tax/fee-on-transfer mechanics for non-standard tokens

- Incorrectly entered recipient addresses or amounts (no recovery)

- Contracts that reject transfers (e.g., blacklisted addresses)

- Recurring sends — each execution is a separate transaction

- Rebasing or fee-bearing tokens — assumes standard ERC-20

- Off-chain data or cross-chain state

- Gas cost estimates beyond the contract fee

- Chain reorganizations that may affect the target block

- Guaranteed execution at the exact target block — timing depends on block production

- The underlying scheduling mechanism — this tool prepares the transaction but requires external infrastructure for delayed execution

PLEASE NOTE

This tool is designed for EVM Layer 2 networks supported by the BotGentz registry. Future block scheduling requires a relayer or transaction scheduling contract to hold and execute the transaction at the correct block. The current implementation demonstrates the preparation and approval steps; the actual delayed execution depends on external infrastructure. The fee is read live from the contract and may change between reads and transaction execution. Always verify the contract owner, the fee amount, the target block, and the total distribution amount before signing. You are responsible for ensuring the recipient addresses and amounts are correct, the tokens are transferable, and you have sufficient native balance for both the fee and gas. The tool does not automatically retry failed transactions or recover from network congestion; each execution is a single, discrete operation.