Skip to content
Universal Manifest

Proof-of-Personhood

This page describes a integration pattern for binding multi-provider proof-of-personhood credentials (World ID, Gitcoin Passport, BrightID) to Universal Manifest subjects.

Proof of Personhood Integration

Boundary: normative vs non-normative

Section titled “Boundary: normative vs non-normative”
  • Normative contract: Specification and Conformance
  • Non-normative guidance: this page

All provider-specific claims, pointer names, and consent keys on this page are explicitly non-normative.

What you implement

Section titled “What you implement”

Inputs

Section titled “Inputs”
  • A valid Universal Manifest with a stable subject identifier
  • One or more personhood verification results from supported providers
  • Consumer-side trust policy defining which providers are accepted

Outputs

Section titled “Outputs”
  • Manifest claims entries carrying provider-specific personhood attestations
  • Deterministic handling for expired or unrecognized personhood claims
  • Consent-gated disclosure of verification status to third parties

Minimum behaviors

Section titled “Minimum behaviors”
  • Represent personhood credentials as claim extensions
  • Ignore unknown personhood claim types safely
  • Enforce consent before disclosing verification status
  • Do not treat expired attestations as current proof
  • Support multi-provider coexistence without namespace collision

Provider overview

Section titled “Provider overview”
  • World ID — Biometric proof of unique personhood (iris-scan-backed binary attestation)
  • Gitcoin Passport — Composite Sybil-resistance score aggregating stamps from multiple identity sources
  • BrightID — Social-graph-based unique-human verification through peer connections

These providers are complementary. Consumers select which providers they trust; no single provider is required.

Suggested pointer names

Section titled “Suggested pointer names”
  • personhood.worldId.verification
  • personhood.gitcoinPassport.score
  • personhood.brightId.verification
Section titled “Suggested consent keys”
  • personhood.shareVerification
  • personhood.crossPlatformLink

Reference fixtures

Section titled “Reference fixtures”

These examples are implementation aids and should not be treated as extra conformance requirements.

Next

Section titled “Next”