Ethereum L1 Recurring Payroll Batch Sender

WHAT IT DOES

Ethereum L1 Recurring Payroll Batch Sender is a specialized DeFi tool that automates recurring token payments to multiple recipients through individual, non-custodial payment contracts. Instead of manually sending payments each cycle, this tool deploys a separate recurring payment contract for each recipient, funding each contract with the total token amount required for all scheduled payments and attaching a release schedule based on your specified interval and number of payments. Each contract is independent—recipients can claim their periodic payments automatically according to the schedule you define. This tool is ideal for payroll, subscription payments, grant disbursements, staking rewards, and any scenario where you need to make regular token distributions over time on Ethereum L1. By deploying all payment contracts in a single batched transaction, you save significantly on gas costs compared to deploying each contract individually, while ensuring every recipient gets a fully functional, audited recurring payment contract with their allocation locked and scheduled for release.

HOW TO USE

Connect your Web3 wallet to Ethereum L1. Enter the ERC-20 token contract address you wish to distribute. Configure the payment parameters: payment interval (the time between each payment in seconds), number of payments (how many total payments each recipient will receive), and start time (Unix timestamp; leave 0 to start from the current block time). Paste or upload your list of recipients in the format "address, amount_per_payment" with one entry per line—amounts are in human-readable token units per payment cycle. The tool calculates the total tokens required per recipient (amount_per_payment × number_of_payments) and the overall total. Review the sender contract address, fee, and contract owner for transparency. Click the deploy button, review the transaction in your wallet, and confirm. The tool deploys one recurring payment contract per recipient sequentially within the same batched transaction. After confirmation, each recipient receives their own contract address and can begin claiming payments according to the schedule you defined.

MECHANISM: BATCH RECURRING PAYMENT CONTRACT DEPLOYMENT

The tool interacts with a specialized BotGentz recurring payment factory contract that creates individual payment contracts for each recipient in a single batched transaction. For each recipient-amount pair, the tool calls the createRecurringPaymentContract function on the factory, passing the token address, recipient address, amount per payment, payment interval, number of payments, and start time. The factory deploys a new Minimal Proxy (EIP-1167) payment contract for each recipient, initializing it with the provided parameters and transferring the total token amount (per-payment amount × number of payments) from the sender to the newly created contract. Each contract implements a linear release schedule: recipients can claim a fixed amount at each interval after the start time, with the contract automatically tracking claims and releasing only the earned portion. The tool reads the fee() function live from the factory, splitting the fee evenly across each deployment and including it in the value sent with each call. The tool checks the sender's token balance against the total required (all recipient totals plus fee) and approves the factory for the exact total before beginning deployment. All contracts use a standard, audited recurring payment template with configurable intervals and claim mechanics.

WHAT IT CANNOT SEE

This tool reads no on-chain data directly. It does not verify that recipient addresses are valid, that the sender has sufficient token balance, or that the token contract address provided is correct. It cannot guarantee that all payment contracts will deploy successfully—if one deployment fails due to a recipient address being a contract that reverts, insufficient gas, or any other reason, the entire batch reverts, leaving no contracts deployed. It cannot verify that payment parameters are legally, tax, or economically appropriate for your use case. It cannot detect if the token contract uses non-standard transfer mechanics that might break payment contract functionality. It cannot provide post-deployment monitoring or modification of payment schedules—once deployed, contracts are immutable and tokens cannot be recovered. It cannot ensure recipients will claim their payments or that the token retains stable value over the payment period. It does not account for gas price fluctuations during execution or provide fallback mechanisms for mid-batch failures. It cannot account for changes in network conditions or token availability during the recurring payment window.

PLEASE NOTE

This tool works exclusively on EVM-compatible chains and is designed for Ethereum L1. It requires the user to have sufficient native ETH for gas and sufficient token balance to cover the total amount sent (all payments for all recipients) plus the sender contract fee. The user is solely responsible for verifying the token contract address, recipient addresses, payment parameters, and amounts before signing. Always test with a small batch first to confirm the setup is correct. Once recurring payment contracts are deployed, they cannot be modified or undone—the tokens are locked according to the schedule you set. The payment factory contract addresses are hardcoded per chain and are publicly available for verification; no third-party custody is involved; you remain in full control of your wallet and funds at all times. Recipients will need to interact with their individual payment contracts to claim tokens at each interval—they are not automatically pushed.