Time-Locked Batch Sender (Base)

WHAT IT DOES

Time-Locked Batch Sender (Base) enables ERC-20 token payroll distributions on the Base network that are restricted by a time-lock condition. Connect your wallet, enter the payroll token address, list recipient addresses with payment amounts, set a pay frequency, and define a time-lock timestamp with a condition (send before or after that time). The tool reads your token balance, native ETH balance, current allowance, and BotGentz sender contract fee, then verifies the current block timestamp against the time-lock condition before allowing any transfer. If the condition is met, it batches all transfers into a single transaction. This is ideal for scheduled payments, vesting schedules, or any scenario where you want to prevent premature distributions.

HOW TO USE

1. Connect your wallet using the built-in connector. Ensure you are on the Base network (chain ID 8453).

2. Enter the ERC-20 token address you wish to use for payroll.

3. Provide a list of recipients and their payment amounts (one per line, comma-separated).

4. Set the pay frequency in seconds (e.g., 2592000 for 30 days) to define the recurring schedule.

5. Choose the time-lock type: "Send before timestamp" or "Send after timestamp".

6. Enter the Unix timestamp that defines the time-lock boundary.

7. Review the current block time, time-lock status, total tokens, native fee, and your balances.

8. Click "Send Time-Locked Batch" — the tool will verify the time-lock condition, approve the exact total token amount if needed, and execute the batch transfer only if the condition passes. The contract charges a fee in native ETH, which is deducted from your wallet.

TECHNICAL MECHANISM

The tool uses the shared BotGentz sender contract deployed on Base. It reads the contract's fee and owner address on-chain each time, ensuring the fee is current and never stale. The time-lock is enforced by querying the current block timestamp from the provider and comparing it against the user-specified timestamp and condition type. If the condition is not met, the tool aborts the transaction before any on-chain interaction occurs. The approval step authorizes the sender contract for the exact total token amount (not unlimited) to minimize risk. The batch transfer is executed as a single transaction with the fee sent as value. All transfers are sequential and awaited, preventing nonce conflicts. The tool performs a native balance check before sending to ensure the fee can be covered.

WHAT IT CANNOT SEE

This tool cannot send native gas tokens (ETH) or any token standard other than ERC-20. It cannot detect token tax, fee-on-transfer, or rebasing mechanics. It cannot recover incorrectly entered recipient addresses or amounts. It cannot send to contracts that reject transfers. It does not simulate or estimate gas costs beyond the contract fee. Memo data storage is not supported by the standard BotGentz sender contract. The tool does not verify employee eligibility, employment status, or payroll approval. It does not handle tax withholding, benefits, or deductions, and does not support off-ramping to fiat. The time-lock is enforced client-side and may be bypassed by direct contract interaction; it is not enforced on-chain. The tool does not support recurring time-locks per cycle.

PLEASE NOTE

This tool is for EVM-compatible chains only, specifically Base. Ensure you are on the correct network and have sufficient ETH for the fee before sending. The BotGentz sender contract is a shared, community-audited contract; review its address and owner before each use. Time-lock conditions are checked at the time of sending and are not enforced on-chain after the transaction is submitted. All transactions are irreversible.