Batch Sender with On-Chain Memo Attachment (Zora)

WHAT IT DOES

Batch Sender with On-Chain Memo Attachment (Zora) is a specialized DeFi and developer tool that enables batch token distribution with attached memo messages stored permanently on-chain. Instead of simply transferring tokens to recipients, this tool allows you to attach a custom memo to each transfer—either a single global memo for all recipients or individual per-recipient memos. Each memo is stored on-chain via the sender contract, creating a permanent, immutable record of the purpose of each transfer. This is ideal for payroll distributions (attaching payment period details), grant programs (attaching project names or grant IDs), airdrop campaigns (attaching recipient notes or instructions), and any scenario where you need to provide context or reference information alongside token transfers. By storing memos on-chain, the tool ensures that the purpose of each transfer is permanently recorded and verifiable, eliminating the need for off-chain spreadsheets or external references that can be lost or disputed.

HOW TO USE

Connect your Web3 wallet to the Zora network. Enter the ERC-20 token contract address you wish to distribute. Enter a global memo message that will be attached to all transfers, or leave blank to use per-recipient memos. Optionally, enter per-recipient memos in the format "address, memo" with one entry per line—these override the global memo for specific recipients. Paste or upload 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 displays a preview showing each recipient, their token amount, and the memo that will be attached to their transfer. Review the sender contract address, fee, and contract owner for transparency. Click the send button, review the transaction in your wallet, and confirm. The tool executes a batched transfer with memos attached, storing each memo on-chain alongside the corresponding transfer.

MECHANISM: ON-CHAIN MEMO STORAGE WITH BATCH TRANSFER

The tool interacts with a specialized BotGentz sender contract deployed on Zora that supports a batchTransferERC20WithMemo function. This function accepts arrays of recipients, amounts, and memo strings, storing each memo on-chain as part of the transfer operation. The memos are typically stored as string data in the contract's event logs or as part of the transaction calldata, creating a permanent on-chain record. The tool builds the batch transaction by encoding each recipient's address, amount, and memo into the appropriate arrays. It reads the fee() function live from the sender contract, checks the sender's balance and allowance, approves the exact total, and executes the batch transfer. Each memo is stored on-chain, providing an immutable audit trail of the purpose of each transfer. This eliminates the need for off-chain record-keeping and ensures that the context of each payment is permanently available to auditors, recipients, and other stakeholders.

WHAT IT CANNOT SEE

This tool reads no on-chain data directly. It does not verify that recipient addresses are valid, that the sender has sufficient token balance, or that the token contract address provided is correct. It cannot guarantee that all transfers will succeed—if one transfer fails due to a blacklisted address, insufficient balance, or any other reason, the entire batch reverts. It cannot verify that the memo string is stored permanently or that the on-chain storage cost is predictable—storage costs may vary based on memo length and network conditions. It cannot guarantee that memos are readable by all recipients or that the memo data format is compatible with the sender contract. It cannot provide memo retrieval tools or indexing—recipients and auditors may need to query the blockchain directly to read memos. It cannot recover from failed transactions or generate reports for failed batches. It cannot ensure that memos are displayed in wallets or explorers.

PLEASE NOTE

This tool works exclusively on EVM-compatible chains and is specifically designed for the Zora network. It requires the user to have sufficient native ETH for gas 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. Memo storage consumes additional gas—longer memos will increase transaction costs. 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. On-chain memos are public and immutable—do not include sensitive information.