Proof-of-Attendance Token Claim Tool

WHAT IT DOES

The Proof-of-Attendance Token Claim Tool enables event attendees to claim their POAP-style attendance tokens directly. It reads POAP token contract state, user address, wallet balance, and claim eligibility. The tool processes event metadata including event ID, event name, claim deadline, and proof data (Merkle proof). It verifies the attendee address, token URI, token metadata, claim status, and claimed supply. The tool supports claimToken for standard claims, claimWithProof for Merkle-proof-based claims, and claimBatch for claiming multiple tokens in a single transaction. It reads gas price, block timestamp, chain ID, transaction nonce, and approval state before execution.

HOW TO USE

Connect your wallet, select the target network, and enter the POAP token contract address. Provide the event ID or claim ID you wish to claim. Optionally enter an event name for reference. If the claim requires a Merkle proof, enter the proof as comma-separated hex values. You may also provide a custom token URI if the contract supports it. The tool will fetch contract state, verify your eligibility using canClaim(), and check if you have already claimed using hasClaimed(). Once confirmed, it submits the appropriate claim transaction—claimToken for standard claims, claimWithProof when a proof is provided, or claimBatch for multiple claims. The tool displays the event URI and contract owner before you sign.

TECHNICAL MECHANISM

Unlike generic minting tools, this claim executor is purpose-built for proof-based attendance token systems. It first reads the contract's owner() to verify the contract is active, then checks claim eligibility using canClaim() or verifyProof() functions. The tool validates the claim status via hasClaimed() to prevent duplicate claims. For Merkle proof claims, it parses user-provided hex values into bytes32[] format and passes them to claimWithProof(). For batch claims, it uses claimBatch() with arrays of event IDs and recipients. The tool reads eventURI() to display token metadata before claiming, giving users transparency about what they're claiming. It also checks isApprovedForAll() to ensure the contract can mint on behalf of the user if approval is required, though most claim functions are public and don't require approval. Gas costs are calculated using receipt.effectiveGasPrice for accurate post-EIP-1559 fee accounting, and the tool provides clear feedback on claim success or failure.

WHAT IT CANNOT SEE

This tool cannot verify that the claimant actually attended the event beyond what is proven by the on-chain proof. It cannot detect collusion or shared proofs across multiple addresses, nor can it validate the authenticity of event data off-chain. It also cannot verify that the claim proof hasn't been compromised. The tool cannot detect if the event is legitimate or if the claim contract has been deployed by a malicious actor. It also cannot verify that the token URI is accessible or that the metadata accurately reflects the event.

PLEASE NOTE

This tool supports EVM-compatible chains. Claims are typically gas-efficient and do not require approval, but ensure you have sufficient native balance for gas. The event ID must be correct—claiming the wrong event may result in a different token or a failed transaction. Merkle proofs must be provided exactly as generated by the claim distributor. This tool does not handle minting new tokens—it only claims pre-minted or mint-on-claim tokens. For batch minting, use the Proof-of-Attendance Token Batch Minter.