Batch distribution is an operational tool for a sender who already has a reviewed recipient list and a legitimate reason to transfer test assets. It is not evidence of a reward programme, token legitimacy, affiliation, or user eligibility. The Lester Labs tool validates CSV recipient addresses and display amounts locally, shows the complete send list, and uses only the immutable source-pinned replacement to split ERC-20 or zkLTC transfers into batches of up to 200 recipient entries. Each batch is a separate wallet transaction.
Local parsing and reports do not authorize a transaction. Distribution requires chain 4441, the exact replacement runtime and target, an exact token allowance, and a separate wallet review for every bounded batch. Future mainnet contracts require a separate review.
Go independently to lester-labs.com/airdrop. You can prepare and inspect a recipient list without approving a token or signing a distribution transaction.
Create a CSV file with two columns: recipient address and amount. address,amount 0x1234...abcd,1000 0x5678...wxyz,2500 Make sure addresses are valid Ethereum-format (42 characters starting with 0x). Enter normal display amounts, such as 1.5 or 1000; the tool reads the token decimals and converts each amount to base units exactly once when building the transaction.
Click Upload CSV and select your file. Parsing stays in your browser; the CSV is not uploaded to a Lester Labs server. The complete review table shows each address, amount, and validation status. Use its page controls to inspect every row that will be submitted, and fix any entries flagged in red before proceeding.
The tool shows the total amount, validated recipient count, batch count, network, contract readiness, and the wallet confirmations that will be requested. Review carefully: each confirmed batch is irreversible.
Never approve the legacy Disperse contract. Each replacement ERC-20 approval must name the exact source-pinned spender and batch total; every bounded token or native batch must be reviewed as a separate transaction on chain 4441.
Preserve the local review report, but do not treat it as a receipt. Once a replacement is active, begin with a small test batch, verify every recipient and amount independently, and preserve confirmed hashes until the sequence is complete.
Open each replacement transaction hash in an independently selected explorer or RPC. For ERC-20 distributions, verify Transfer logs and base-unit values against the report; for native zkLTC, verify transaction value and supported balance changes. Duplicate addresses remain separate recipient entries and are not unique-wallet counts.