Zealy-Style Community Quest Reward Batch Distributor (Any L2)

WHAT IT DOES

Zealy-Style Community Quest Reward Batch Distributor (Any L2) enables community engagement platforms, Zealy-style quest programs, and ecosystem initiatives to distribute community quest rewards from a single treasury wallet to multiple participants across any L2 chain in one batch operation. Built specifically for Zealy-style community quest and engagement platforms, the tool simplifies reward distributions for completed community tasks, activities, and engagements across Arbitrum, Base, Optimism, zkSync, Polygon, BNB Chain, Mantle, Scroll, Linea, and other L2 networks. It scans the treasury wallet's token balance, validates the contract fee, and executes a multi-send transaction through the BotGentz sender contract with complete transparency. The tool allows participants to specify their chain ID, enabling per-chain filtering so that only recipients on the current chain are processed—users can maintain separate distribution lists or use the chain filter to deploy rewards chain-by-chain. The tool automatically detects the current chain, looks up the correct sender contract from the BULKSEND registry, and reads the live fee and owner from the contract before any transaction is signed. It supports all EVM chains with registered sender contracts, making it truly chain-agnostic for community quest operators. The tool includes duplicate address detection and transaction history awareness to support compliance workflows and community reward auditing.

HOW TO USE

Connect your wallet using the built-in wallet bridge. Enter participant wallets (one per line) with optional amounts and chain IDs in the format address,amount,chainId (e.g., 0xaaaa...,500.0,42161 for Arbitrum). Amounts and chain IDs are optional—leave amount blank to split equally among participants, and omit chain ID to use the current chain. Specify the reward token address and the treasury wallet address that holds the rewards. Click "preview rewards" to retrieve the treasury token balance, filter participants for the current chain, compute per-participant amounts, and verify that the total is covered. The review panel displays the treasury wallet balance, total rewards to distribute, contract fee, owner, duplicate detection results, and a table of participants with their chain IDs and allocated reward amounts. Review the summary and click "distribute rewards" to execute the batch transfer as a single atomic operation. The tool handles the approval process automatically, approving only the exact total amount needed for the distribution.

TECHNICAL MECHANISM

The batch distribution uses the BotGentz sender contracts (BULKSEND registry) specific to each chain and token standard. It calls multiSendToken with the recipient addresses and amounts arrays, sending the total reward token amount from the treasury wallet to all filtered participants (those matching the current chain) in one transaction. The contract fee is read live on each session using the fee() view function and is never hardcoded—this protects against owner fee adjustments that would otherwise cause revert due to underpayment. The tool performs an exact approval for the total token amount before calling multiSendToken, never using unlimited approvals. The total required token amount is checked against the treasury balance before submission. The tool includes duplicate detection by hashing recipient addresses and comparing them case-insensitively, providing a compliance-ready audit trail. The chain ID field allows per-chain deployments, enabling the same distribution list to be reused across multiple L2s. The batch is executed as a single atomic transaction—either all participants on the current chain receive their rewards or the entire transaction reverts, preventing partial distributions. All operations use ethers v5.7.2 with BigNumber for precise decimal arithmetic, and the fee is paid in native ETH (not the reward token), which the tool verifies the treasury wallet has before proceeding.

WHAT IT CANNOT SEE

This tool cannot verify off-chain ownership of recipient wallets, private key availability, or authorization to send rewards. It cannot prove that recipient addresses are legitimate Zealy-style community quest participants or that the sender has proper authority to distribute rewards. It cannot recover funds sent to wrong addresses. It cannot detect Sybil attacks or duplicate participant identities across L2s beyond address-level deduplication. It cannot access private wallet preferences or security policies. It cannot verify quest completion, community participation, or reward criteria off-chain. It cannot validate that recipients are active participants or meet program requirements across different L2 networks such as specific community tasks, engagement metrics, or participation thresholds. The chain ID filter is a convenience feature—the tool does not verify that participants actually completed community quests on the specified chain. The tool cannot verify Zealy-style credentials, community badges, or off-chain activity proofs such as Discord roles, Twitter follows, or other social engagement proofs. The duplicate detection feature only identifies exact address matches and does not detect variations or Sybil accounts. The tool does not validate participant wallet ownership or perform KYC/AML checks—you are responsible for ensuring that every participant wallet is correct and that you have the authority to send from the treasury wallet. Rewards sent to an incorrect or unreachable address are irrecoverable.

PLEASE NOTE

EVM chains only. Requires a wallet connection with BGWallet bridge. The sender contract must be registered in the BULKSEND registry for the current chain. Always verify the contract address, fee, owner, and participant list displayed in the review panel before signing any transaction. This is a free tool provided for Zealy-style community quest platforms and ecosystem programs—use at your own risk. The fee is paid in native ETH, so ensure the treasury wallet has sufficient native balance for gas and the contract fee. The chain ID field is optional—if omitted, participants are processed on the current connected chain. The duplicate detection feature is provided as a courtesy and does not guarantee complete Sybil resistance or compliance with regulatory requirements. For tokens with low decimal precision, amounts may round down during equal split distribution.