This app runs inside the BotSurf browser. Don't have it yet? Get the app or extension now!

Batch Sender with CSV Audit Trail Export (Any L2)

Developer Tools · All
0 installs · Verified BotGentz app
Launch App
Opens in BotSurf — nothing to install.
CategoryDeveloper Tools
PlatformAll
Pricing Free
Installs0
Download BotSurf to use — free
No account needed for free apps. Once BotSurf is open, find this app in Apps from the + menu.

About this app

WHAT IT DOES

Batch Sender with CSV Audit Trail Export is a specialized DeFi and developer tool that combines efficient batch token distribution with automated audit trail generation. Beyond executing a single batched transaction to multiple recipients, this tool reads the transaction receipt after confirmation and generates a downloadable CSV audit trail containing every recipient's address, amount sent, transaction hash, block number, chain name, and status. This is ideal for airdrop coordination, payroll processing, grant distributions, and any scenario where you need to provide verifiable proof of transfer for record-keeping, tax compliance, or community transparency. The tool eliminates the manual effort of cross-referencing wallet addresses with transaction data—after the batch sends, the audit trail is automatically structured and ready for export with one click, significantly reducing administrative overhead and ensuring accurate record-keeping.

HOW TO USE

Connect your Web3 wallet to your preferred L2 or L1 chain. Enter the ERC-20 token contract address you wish to distribute. Paste your list of recipients in the format "address, amount" with one entry per line—amounts are in human-readable token units. The tool parses the list and calculates the total tokens to be sent. Review the sender contract address, fee, and contract owner for transparency. Click the send batch button, review the transaction in your wallet, and confirm. The tool executes the batched transfer, waits for confirmation, and reads the transaction receipt. It then generates a structured CSV audit trail containing the recipient address, amount, transaction hash, block number, chain name, and a success status for each recipient. A download button appears, allowing you to save the CSV file for your records. The audit trail provides a complete, verifiable record of the distribution that can be shared with recipients, auditors, or compliance teams.

MECHANISM: POST-TRANSACTION RECEIPT PARSING FOR AUDIT GENERATION

The tool implements a two-phase workflow: batch execution followed by audit trail generation. First, it executes a standard batch transfer via the shared BotGentz sender contract—reading the fee() function live, checking balance and allowance, approving the exact total, and calling batchTransferERC20. After the transaction is confirmed, the tool retrieves the full transaction receipt using the provider's wait() method with confirmations. The receipt includes the transaction hash, block number, and effective gas price. The tool then constructs a CSV file by iterating through the original recipient list and pairing each address and amount with the transaction metadata. The CSV includes headers for recipient address, amount, transaction hash, block number, chain name, and status, with each recipient represented as a separate row. The transaction hash is the same for all recipients since the batch is atomic, providing a single verifiable reference for the entire distribution. The CSV export is generated client-side using Blob and downloaded via a temporary anchor element, requiring no server interaction and keeping all data local.

WHAT IT CANNOT SEE

This tool reads transaction receipts after execution but cannot verify recipient validity, sender balance, token contract correctness, transfer pausing, blacklisting, or gas fluctuations before the transaction. It cannot guarantee that all transfers will succeed—if the batch transaction fails at the contract level, no audit trail is generated and no partial transfers occur. It cannot account for L2-specific gas mechanics or fee structures that might affect transaction finality. It cannot detect if the token contract uses non-standard transfer mechanics that might affect transfer success. It cannot provide proof of delivery beyond the on-chain transaction data—recipients claiming non-receipt would need to verify their own balances. It cannot recover from failed transactions or generate an audit trail for failed batches. It cannot verify that the CSV export matches the actual on-chain state if the transaction is still pending or reorganized due to chain reorgs. The audit trail is generated from the receipt alone and does not independently verify each recipient's balance after the transfer.

PLEASE NOTE

This tool works exclusively on EVM-compatible chains and supports Ethereum L1, Optimism, Arbitrum, Base, Polygon, BNB Chain, Avalanche, and zkSync Era. It requires the user to have sufficient native gas token for the transaction and sufficient distribution token balance to cover the total amount sent plus the sender contract fee. The user is solely responsible for verifying the token contract address, recipient addresses, and amounts before signing. Always test with a small batch first to confirm the setup is correct. The CSV audit trail is generated for informational purposes and should be verified against on-chain data for critical use cases. The sender 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.

Similar Apps

Log in to BotGentz

Suggest an App

Tell us what you'd find useful — if we build it, we'll email you the moment it's ready.