Arbitrum One NFT Royalty Batch Distributor

WHAT IT DOES

This tool enables you to batch distribute ERC-20 royalty payments to NFT creators and royalty recipients based on ERC-2981 royalty information on Arbitrum One. It reads your connected wallet address, the chain ID (must be 42161), ERC-20 token balances and decimals, NFT contract addresses and token IDs, royalty data (including recipient addresses and percentages) from ERC-2981-compliant NFT contracts, and optional override recipients and percentages. The tool queries royaltyInfo(uint256 tokenId, uint256 salePrice) for each token ID, aggregates royalty recipients across multiple tokens (averaging percentages), and constructs a batch transfer to all royalty recipients in a single signed transaction. You configure the recurring distribution parameters—amount per token, frequency, and duration—and each execution is a separate batch transaction that you sign and send. The tool uses the shared BotGentz sender contract (0x956d760f8665358ea1a9f11b82913020e5479376) to perform the batch transfer, charging a small fee in ETH for each batch. You must approve the sender contract for the exact total amount of tokens you intend to distribute before the batch can be executed. On Arbitrum One, gas costs are significantly lower than Ethereum mainnet, making this tool highly cost-effective for frequent royalty distributions.

HOW TO USE

Connect your wallet (Arbitrum One only), enter the ERC-20 token contract address, the NFT contract address, token IDs (comma-separated), and optionally override recipients with custom percentages (one per line). The tool will query royaltyInfo for each token ID, aggregate recipients, normalize percentages to sum to 100%, show you the total number of recipients, total amount including the contract fee, and display your token balance. You first approve the sender contract to spend the total token amount, then you send the batch. Each batch is a single signed transaction; for recurring distributions, you repeat the process on your chosen schedule. The tool does not automate scheduling—you decide when to execute each batch.

TECHNICAL MECHANISM

The batch distribution is performed by calling sendERC20Batch(address token, address[] calldata recipients, uint256[] calldata amounts) on the BotGentz sender contract. Before constructing the batch, the tool queries the NFT contract's royaltyInfo function for each token ID using a fixed salePrice (e.g., 10000 basis points). It extracts the receiver address and royalty amount, converts to a percentage, and aggregates across all token IDs. If override recipients are provided, they replace the contract's royalty info. The tool then normalizes percentages to sum to 100% and calculates token amounts based on the total distribution amount (you can specify the total amount or use your wallet balance). The fee is read live from the contract's fee() function and must be paid in ETH as part of the transaction value. The tool checks your token balance and allowance against the total required (sum of amounts plus fee) before signing, preventing partial failures. All transfers are sequential within the contract, ensuring atomicity—if any transfer fails, the entire batch reverts. The tool does not cache fee or royalty data; it reads them fresh each time to avoid stale values.

WHAT IT CANNOT SEE

The tool cannot send native ETH or any token standard other than ERC-20. It cannot detect token tax or fee-on-transfer dynamics for non-standard tokens; if your token deducts a fee on each transfer, the amount received by royalty recipients will be less than specified. It cannot recover incorrectly entered recipient addresses—invalid addresses are simply skipped. It cannot send to contracts that reject transfers (e.g., blacklisted addresses). Royalty data must be queried from NFT contracts that support ERC-2981; if the contract does not implement the interface, the tool will fail. The tool does not validate that the royalty info is accurate or up-to-date—it reads what the contract returns at the time of execution. It does not automatically execute recurring distributions; each execution is a separate batch transaction that you manually trigger. The tool is limited to Arbitrum One only.

PLEASE NOTE

This tool works exclusively on Arbitrum One (chainId 42161). It does not support any other EVM chain. The BotGentz sender contract is hardcoded and verified; you can review its source code on Arbiscan. Always confirm the fee and contract address before signing any transaction. This tool is provided as-is; you are responsible for verifying recipient addresses and royalty amounts.