Airdrops are one of the most effective token distribution mechanisms in crypto. They reward early users, bootstrap liquidity, and drive network effects. But doing them manually — copying addresses, sending one transfer at a time — does not scale. The Lester Labs Airdrop Tool lets you upload a CSV of recipient addresses and display amounts, inspect the complete validated send list, and distribute ERC-20 tokens or zkLTC in batches of up to 200 recipients. Each batch is a separate transaction. A failed batch reverts without changing that batch, while any earlier confirmed batches remain complete and are skipped when you resume.
The current Airdrop Tool targets LitVM testnet and test assets. Future mainnet contracts, addresses, limits, and fees must be verified separately before distributing assets with real value.
Go to lester-labs.com/airdrop. Connect your wallet and switch to LitVM network. Make sure you hold the tokens you want to distribute in your connected wallet.
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.
For ERC-20 tokens, approve the exact total first, then confirm each direct-distribution batch. Native zkLTC distributions request one confirmation per batch. The tool saves confirmed batch hashes and the next batch cursor on this device, so Retry resumes at the unconfirmed suffix instead of replaying successful sends.
For a large list, complete a smaller test batch first and verify its recipients and amounts on the explorer. Keep the browser storage for this site intact until every batch confirms; it contains the local resume cursor and confirmed transaction hashes.
After each transaction confirms, open its hash in the LitVM block explorer. For ERC-20 distributions, inspect the token contract’s Transfer logs and verify the recipients and base-unit values against your report. For native zkLTC, inspect the transaction value and internal balance changes supported by the explorer. The downloadable report maps every submitted recipient to its confirmed batch hash.