pomp

Start by setting up a membership drop in pomp: connect the community wallet, pick a network, and choose how people qualify (allowlist, invite codes, on-chain criteria, or open claim). Upload brand assets or pick a template, then define traits that personalize each profile image—role, tenure, chapter, or achievement. Decide whether passes can be transferred or are bound to a wallet, set supply and expiry, and choose how fees are handled (paid by claimer or sponsor). Preview the collection, test the claim flow in a sandbox, and publish a hosted claim link. You can embed the widget on your site, share it in email, or pin it in Discord so new members can onboard themselves.

For members, claiming is quick: connect a wallet, verify eligibility, import an existing avatar or select a base image, and apply your organization’s overlay and traits. After minting, the token appears in the wallet alongside a downloadable PFP for socials. The same token can unlock benefits automatically: link your account to Discord to receive roles, sign once to open gated channels or documents, and present a QR code in-person to redeem perks. If the community supports codes or NFC cards, the token can bind to those too, so non-crypto users can participate without friction. Members see a simple dashboard: what they hold, where it works, and how to upgrade when they level up.

Integrators can plug POMP into existing tools. Use the API or SDK to check token ownership and traits before granting access to pages, cohorts, or premium features. Set webhooks to sync changes—when someone mints, renews, or loses status, their roles update across Discord, Slack, Telegram, and your app. For real-world events, spin up a verification station: staff scan a wallet QR or ENS name, confirm membership and tier, and log check-ins. Automate discounts by verifying at checkout, or route verifications through a backend if you want to hide logic. Analytics let you track claim rates, active holders, redemption counts, and which perks see the most use, so you can tweak your program based on data instead of guesses.

Ongoing operations are straightforward. Schedule renewals, issue upgrades for contributors, or revoke access when rules are broken. Handle lost wallets with a burn-and-reissue workflow that preserves history while keeping the collection clean. You can switch templates without reminting by updating layered art for future claims, or launch a new season with different traits. Follow least-data principles: you don’t need personal info—wallets and signatures are enough—and you can export holder lists for backup. POMP uses standard token formats so assets display broadly, and metadata is structured for audits and compliance reviews. Whether you’re running a DAO, a college club, a conference, a creator community, or a sports fan group, you can move from idea to a working membership system in an afternoon.