Proof-of-Attendance Token Batch Minter

WHAT IT DOES

The Proof-of-Attendance Token Batch Minter enables event organizers to mint POAP-style attendance tokens for multiple attendees in a single batched transaction. It reads POAP token contract state, user address, wallet balance, and token minting eligibility. The tool processes event metadata including event ID, event name, event date, event location, and event organizers. It takes a list of attendee addresses, minting limits, batch minting limits, token URIs, and token metadata. The tool supports batchMintTokens for minting with custom URIs, batchMintWithEventData for embedding event information, and mintAndTransferBatch for combined mint and transfer operations. It reads gas price, block timestamp, chain ID, transaction nonce, approval state, and contract owner state before execution.

HOW TO USE

Connect your wallet, select the target network, and enter the POAP token contract address. Provide an event name or description for the tokens. List attendee addresses (one per line) who should receive tokens. Optionally provide a token URI base URL—the tool will append token IDs to generate unique metadata links for each attendee. The tool will fetch contract state, verify you are the contract owner or have permission to mint, and check approval for the batch sender contract. Once confirmed, it submits the appropriate batch mint transaction, creating and distributing all tokens in a single operation. The tool displays the fee, sender contract address, and sender owner before you sign.

TECHNICAL MECHANISM

Unlike manual minting that requires a transaction per attendee, this tool uses the shared BotGentz sender contract (BULKSEND registry) to batch mint all POAP tokens in one transaction. It first reads the token contract's owner() to verify authorization, then checks isApprovedForAll() to ensure the sender contract can mint on behalf of the user. If not approved, it prompts and executes a setApprovalForAll transaction. The tool reads the fee live from the sender contract via fee()—never using a hardcoded value—and validates that the user's native balance covers it before proceeding. It dynamically selects the optimal minting method: batchMintTokens when custom URIs are provided, batchMintWithEventData when event metadata is prioritized, or mintAndTransferBatch as a fallback. The tool handles URI generation by appending token indices to the base URI, and batch processes all attendees atomically. Gas costs are calculated using receipt.effectiveGasPrice for accurate post-EIP-1559 fee accounting.

WHAT IT CANNOT SEE

This tool cannot verify that attendees actually attended the event beyond what is provided as input. It cannot detect duplicate mints or sybil attacks, nor can it validate the authenticity of event data or attendee identities off-chain. The tool cannot verify that the token URIs are accessible or that the metadata accurately reflects the event. It also cannot detect if attendees are using multiple addresses to claim multiple tokens, or if the event actually occurred as described.

PLEASE NOTE

This tool supports EVM-compatible chains. The batch sender contract must be deployed on the target network; unsupported chains will prompt an error. Always verify the sender contract address and fee displayed before signing. Minting POAP tokens typically requires you to be the contract owner or have minter role permissions. The fee is paid in native currency and displayed in the review step. This tool does not handle token transfers after minting—tokens are minted directly to attendees. For transfer, use the Carbon Credit Batch Transfer Tool or Metaverse Land Parcel Batch Transfer Tool.