POAP: Proof of Attendance Protocol — drops, collectors, and builders

POAP is short for Proof of Attendance Protocol. In plain terms: mint a digital collectible that says “this wallet was part of that moment” — conference hall, product launch, community call, city meetup — and let people keep it as a durable on-chain bookmark.

Site: poap.xyz. Issue: drops.poap.xyz. Collectors: collectors.poap.xyz. Builders: documentation.poap.tech. X: @poapxyz.

Public marketing cites multi‑million lifetime mints and tens of thousands of issuers — treat live counters on the homepage as the source of truth; the shape of the product matters more than the exact number on any given day.

Click to zoom

What a POAP is (technically)

Official materials describe POAPs as standard ERC-721 tokens minted on POAP smart contracts (contracts currently governed by POAP Inc for practical operation). Each token is non-fungible: unique serial, transferrable ownership, metadata that ties art + story to a Drop (the event or moment definition).

That is different from a generic “free NFT airdrop.” POAP’s brand promise is curation and quality guidelines for drops — the protocol is meant to stay associated with real shared history, not spam. Issuers still have to tell a clear story and distribute carefully; the platform is not a free mint factory for random JPEGs.

Protocol vs platform

• Protocol — the on-chain collectible + rules that make attendance mementos authentic, ownable, and hard to rewrite.
• Platform — apps and tooling: drop creation, claim flows, collector gallery, collections, mobile experience, and an ecosystem of integrations (wallets, gates, physical chips, votes).

POAP Inc builds core rails; third-party developers build experiences on top (gating, games, family graphs, kiosks, etc.). Featured ecosystem names on the builders page have included wallet and access products such as Rainbow, Trust, Tokenproof, and IYK — the list changes; the pattern is “POAP as identity/attendance signal.”

How it works: mint → drop → connect

1. Mint / design a Drop
   Story + artwork + supply + claim rules
   (drops.poap.xyz / issuer tools)

2. Drop / distribute
   QR codes, claim links, email reserve, kiosk, partner flows
   Collectors claim to a wallet (or email → later wallet)

3. Connect / unlock
   Holders use POAPs for chats, perks, gates, votes, reunions
   Collection becomes a portable history graph

Distribution methods are a product of their own (static QR, rotating codes, DM links, audio-event patterns, anti-farming challenges). Poor distribution is how drops get farmed; good distribution is how they stay meaningful. POAP’s help center and issuer guidelines are the operational handbook here.

Roles

• Issuers — events, brands, communities creating drops for milestones and gatherings.
• Collectors — wallets holding POAPs; scan/view on collectors site, browse poap.gallery, curate collections.
• Builders — apps that read POAP ownership, mint via API, attach “moments,” or gate experiences on holdership.

Builder surface

For integrations, start at documentation.poap.tech and the open SDK:

npm install @poap-xyz/poap-sdk
# or pnpm add / yarn add @poap-xyz/poap-sdk

The poap-xyz/poap-sdk README (developer preview — expect change) groups capabilities roughly as:

• POAPs — fetch tokens, search by collector or drop, mint sync/async, reserve to email, mint/index status
• Drops — create/update/fetch/search drop definitions
• Moments — attach richer media/story to a drop or specific POAP
• Providers / utils — API providers, auth headers, pagination helpers

Treat production use as “confirm current auth, base URLs, and preview status with POAP” — the SDK itself flags active development. For high-profile activations, POAP also offers services/partner support beyond self-serve drops.

Other open pieces in the org (illustrative): subgraph indexing, QR kiosk, family/common-POAP matching, sybil-resistant voting experiments — useful references when you need attendance graphs rather than a single claim page.

What builders usually do with POAP

• Event proof — IRL or online attendance without collecting emails as the only artifact
• Access gating — Discord roles, pages, merch, or allowlists keyed to drop IDs
• Community graph — “who else was there” (family-style products)
• Reputation light — not a credit score; a portable scrapbook that other apps can optionally trust
• Campaign memento — product launches and contributor thanks with craft, not spam

Solana builders: where POAP fits

POAP’s contracts and collector culture are EVM / ERC-721 centered, not a Solana-native mint standard. That does not make the product irrelevant to Solana teams:

• Multi-chain communities still run Ethereum-side POAP drops for global events while the product lives on Solana.
• Many users already have POAP-heavy wallets; gating “has conference POAP X” remains an off-Solana check via API.
• For on-Solana attendance, teams typically mint Metaplex Core / Token Metadata (or compressed) NFTs, or run custom claim programs — same social job, different ledger. See Metaplex Core and cNFTs when the requirement is “native SOL wallet only.”

Honest product choice: need the POAP brand + existing collector graph → use POAP. Need pure Solana UX and no EVM dependency → mint attendance on Solana and optionally mirror metadata.

Quality bar (why “just mint NFTs” fails)

POAP’s own issuer guidance stresses story, craft, and careful distribution. Farmed free mints erode the signal that gates and communities rely on. If you issue POAPs, budget time for art, copy, claim UX, and anti-farming — the token standard is the easy part.

Resources

• poap.xyz · About the protocol · Builders
• Create a drop · Documentation · poap-sdk
• Help: POAP Zendesk
• POAP on DevRels

Bottom line

POAP is the category-defining attendance collectible stack: ERC-721 mementos, curated drops, collector apps, and a builder API/SDK so communities can prove “you were there” without turning every event into a spreadsheet. Solana teams should use it when the POAP network is the point; use native Solana NFTs when the wallet and chain must stay Solana-only. Either way, the hard work is the story and the claim path — not the token standard.