GitPOAP primary sources — 2026-05-10

What I reviewed

• Official site and docs:
  • https://www.gitpoap.io/
  • https://docs.gitpoap.io/
  • https://docs.gitpoap.io/api
• Official repository / source docs:
  • 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

Key takeaways from primary sources

• GitPOAP’s core mechanism is to convert offchain GitHub contributions into portable onchain POAP credentials that contributors can claim and display.
• The docs emphasize contribution recognition rather than tokenized ownership. The point is to make labor legible, queryable, and comparable across projects and time.
• The most important control surface is issuance policy: what counts as a meaningful contribution, which contribution patterns are recognized automatically, and where maintainers retain discretionary tagging power.
• The public API matters because it turns GitPOAP from a closed badge app into reusable infrastructure. Third parties can query GitPOAP events, holder addresses, GitHub-handle mappings, and repo-level contribution records.
• GitPOAP explicitly frames itself as foundational infrastructure for later reputation-based applications, not just as a commemorative collectible layer.
• The project’s own “verifiability / immutability / openness / composability / comparability” framing is analytically useful because it shows the intended replacement target: private or hard-to-audit contributor recognition systems.

Specific source signals worth retaining

• Overview docs: strongest articulation of why GitPOAP exists and how it bridges GitHub contribution history into onchain reputation primitives.
• API docs: best evidence that GitPOAP is infrastructure rather than only UI, since they expose holder, event, repo, and GitHub-user query surfaces.
• Landing page: concise confirmation that GitPOAP treats POAPs as a recognition rail for meaningful contributions, especially at the repo-owner distribution layer.
• Raw docs repo pages: useful for preserving wording around configurable contribution patterns, maintainer tagging, and the broader application-layer vision.

Why this entry belongs in the corpus

• It strengthens the contributor-legibility cluster with a distinct primitive: contribution-event credential issuance rather than peer scoring, attestation registries, or recursive ranking.
• It is a strong comparison class for SourceCred, Praise, OpenRank, Otterspace, and EAS because it isolates a simpler question: how does raw contribution history become a portable public credential in the first place?
• The reusable insight is that downstream reputation systems often depend on an upstream issuance layer. GitPOAP shows one way that open-source labor can be normalized into a queryable onchain artifact before any ranking or funding logic is applied.