Reward Distribution Tool

WHAT IT DOES

Reward Distribution Tool gives DeFi protocols, DAOs, and project teams a powerful way to batch distribute token rewards to multiple recipients in a single transaction. It reads reward distribution contract state, recipient lists, reward amounts per recipient, distribution schedules, total rewards allocated, claimed amounts, and token balances. You can distribute ERC-20, ERC-721, and ERC-1155 tokens to hundreds of recipients at once, with live fee calculation from the shared BotGentz sender contract. The tool shows you the sender contract address, owner, current fee, total distribution amount, total with fee, and your token balance before you sign—so you always know exactly what you're approving.

HOW TO USE

Connect your EVM wallet. Enter the token address you want to distribute. Select the token standard (ERC-20, ERC-721, or ERC-1155). Enter recipients one per line in the format: address,amount (e.g., 0x123...,100.5). For ERC-721, the amount is the token ID. For ERC-1155, the format is address,id,amount. Use "Preview distribution" to see the sender contract address, owner, fee, total amount, total with fee, and your token balance. The tool checks if your balance covers the total plus fee. Click "Distribute rewards" to approve the sender contract for the exact total amount and send the distribution transaction. Each action generates a transaction you review and sign in your wallet. The tool uses the shared BotGentz sender contracts, so you don't need to deploy your own distribution contract.

TECHNICAL APPROACH

This tool uses the shared BotGentz bulk sender contracts deployed across multiple EVM chains. It looks up the sender contract address by chain ID and token standard from the embedded BULKSEND registry—using separate addresses for ERC-20, ERC-721, and ERC-1155 on networks like BNB Chain and Polygon where the contracts differ per standard. The tool reads the live fee by calling fee() on the sender contract every time, never hardcoding a stale fee. It checks token balance and computes the total distribution amount plus fee per sender, then approves the sender contract for the exact total (not unlimited). For ERC-20, it calls distributeERC20(); for ERC-721, distributeERC721() with token IDs; for ERC-1155, distributeERC1155() with IDs and amounts. All RPC calls are wrapped in a robust error handler that extracts the actual failure reason from Ethers error objects, digging three levels deep to avoid showing "[object Object]" when a transaction reverts. Transaction costing uses receipt.effectiveGasPrice post-EIP-1559 rather than tx.gasPrice, which overstates actual spend.

WHAT IT CANNOT SEE

This tool cannot verify off-chain recipient eligibility or guarantee that recipients will claim their rewards. It cannot detect whether recipients are active or whether they will accept the tokens. It cannot simulate execution or test whether the distribution will succeed before sending. It cannot see pending distribution operations that are not yet broadcast to the public mempool. It cannot detect if the token contract has transfer restrictions or blacklists that would prevent distribution. The tool facilitates batch distributions, but it does not guarantee that all transfers will succeed—individual transfers may fail if recipient addresses are invalid or token contracts have restrictions.

PLEASE NOTE

This tool supports EVM‑compatible chains only where BotGentz sender contracts are deployed: Ethereum, Goerli, Sepolia, Optimism, Cronos, BNB Chain, Polygon, Fantom, zkSync Era, Base, Arbitrum, Avalanche, and Linea. Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, and XRP are not supported. This is a read‑write tool that requires signing transactions—always verify the sender contract address, token address, recipients, and amounts before approving. The tool is free and open under the BotGentz PLAYBOOK‑C specification.