10 Real Use Cases of Proof of Personhood in Crypto, DAOs, and AI

April 29, 2026 proof of personhood proof of humanity use cases verified human credentials

10 Real Use Cases of Proof of Personhood in Crypto, DAOs, and AI

Proof of personhood used to sound like a niche crypto idea.

It was discussed in DAO forums, identity research, airdrop design, and public goods funding. The basic question was simple but difficult:

How can an online system know that one account represents one real human?

That question is now much bigger than crypto.

AI can generate realistic accounts, comments, images, voices, messages, and digital behavior. Airdrop farmers can operate thousands of wallets. Bot networks can manipulate reviews, social feeds, polls, waitlists, and marketplaces. Online communities increasingly need a way to distinguish humans from automation without forcing everyone through traditional KYC.

That is why proof of personhood is becoming practical internet infrastructure.

Proof of personhood, also called proof of humanity, proof of human, or verified human credentials, helps users prove they are real, unique humans online. It can use biometrics, social proof, zero-knowledge credentials, wallet reputation, KYC-based attestations, or multi-signal systems like Human Passport.

This guide explains 10 real use cases of proof of personhood across crypto, DAOs, AI platforms, social apps, ticketing, marketplaces, and public goods.

The important point is not that every app needs identity verification.

The important point is that some online actions depend on real human participation.

When that is true, proof of personhood becomes useful.

Quick Answer: What Are the Main Use Cases of Proof of Personhood?

The most important proof-of-personhood use cases are:

Crypto airdrop Sybil resistance
DAO voting and fair governance
Quadratic funding and public goods
AI-platform human verification
Social network human badges
Ticketing and scarce-access fairness
Dating app safety and anti-scam verification
Marketplace trust and fake-review reduction
Gaming, quests, and reward abuse prevention
Private credentials for age, eligibility, and membership

These use cases share a common problem:

The system needs to know whether a participant is a real human, a unique human, or an eligible human — without necessarily knowing that person’s legal identity.

That distinction matters.

Proof of personhood is not the same as KYC. KYC asks who you are legally. Proof of personhood asks whether you are human, unique, or eligible for a specific action.

What Makes a Good Proof-of-Personhood Use Case?

Not every product needs proof of personhood.

A good use case usually has at least one of these traits:

One person should only get one claim.
One person should only get one vote.
Bots can distort the system.
Duplicate accounts create unfairness.
AI-generated activity is hard to detect.
Legal identity is too invasive.
Pseudonymous participation matters.
Rewards or access are scarce.
Trust depends on human participation.
The cost of abuse is high.

A weak use case usually looks like this:

The action is low-risk.
Basic rate limits are enough.
The app does not need uniqueness.
Verification would scare users away.
The benefit does not justify the privacy cost.
Anonymous access is important.
The platform cannot explain why verification is needed.

The best proof-of-personhood systems are proportional.

They ask for the minimum proof needed for the action.

Use Case 1: Crypto Airdrop Sybil Resistance

Crypto airdrops are one of the clearest use cases for proof of personhood.

Airdrops distribute tokens to users. But if rewards are based on wallets, one person can create many wallets and claim many times.

This is the airdrop Sybil problem.

A project may want to reward 100,000 real users. Instead, professional farmers create wallet clusters, perform minimum activity, complete quests, and capture a large share of the distribution.

Proof of personhood helps by letting projects ask:

Is this claimant a real human?
Is this human unique?
Has this human already claimed?
Is this wallet part of a farmed cluster?
Does this user have credible human credentials?

How projects use it

Airdrop teams may use:

Human Passport scores
World ID proofs
BrightID or Proof of Humanity credentials
Wallet clustering
Zero-knowledge nullifiers
KYC for regulated distributions
Social attestations
Manual appeals

A strong design might let all eligible wallets claim a base amount, while giving higher allocations to users with verified-human credentials.

Why it matters

Airdrops are expensive. If a large share of tokens goes to farmers, the project loses community trust and wastes token supply.

Proof of personhood does not eliminate farming, but it raises the cost and helps rewards reach more real users.

Best-fit proof methods

Human Passport for baseline scoring
World ID or biometric proof for stronger uniqueness
Wallet clustering for suspicious patterns
Nullifiers to prevent duplicate claims
Appeals for false positives

Use Case 2: DAO Voting and Fair Governance

DAOs have a voting problem.

Token-weighted voting gives more power to large holders. One-wallet-one-vote is easy to manipulate because one person can create many wallets. Reputation-based voting can be gamed if reputation is farmable.

Proof of personhood enables experiments with one-human-one-vote or human-weighted governance.

A DAO may want to know:

Is this voter a real person?
Is this voter unique?
Is this voter a member of the community?
Has this person already voted?
Can voting remain private while preventing double votes?

How DAOs can use it

Proof of personhood can support:

One-human-one-vote
Quadratic voting
Human-gated proposal creation
Verified-human quorum
Contributor-based governance
Anonymous voting with nullifiers
Anti-spam governance forums
Fairer grant committee participation

Why it matters

Governance legitimacy depends on trust.

If a vote can be manipulated by fake accounts, the DAO’s decisions become less credible.

Proof of personhood can make governance more human-aware. But it does not solve governance by itself. Verified humans can still vote badly, sell votes, follow bribery incentives, or coordinate attacks.

Identity is one governance primitive, not a full governance system.

Best-fit proof methods

Social proof for community membership
Human Passport for multi-signal verification
World ID or strong PoP for one-human uniqueness
Zero-knowledge nullifiers for private one-person voting
Contributor attestations for reputation

Use Case 3: Quadratic Funding and Public Goods

Quadratic funding is designed to reward projects that have broad community support.

Instead of only counting how much money is donated, quadratic funding gives extra weight to the number of unique contributors.

This creates a Sybil problem.

If one person splits donations across many fake accounts, they can make a project look more broadly supported than it really is.

Proof of personhood helps funding rounds verify that contributors are real and unique.

How funding platforms use it

Public goods platforms may use:

Human Passport
Donation pattern analysis
Wallet clustering
Community review
BrightID or Proof of Humanity
Attestations
MACI-style private voting tools
Nullifiers
Appeals

Why it matters

Quadratic funding only works if participation is credible.

Without Sybil resistance, matching funds can be manipulated by fake donors. With thoughtful proof-of-personhood design, matching can better reflect real community support.

Best-fit proof methods

Human Passport and Stamps
Social proof for community trust
Wallet clustering for donor patterns
ZK proofs for private eligibility
Nullifiers to prevent duplicate participation

Use Case 4: AI Platform Human Verification

AI platforms face a growing identity problem.

As AI agents become more capable, platforms may need to distinguish between:

Human users
Human-assisted AI users
AI agents acting for humans
Autonomous bots
Organizations
Duplicate accounts
Abuse networks

Proof of personhood can help AI platforms limit abuse without requiring legal identity for every user.

How AI platforms could use it

An AI platform might use proof of personhood to:

Limit free-tier abuse to one account per human
Reduce bot-created accounts
Verify human users for sensitive actions
Label human-backed AI agents
Distinguish automated agents from people
Prevent reward farming or credits abuse
Support human-only communities or feedback pools

Why it matters

AI makes fake human activity cheaper. That means human verification becomes more valuable.

But the solution should not be “upload your passport to every AI app.”

Proof of personhood can create a privacy-preserving middle layer: prove humanity without revealing legal identity.

Best-fit proof methods

World ID or strong proof of human for uniqueness
Human Passport or multi-signal credentials
Device and abuse detection for low-risk cases
ZK credentials for privacy
Nullifiers for one-account-per-human systems

Use Case 5: Social Network Human Badges

Social networks are being flooded with synthetic activity.

AI can create posts, replies, profile bios, images, comments, and engagement. Bot networks can manipulate trends, harass users, and distort public conversation.

Proof of personhood can support optional human verification.

A social network could let users prove:

This account is controlled by a real human.
This human has not created many verified accounts.
This post came from a verified human.
This poll response should count as human input.
This account is not an automated bot cluster.

How social apps can use it

Social platforms could offer:

Verified-human badges
Human-only comment filters
Polls weighted toward verified humans
Reduced bot amplification
Better moderation signals
Human-only community spaces
Pseudonymous human verification

Why it matters

The goal is not to end anonymity.

Many users need pseudonymity for safety, politics, health, work, whistleblowing, or personal reasons.

The better model is:

Verified human, not necessarily publicly identified.

A user should be able to prove they are human without revealing their legal name.

Best-fit proof methods

Anonymous credentials
Zero-knowledge proofs
Optional World ID or human credentials
Social attestations
Platform reputation
Anti-correlation design

Use Case 6: Ticketing and Scarce-Access Fairness

Ticketing is a classic bot problem.

When concert tickets, event passes, limited products, or exclusive drops go live, bots can buy inventory faster than humans.

Proof of personhood can help create fairer access.

A ticketing platform may not need to know a buyer’s full legal identity. It may only need to know that one person is not creating hundreds of accounts.

How ticketing platforms can use it

Proof of personhood can support:

One ticket allocation per verified human
Human-only presales
Bot-resistant queues
Fair waitlists
Reduced scalping
Human-verified purchase limits
Privacy-preserving access credentials

Why it matters

Scarce access is where fake accounts create obvious unfairness.

If a product, event, or opportunity is limited, proof of personhood helps enforce fairness without necessarily exposing legal identity.

Best-fit proof methods

One-human credentials
Nullifiers for event-specific purchase limits
Liveness checks for high-risk purchases
ZK proofs for privacy
Optional KYC only when legally required

Use Case 7: Dating App Safety and Anti-Scam Verification

Dating apps face fake profiles, romance scams, catfishing, bots, and increasingly realistic AI-generated personas.

AI can create photos, write messages, clone voices, and maintain conversations.

Proof of personhood can help dating apps verify that a profile is controlled by a real person.

How dating apps can use it

Dating platforms could use proof of personhood to show:

This profile is controlled by a real human.
This person passed liveness verification.
This account is not duplicated at scale.
This user has a privacy-preserving human credential.
This profile is not part of a known scam cluster.

Why it matters

Dating requires trust, but also privacy.

Users may not want their legal identity exposed to other users. They may not want public biometric information or address data connected to a dating profile.

The ideal badge is not:

Legal identity revealed

It is:

Verified human

That distinction is crucial.

Best-fit proof methods

Face liveness for profile authenticity
Optional stronger proof of human
Privacy-preserving badges
Anti-scam reputation systems
Device and behavior signals
Clear user consent

Use Case 8: Marketplace Trust and Fake Review Reduction

Marketplaces rely on trust.

But AI makes fake reviews, fake sellers, fake buyers, and fake support messages easier to generate.

Proof of personhood can help marketplaces distinguish real users from account farms.

How marketplaces can use it

Marketplaces may use verified-human credentials for:

Human-verified reviews
Seller verification
Buyer trust signals
One review per human
Fraud prevention
Fake account reduction
Reputation portability
Dispute resolution
Anti-review-farm systems

Why it matters

Reviews and reputation systems only work if the participants are credible.

A marketplace does not always need legal identity for every action. But it may need stronger proof when users are selling goods, making high-value purchases, leaving reviews, or creating repeated accounts.

Best-fit proof methods

Verified-human badges
Purchase verification
Reputation credentials
KYC for high-risk sellers
ZK proofs for eligibility
Anti-fraud scoring

Use Case 9: Gaming, Quests, and Reward Abuse Prevention

Games and quest platforms are heavily attacked by bots and farmers.

This is especially true when rewards have financial value.

Examples include:

Play-to-earn games
Onchain games
NFT drops
Quest platforms
Testnet campaigns
Token reward systems
Leaderboards
Tournaments
In-game economies

Proof of personhood can help limit abuse.

How games and quest platforms can use it

They may use human verification for:

One account per human tournaments
Human-only reward pools
Anti-bot leaderboards
Quest reward eligibility
Testnet incentive filtering
Fair NFT mints
Reduced farming
Better player reputation

Why it matters

If rewards can be farmed by scripts, they will be farmed by scripts.

Proof of personhood gives projects a way to separate casual play from high-reward participation.

The best design is risk-based:

No proof for casual play
Lightweight checks for suspicious behavior
Stronger proof for rewards, tournaments, and economies

Best-fit proof methods

Human Passport for quest platforms
Wallet clustering for farming patterns
Device and behavior detection
Optional proof of human for reward tiers
Nullifiers for one-claim rewards

Use Case 10: Private Credentials for Age, Eligibility, and Membership

Some of the most important proof-of-personhood use cases are not about proving identity. They are about proving eligibility.

A user may need to prove:

They are over a required age.
They are a member of a group.
They live in an eligible region.
They hold a valid credential.
They completed KYC with a trusted provider.
They are a verified human.
They have not already claimed.
They meet a score threshold.
They are allowed to access a community.

Zero-knowledge identity and verifiable credentials are especially useful here.

How private credentials work

A user receives a credential from an issuer.

Later, the user proves a specific fact from that credential without revealing the whole credential.

For example:

Prove over 18 without revealing exact birthdate.
Prove membership without revealing full identity.
Prove eligibility without showing all wallet history.
Prove KYC completion without uploading documents to every app.
Prove human verification without exposing biometric data.

Why it matters

This may be the most privacy-preserving direction for proof of personhood.

The future should not be one universal identity card. It should be a wallet of proofs, where users reveal only what each app actually needs.

Best-fit proof methods

Privado ID
zkPass
Reclaim Protocol
Holonym
Verifiable credentials
Anonymous credentials
Zero-knowledge proofs
Scoped nullifiers

Bonus Use Case: AI Agent Delegation

AI agents create a new category of identity.

An AI agent may act for:

A human
A company
A DAO
A marketplace seller
A software service
A bot network
Itself

Platforms may need to know whether an AI agent is authorized by a verified human.

Proof of personhood can support human-backed AI delegation.

For example:

A verified human authorizes one AI shopping agent.
A verified human allows an AI assistant to manage bookings.
A verified human uses an AI agent to participate in a workflow.
A platform limits one AI account per verified human.
A DAO allows AI-assisted drafting but human-only voting.

This does not mean banning AI agents.

It means making the relationship between humans and agents clearer.

Human credentials may become important for AI-agent accountability.

What These Use Cases Have in Common

These use cases look different, but they share the same identity pattern.

They need a way to answer one or more of these questions:

Is this participant human?
Is this participant unique?
Is this participant eligible?
Has this participant already acted?
Is this account a bot or AI agent?
Is this person a trusted community member?
Can this proof be checked without exposing legal identity?
Can this system reduce abuse without becoming surveillance?

Proof of personhood is useful when the answer matters.

It is not useful when the question does not need to be asked.

Which Proof Method Fits Which Use Case?

Different use cases need different proofs.

Use Case	Best-Fit Proof
Airdrops	Human Passport, World ID, wallet clustering, nullifiers
DAO voting	Social proof, contributor credentials, World ID, ZK voting
Public goods funding	Human Passport, social attestations, wallet clustering
AI platforms	Proof of human, nullifiers, abuse detection
Social networks	Optional anonymous human credentials
Ticketing	One-human purchase credentials, nullifiers
Dating apps	Liveness, verified-human badges, anti-scam signals
Marketplaces	Seller credentials, verified reviews, reputation
Gaming and quests	Human Passport, behavior analysis, reward-tier verification
Age or eligibility	ZK credentials, verifiable credentials, selective disclosure

The best systems are layered.

They do not rely on one proof everywhere.

When Proof of Personhood Is a Bad Fit

Proof of personhood should not be used everywhere.

It may be a bad fit when:

The action is low-risk.
Simple bot detection is enough.
Anonymous access is important.
The app cannot explain why verification is needed.
The system collects more data than necessary.
Users have no alternative.
There is no appeal process.
The verification provider is opaque.
The credential creates cross-app tracking.
The risk does not justify the friction.

A public website should not require proof of personhood just to read an article.

A casual community should not demand biometrics to join a conversation.

Verification should be proportional.

Privacy Principles for Real-World Use Cases

Every proof-of-personhood use case should follow privacy principles.

1. Minimum necessary proof

Ask only for the proof needed.

2. No legal identity unless required

Do not use KYC when human uniqueness is enough.

3. No raw biometric sharing with apps

Apps should receive proofs, not biometric data.

4. Scoped nullifiers

Prevent double use without cross-app tracking.

5. Selective disclosure

Reveal only the needed fact.

6. Multiple verification options

Do not force everyone through one issuer.

7. Pseudonymity support

Let users prove humanity without revealing legal names.

8. Appeals

Real users need recourse when wrongly rejected.

9. Transparency

Explain what data is collected, stored, and shared.

10. Proportionality

Verification should match the risk.

These principles are what separate respectful proof of personhood from surveillance.

The Future of Proof of Personhood Use Cases

Proof of personhood is likely to become more common as AI and automation continue to grow.

But the future should not be identity everywhere.

The future should be contextual proof.

A user may hold many credentials:

Proof of human
Proof of age
Proof of membership
Proof of uniqueness
Proof of KYC
Proof of contribution
Proof of reputation
Proof of eligibility
Proof of account ownership

Apps should request only the credential needed for the action.

A DAO vote may need one-human uniqueness.

A ticket sale may need one-human purchase proof.

A social network may offer optional human badges.

An AI platform may need human-backed account limits.

A regulated exchange may need KYC.

A public article should need no proof at all.

That is the right direction:

More trustworthy systems without unnecessary identity disclosure.

Summary: Proof of Personhood Use Cases

Proof of personhood is moving from theory to practice.

The biggest use cases are:

Crypto airdrop Sybil resistance
DAO voting and fair governance
Quadratic funding and public goods
AI-platform human verification
Social network human badges
Ticketing and scarce-access fairness
Dating app safety and anti-scam verification
Marketplace trust and fake-review reduction
Gaming, quests, and reward abuse prevention
Private credentials for age, eligibility, and membership

These use cases matter because the internet is increasingly filled with bots, AI agents, fake accounts, wallet farms, and synthetic activity.

But proof of personhood must be used carefully.

The goal is not to identify everyone everywhere.

The goal is to let people prove the minimum fact needed for a specific action.

That is why verified-human credentials may become one of the most important identity layers of the AI and crypto era.

FAQ: Proof of Personhood Use Cases

What is proof of personhood used for?

Proof of personhood is used to verify that an account, wallet, or credential belongs to a real human, often a unique human. Common use cases include airdrops, DAO voting, public goods funding, AI-platform abuse prevention, social trust, ticketing, dating apps, marketplaces, and gaming rewards.

Why do crypto airdrops need proof of personhood?

Crypto airdrops need proof of personhood because one person can create many wallets to claim more tokens than intended. Proof of personhood helps projects reduce Sybil attacks and distribute tokens more fairly.

Can proof of personhood help DAO voting?

Yes. Proof of personhood can support one-human-one-vote, quadratic voting, private voting with nullifiers, and human-gated proposal systems. It does not solve governance alone, but it can reduce fake-account manipulation.

How does proof of personhood help AI platforms?

AI platforms can use proof of personhood to distinguish verified humans from bots, duplicate accounts, and AI agents. It can help limit abuse, free-tier farming, and fake user activity without forcing full KYC.

Is proof of personhood the same as KYC?

No. KYC verifies legal identity. Proof of personhood verifies humanness, uniqueness, or eligibility. Many apps need proof that a user is human, not the user’s legal name.

Do all proof-of-personhood systems use biometrics?

No. Some use biometrics, but others use social proof, wallet reputation, zero-knowledge credentials, KYC-based attestations, Stamps, or community verification.

What is the best proof-of-personhood use case?

Airdrop Sybil resistance is one of the clearest current use cases. DAO voting, public goods funding, AI-platform verification, and ticketing are also strong use cases.

Should every app require proof of personhood?

No. Proof of personhood should be proportional. It is useful when bots, duplicate accounts, or scarce access create real problems. It should not be required for ordinary browsing or low-risk participation.

What are verified human credentials?

Verified human credentials are digital proofs showing that a user has passed some form of human verification. They can be used to prove humanity, uniqueness, eligibility, or non-duplication.

How can proof of personhood protect privacy?

Privacy-preserving systems can use zero-knowledge proofs, selective disclosure, anonymous credentials, and scoped nullifiers so users prove only what is needed without revealing legal identity or full personal data.

Suggested External References for Editorial Review

These are optional references for the editor/developer. They do not need to be shown in the published article unless you want a cited resources section.

World ID official documentation
Human Passport documentation
W3C Verifiable Credentials documentation
NIST Digital Identity Guidelines
BrightID documentation
Proof of Humanity materials
Privado ID documentation
zkPass documentation
Reclaim Protocol documentation
Holonym documentation
Gitcoin materials on quadratic funding and Sybil resistance
Research on AI agents, synthetic media, and bot detection

Optional FAQ Schema JSON-LD

Claude Code can add this to the page head if the blog template supports structured data.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is proof of personhood used for?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Proof of personhood is used to verify that an account, wallet, or credential belongs to a real human, often a unique human. Common use cases include airdrops, DAO voting, public goods funding, AI-platform abuse prevention, social trust, ticketing, dating apps, marketplaces, and gaming rewards."
      }
    },
    {
      "@type": "Question",
      "name": "Why do crypto airdrops need proof of personhood?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Crypto airdrops need proof of personhood because one person can create many wallets to claim more tokens than intended. Proof of personhood helps projects reduce Sybil attacks and distribute tokens more fairly."
      }
    },
    {
      "@type": "Question",
      "name": "Can proof of personhood help DAO voting?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. Proof of personhood can support one-human-one-vote, quadratic voting, private voting with nullifiers, and human-gated proposal systems. It does not solve governance alone, but it can reduce fake-account manipulation."
      }
    },
    {
      "@type": "Question",
      "name": "Is proof of personhood the same as KYC?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "No. KYC verifies legal identity. Proof of personhood verifies humanness, uniqueness, or eligibility. Many apps need proof that a user is human, not the user's legal name."
      }
    },
    {
      "@type": "Question",
      "name": "Should every app require proof of personhood?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "No. Proof of personhood should be proportional. It is useful when bots, duplicate accounts, or scarce access create real problems. It should not be required for ordinary browsing or low-risk participation."
      }
    }
  ]
}

Claude Code Implementation Notes

Create this as an individual blog article page.

Recommended file path options:

/content/blog/proof-of-personhood-use-cases.md

/src/content/blog/proof-of-personhood-use-cases.md

or, for a simple static Cloudflare Pages site:

/public/blog/proof-of-personhood-use-cases/index.html

Use the frontmatter fields for:

Blog index card
SEO title
Meta description
Canonical URL
Social preview title
Social preview description
Blog category
Reading time
Article schema

Preferred route:

/blog/proof-of-personhood-use-cases

END POST

⚠ Educational content only — not financial, medical, or legal advice. This article is published by ProofHuman, an independent editorial property. We are not affiliated with any protocol mentioned. Biometric verification has real privacy tradeoffs; verify regulations and your own comfort before participating.

Explore the directory

See the full directory of decentralized identity and proof-of-personhood protocols, categorized and filterable.

All Blog Posts Protocol Directory

10 Real Use Cases of Proof of Personhood in Crypto, DAOs, and AI

10 Real Use Cases of Proof of Personhood in Crypto, DAOs, and AI

Quick Answer: What Are the Main Use Cases of Proof of Personhood?

What Makes a Good Proof-of-Personhood Use Case?

Use Case 1: Crypto Airdrop Sybil Resistance

How projects use it

Why it matters

Best-fit proof methods

Use Case 2: DAO Voting and Fair Governance

How DAOs can use it

Why it matters

Best-fit proof methods

Use Case 3: Quadratic Funding and Public Goods

How funding platforms use it

Why it matters

Best-fit proof methods

Use Case 4: AI Platform Human Verification

How AI platforms could use it

Why it matters

Best-fit proof methods

Use Case 5: Social Network Human Badges

How social apps can use it

Why it matters

Best-fit proof methods

Use Case 6: Ticketing and Scarce-Access Fairness

How ticketing platforms can use it

Why it matters

Best-fit proof methods

Use Case 7: Dating App Safety and Anti-Scam Verification

How dating apps can use it

Why it matters

Best-fit proof methods

Use Case 8: Marketplace Trust and Fake Review Reduction

How marketplaces can use it

Why it matters

Best-fit proof methods

Use Case 9: Gaming, Quests, and Reward Abuse Prevention

How games and quest platforms can use it

Why it matters

Best-fit proof methods

Use Case 10: Private Credentials for Age, Eligibility, and Membership

How private credentials work

Why it matters

Best-fit proof methods

Bonus Use Case: AI Agent Delegation

What These Use Cases Have in Common

Which Proof Method Fits Which Use Case?

When Proof of Personhood Is a Bad Fit

Privacy Principles for Real-World Use Cases

1. Minimum necessary proof

2. No legal identity unless required

3. No raw biometric sharing with apps

4. Scoped nullifiers

5. Selective disclosure

6. Multiple verification options

7. Pseudonymity support

8. Appeals

9. Transparency

10. Proportionality

The Future of Proof of Personhood Use Cases

Summary: Proof of Personhood Use Cases

FAQ: Proof of Personhood Use Cases

What is proof of personhood used for?

Why do crypto airdrops need proof of personhood?

Can proof of personhood help DAO voting?

How does proof of personhood help AI platforms?

Is proof of personhood the same as KYC?

Do all proof-of-personhood systems use biometrics?

What is the best proof-of-personhood use case?

Should every app require proof of personhood?

What are verified human credentials?

How can proof of personhood protect privacy?

Suggested Internal Links

Suggested External References for Editorial Review

Optional FAQ Schema JSON-LD

Claude Code Implementation Notes

Explore the directory