zkSync Era Recurring Payroll Batch Sender

WHAT IT DOES

zkSync Era Recurring Payroll Batch Sender lets you create recurring payment streams for multiple employees or team members in a single batched transaction on the zkSync Era network. The tool reads your connected wallet and chain ID, automatically selects the BotGentz sender contract for zkSync, and calculates the current fee in native ETH. You provide the payroll token address, a list of employee addresses and recurring amounts, and select the pay frequency (monthly, bi-weekly, or weekly). The tool checks your native ETH balance to ensure you can cover the fee. Each employee receives a recurring payroll stream, all set up in one transaction, saving gas compared to creating streams individually. This is ideal for DAOs, web3 companies, or any organization managing regular payroll with token-based compensation.

HOW TO USE

Connect your wallet and ensure you are on the zkSync Era network (chain 324). Enter the ERC-20 token address you want to use for payroll. Select the pay frequency from the dropdown. Paste your employee list as comma-separated values (one per line: address, amount). Review the summary table showing total per cycle, fee in ETH, and all employees. Click "sign & create recurring payroll" to approve the token spend and execute the transaction. The batch is sent as a single transaction, creating all recurring payroll streams atomically—if any stream fails to create, the entire batch reverts.

TECHNICAL MECHANISM

The tool uses the BotGentz bulk sender registry to fetch the correct contract address for zkSync Era. It reads the current fee from the sender contract's fee() method at execution time—never hardcoding a stale value, because fees are settable by the contract owner and stale fees would cause revert due to underpayment. The tool checks your native ETH balance against the total fee to ensure you have enough ETH for the contract fee and gas. Before sending, it verifies your token allowance and approves the exact total amount to the recurring payroll contract—not an unlimited allowance—then calls the batch recurring payroll function with the recipient array, amounts array, and frequency parameter. The contract processes all streams atomically; if any stream creation fails, the entire batch reverts, leaving your tokens untouched. The tool automatically detects token decimals and symbol, and maps the selected frequency to the contract's expected format.

WHAT IT CANNOT SEE

This tool cannot send native ETH or any token other than ERC-20. It does not detect token tax, fee-on-transfer, rebasing, or deflationary mechanics—it assumes standard ERC-20 tokens where each transfer moves exactly the specified amount. It cannot recover incorrectly entered employee addresses or amounts; you must verify your list before sending. It cannot send to contracts that reject transfers. It is limited to ERC-20 tokens on zkSync Era only. It does not verify employee eligibility, employment status, or payroll approval—it simply creates streams for the addresses you provide. It does not handle tax withholding, benefits, or deductions. It does not support off-ramp to fiat. The tool does not simulate or estimate gas costs beyond the contract fee. Each execution is a separate transaction—there is no recurring or scheduled sending beyond the initial setup of the streams.

PLEASE NOTE

This tool only works on the zkSync Era network (EVM-compatible, chain 324). It requires a web3 wallet (e.g., MetaMask) connected via the injected wallet bridge. Always double-check your employee list, amounts, and pay frequency before signing. The tool is free to use; only blockchain transaction fees and the BotGentz contract fee apply. Ensure you are using the correct token address—using the wrong token could result in loss of funds. Once created, recurring streams will execute according to the frequency set—please verify the contract's behavior for exact execution timing.

=== END ===