GitPOAP

• Name: GitPOAP
• URL: https://www.gitpoap.io/
• Category: contributor-recognition infrastructure / onchain credential layer / GitHub-to-wallet reputation bridge
• Summary: GitPOAP turns selected GitHub contributions into claimable wallet-visible credentials. Useful issuance plumbing and maintainer-curated contribution inventory, not a reputation engine.
• What it does:
  • Lets repo owners or project operators recognize contributors by minting POAP-based GitPOAPs for meaningful GitHub contributions
  • Detects contributions through configured patterns such as merged pull requests and, per the docs, can also award via maintainer tagging
  • Lets contributors claim GitPOAPs by signing into GitPOAP with their GitHub account, linking offchain contribution history to wallet-visible credentials
  • Exposes a public API for querying whether POAPs or POAP events are GitPOAPs, listing GitPOAP events, resolving GitPOAP holders by address, and looking up GitPOAPs by GitHub handle or repo
  • Provides repo-level badge surfaces so projects can display contributor-recognition counts in README-style contexts
  • Positions the issued credentials as the base layer for later reputation-based applications rather than as a closed-end badge product
• Key claims:
  • The docs describe GitPOAP as contributor recognition wired into GitHub, which is the right frame: it turns software-work events into portable credentials.
  • The real control surface is contribution-selection policy, not the NFT shell. Which actions count, which patterns are configured, and when maintainers override automation determine what later looks like reputation.
  • The public API matters because events, holders, repo mappings, and GitHub-handle lookups are queryable. That makes GitPOAP usable as downstream credential inventory rather than just a badge wall.
  • The sharper read is upstream issuance, not downstream scoring. GitPOAP makes contribution history legible, but it does not rank contributors or compute recursive reputation.
  • Practical authority sits with issuers and maintainers deciding what counts as meaningful work and how standardized those thresholds really are across repos and years.
• Whitepaper: No canonical standalone GitPOAP whitepaper or litepaper surfaced in this pass. The strongest primary materials were the official site, docs, API docs, and official docs repository; see ../whitepapers/gitpoap-primary-sources-2026-05-10.md.
• Sources:
  • https://www.gitpoap.io/
  • https://docs.gitpoap.io/
  • https://docs.gitpoap.io/api
  • https://github.com/gitpoap/gitpoap-docs
  • https://raw.githubusercontent.com/gitpoap/gitpoap-docs/main/docs/index.mdx
  • https://raw.githubusercontent.com/gitpoap/gitpoap-docs/main/docs/api.mdx

Internal linkages

• Best upward reads: sourcecred and openrank.

Control surface

• Power sits with issuer policy, GitHub-event selection rules, maintainer overrides, and the account-linking path that turns GitHub activity into wallet-visible credentials.

• Read it as contributor-credential issuance, not as a reputation engine.

• Last reviewed: 2026-06-12 UTC