Freelancer Payout Batch Sender (Ethereum L1)

WHAT IT DOES

This tool enables freelancer platforms, project managers, and hiring clients to pay multiple freelancers in a single batched transaction on Ethereum L1. Instead of sending 50 individual transactions and paying gas 50 times, you paste a list of freelancer addresses and payout amounts, and the BotGentz bulk-sender contract distributes everything in one go. It supports ERC-20 tokens, ERC-721 NFTs, and ERC-1155 multi-tokens, plus native ETH through the same interface. The tool reads on-chain balances, verifies that your wallet holds enough of each asset to cover the total payouts plus the contract's fee, and checks your transaction history to flag duplicates. It displays the contract's live fee, owner, and address before you sign anything so you know exactly what you are approving. This is designed specifically for freelancer payouts—covering platforms like Upwork, Fiverr, and Toptal, as well as direct client-freelancer arrangements for developers, designers, writers, and other gig workers—but it works for any bulk payment need. Whether you manage a large team of freelancers or work with a handful of contractors, this tool streamlines payroll operations.

HOW TO USE

Connect your EVM wallet via the BotGentz bridge. The tool automatically detects Ethereum L1 (chain ID 1) and looks up the correct bulk-sender contract from the BotGentz registry. Enter the token contract address, choose the token type (ERC-20, ERC-721, or ERC-1155), and paste your freelancer list as one address and payout amount per line. Optionally include project references for your records. Click "Parse list" to validate addresses and preview the total payouts. The review panel shows the number of freelancers, total payouts, token address, and the contract fee in ETH. When you click "Send batch," the tool performs a balance check per sender, not per row, ensuring the entire batch can complete before the first transfer. It then approves the sender contract for the exact total amount, not unlimited, and sends the batched transaction. Progress is shown throughout, including transaction confirmation. All state is in-memory and lost on reload—no data is stored. The tool handles weekly payroll runs, project milestone payments, and batch hiring scenarios with ease.

BULK SENDER CONTRACT MECHANISM

Unlike claim-based airdrops where each recipient pays their own gas to withdraw, this is a true bulk-send tool: the sender pays once for the entire batch. The BotGentz registry provides per-chain, per-standard contract addresses. The tool reads the fee() and owner() methods live from the contract each time—never hardcoding fees because the owner can change them. It uses the contract's sendERC20, sendERC721, and sendERC1155 methods, passing the recipient arrays, amounts or token IDs, and the required fee as msg.value. The fee covers the contract's operational costs and is separate from network gas. The tool checks balances comprehensively: native ETH balance must cover the fee, and ERC-20 balance must cover the total payouts. It walks through approvals sequentially and awaits each transaction, avoiding nonce conflicts that would occur if sends were fired concurrently. Post-EIP-1559, it uses receipt.effectiveGasPrice for accurate cost reporting rather than tx.gasPrice. For chains with different log limits, it chunks reads appropriately, halving ranges on failure. The contract owner is shown so you can verify the deployer before signing. The tool also reads token decimals dynamically and supports multi-token freelancer payments where different freelancers receive different assets. The batch size is limited only by block gas limits, suitable for freelancer teams with hundreds of members.

WHAT IT CANNOT SEE

This tool cannot verify off-chain freelancer work quality, project delivery, or payment eligibility. It cannot prove that recipient addresses are correct, that freelancers are legitimate, or that the same person is not receiving multiple payments via different identities. It cannot detect Sybil attacks or duplicate freelancer identities. It cannot access private freelancer payment preferences, contract terms, or work history. It cannot recover funds sent to wrong addresses—the blockchain is final. It cannot see past the current block, and it cannot enforce business rules beyond what is expressed in the payout list. It does not store any data; all state is in-memory and lost on reload. It cannot verify that freelancers actually completed the work, that deliverables were met, or that payment amounts match agreed-upon rates. It cannot automatically import timesheet data or calculate payments based on hourly rates. It cannot handle multi-currency payments, tax withholdings, or escrow arrangements beyond what you manually enter. It cannot verify that freelancers are eligible to work in your jurisdiction, that they have valid tax IDs, or that they are not on sanctions lists. It cannot enforce payment schedules, milestone approvals, or dispute resolution mechanisms. It cannot verify that the payment complies with applicable labor laws or tax regulations. It cannot handle partial payments, holdbacks, or release conditions beyond what you manually enter. It cannot verify that freelancers have met quality standards or that the project was completed to your satisfaction.

PLEASE NOTE

This tool works only on Ethereum L1 (chain ID 1) with the BotGentz bulk-sender contract deployed. Other EVM chains like Optimism, Arbitrum, Base, Polygon, BNB Chain, and others are supported by sibling tools—this specific tool is restricted to Ethereum mainnet. Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, and XRP are not supported. Always double-check the contract address displayed in the tool against the official BotGentz registry before sending. The tool is free and open-source; the contract fee is set by the owner and displayed live. Use at your own risk—you are responsible for verifying all addresses, payment amounts, and freelancer eligibility before signing any transaction. For businesses with frequent freelancer payments, consider using a multi-signature wallet and implementing a formal project completion review process before releasing payments to ensure quality standards are met.