Gitcoin Passport Explained: Sybil Resistance for Crypto Airdrops and Web3 Apps
Gitcoin Passport Explained: Sybil Resistance for Crypto Airdrops and Web3 Apps
Gitcoin Passport became one of the most important identity tools in Web3 because it solved a very practical problem:
How can crypto apps tell the difference between real users and Sybil attackers without forcing everyone through traditional KYC?
That problem shows up everywhere in crypto.
Airdrops get farmed by thousands of wallets. DAO votes can be manipulated. Grant programs can be attacked by fake accounts. Waitlists fill with bots. Community rewards go to professional Sybil farmers instead of real users.
Gitcoin Passport offered a different model. Instead of asking every user for a passport, driver’s license, or legal identity, it let users collect identity credentials called Stamps. Those Stamps could come from Web2 accounts, Web3 activity, onchain history, attestations, and other signals. Together, they helped produce a score showing that a wallet was more likely to belong to a real, unique human.
Today, Gitcoin Passport is known as Human Passport. Many users still search for “Gitcoin Passport,” so this guide uses both names.
This article explains what Gitcoin Passport / Human Passport is, how Stamps work, what the Unique Humanity Score means, how Passport helps with crypto airdrops and Web3 apps, and what privacy and accuracy tradeoffs builders should understand.
Quick Answer: What Is Gitcoin Passport?
Gitcoin Passport, now Human Passport, is an identity verification and Sybil-resistance protocol that helps Web3 apps identify real users and reduce bots, fake wallets, and duplicate accounts.
The core idea is simple:
- A user connects a wallet.
- The user verifies different signals, called Stamps.
- These Stamps may come from social accounts, Web3 activity, attestations, identity checks, or other credentials.
- The system uses those Stamps to generate a Unique Humanity Score or similar trust signal.
- Apps can use that score or credential to decide whether a wallet is likely to represent a real human.
Human Passport’s official docs describe it as an identity verification application and Sybil resistance protocol that developers can use to protect communities and enable more trustworthy participation. Its core product is Passport Stamps, which verify a user’s identity and trustworthiness.
In plain English:
Passport helps apps ask, “Is this wallet probably controlled by a real human?”
It does not always answer that question perfectly. But it gives builders a practical way to reduce abuse without defaulting to full KYC.
Why Gitcoin Passport Became Important
Gitcoin Passport became important because Web3 has a structural identity problem.
Crypto wallets are powerful because they are easy to create. A person does not need permission to make a wallet. That openness is part of what makes crypto interesting.
But it also creates a problem:
A wallet is not the same thing as a human.
One person can create 10 wallets, 100 wallets, or 10,000 wallets. If a protocol rewards wallets instead of people, attackers can multiply their rewards by multiplying wallets.
This affects:
- Token airdrops
- Testnet incentives
- Governance voting
- Grant programs
- Community rewards
- Allowlist access
- NFT mints
- Quests and campaigns
- Waitlists
- Reputation systems
- Onchain social networks
- Public goods funding
In traditional finance, the answer is often KYC. But many crypto communities do not want to collect legal identities for every use case. They want pseudonymous participation, open access, and privacy.
Gitcoin Passport became popular because it fit that middle ground.
It was not full KYC. It was not just CAPTCHA. It was a reusable identity layer for Web3 trust signals.
What Is a Sybil Attack?
To understand Passport, you need to understand the Sybil problem.
A Sybil attack happens when one person or group creates many fake identities to gain more influence, rewards, or access than they should have.
In Web3, a Sybil attacker might:
- Create hundreds of wallets to farm an airdrop.
- Split donations across fake accounts to manipulate quadratic funding.
- Use bot accounts to complete quests.
- Create fake community members to qualify for rewards.
- Register many wallets for an allowlist.
- Manipulate DAO votes.
- Create fake social proof around a project.
- Farm testnet incentives before a token launch.
The word “Sybil” comes from the idea of one actor pretending to be many identities.
Crypto makes Sybil attacks easier because wallets are cheap and pseudonymous. AI and automation make the problem worse because attackers can generate activity at scale.
Passport is one answer to this problem.
Gitcoin Passport vs Human Passport: What Changed?
The name changed, but the search demand has not.
Many people still know the product as Gitcoin Passport. The newer name is Human Passport. It is part of the broader human.tech ecosystem and is focused on proof of humanity, Sybil resistance, and identity verification for Web3 and beyond.
For SEO and user clarity, a good article should mention both names:
- Gitcoin Passport
- Human Passport
- Passport.xyz
- Passport Stamps
- Unique Humanity Score
- Proof of Humanity
- Sybil resistance
The practical takeaway:
If someone says Gitcoin Passport, they are usually referring to what is now Human Passport.
For a directory site like Proof Human, the entry should likely be listed under the current name, Human Passport, with “formerly Gitcoin Passport” in the description.
How Gitcoin Passport Works
Gitcoin Passport / Human Passport works by aggregating identity signals.
Instead of relying on one document, one biometric, or one centralized database, Passport lets users collect multiple proofs that suggest they are real people with meaningful digital history.
A simplified flow looks like this:
- The user connects a crypto wallet.
- The user opens the Passport app.
- The user verifies different accounts, credentials, or activities.
- Each verification creates a Stamp.
- Stamps contribute to the user’s humanity or trust score.
- Apps query Passport data or use Passport integrations.
- The app decides whether the user meets its threshold.
For example, a user may verify that they have:
- A GitHub account
- A Google account
- A Discord account
- An ENS name
- Onchain transaction history
- Gitcoin activity
- POAPs
- BrightID or other identity credentials
- Social account history
- Other Web3 attestations
The exact available Stamps can change over time. The important concept is that Passport uses multiple signals rather than one identity document.
That makes it flexible. It also means Passport is probabilistic. A high score suggests a wallet is more likely to be human, but it is not absolute proof.
What Are Passport Stamps?
Passport Stamps are verifiable credentials or signals that support a user’s identity, reputation, or humanity score.
A Stamp can represent a verified relationship, action, account, or credential. Each Stamp adds evidence that a wallet belongs to a real person rather than a freshly created Sybil account.
Examples of Stamp categories may include:
- Web2 account verifications
- Web3 wallet activity
- Social account credentials
- Onchain participation
- DAO or community membership
- Gitcoin donation history
- ENS ownership
- POAP attendance
- Identity provider credentials
- Other proof-of-personhood signals
The Stamp model is useful because it does not force every user into the same verification path. A user can build credibility from different sources.
For example:
- A developer may have GitHub and onchain history.
- A community member may have Discord and POAP credentials.
- A DeFi user may have transaction history.
- A grants donor may have Gitcoin activity.
- A privacy-conscious user may prefer certain attestations over social account linking.
This makes Passport more pluralistic than a single biometric or government ID check.
What Is the Unique Humanity Score?
The Unique Humanity Score is a trust or personhood score based on a user’s Passport signals.
The idea is to estimate whether a wallet is likely controlled by a real, unique human.
The score can help apps decide whether to:
- Allow a user to claim an airdrop.
- Count a vote.
- Let a user join a gated community.
- Prioritize a grant donation.
- Reduce spam.
- Access a waitlist.
- Complete a quest.
- Receive rewards.
- Participate in a campaign.
The score is not the same as legal identity. It is not a passport in the government sense. It is a Web3 trust signal.
A higher score generally means the wallet has more credible human-related evidence. A lower score may mean the wallet is new, thin, suspicious, or simply private.
That last point matters.
A low score does not always mean a user is a bot. It may mean the user is new, privacy-conscious, underbanked, inactive on supported platforms, or unwilling to connect certain accounts.
That is why builders should avoid treating the score as perfect truth.
Gitcoin Passport Is Not KYC
Gitcoin Passport is often misunderstood as a KYC tool.
It is not traditional KYC.
KYC stands for Know Your Customer. A KYC process usually verifies legal identity using a government ID, legal name, date of birth, address, selfie, sanctions screening, and other compliance checks.
Passport is different.
Passport asks:
“Does this wallet have signals that suggest it belongs to a real, unique human?”
KYC asks:
“Who is this person legally?”
That difference matters.
A crypto exchange may need KYC because it handles regulated financial services. A grants round, quest platform, DAO vote, or airdrop may not need to know a user’s legal name. It may only need to reduce fake-wallet abuse.
Passport can help with the second use case.
It does not automatically satisfy KYC obligations where legal identity verification is required.
Gitcoin Passport vs World ID
Gitcoin Passport / Human Passport and World ID are both proof-of-humanity tools, but they use different models.
World ID is best known for biometric proof of human through the Orb, which verifies uniqueness using iris scanning.
Human Passport is better understood as a multi-signal identity and Sybil-resistance layer. It uses Stamps, scores, onchain history, offchain signals, and other credentials to evaluate humanity or trust.
A simplified comparison:
| Feature | Human Passport | World ID |
|---|---|---|
| Former name | Gitcoin Passport | Worldcoin identity layer |
| Core model | Multi-signal Stamps and score | Biometric proof of human |
| Main question | Is this wallet likely human? | Is this person a unique human? |
| Strongest signal | Multiple credentials and activity | Orb-based iris uniqueness |
| User friction | Moderate | Higher for Orb verification |
| Privacy concern | Account linking and scoring | Biometric enrollment |
| Best for | Airdrops, grants, Web3 communities | Strong uniqueness, one-human claims |
| Output | Score / credential / verification | Proof-of-human credential |
These tools are not necessarily competitors in every case. Some apps may use both. For example, an airdrop could require a minimum Passport score and allow World ID as a strong additional proof.
Gitcoin Passport vs CAPTCHA
CAPTCHA is designed to stop automated bots during a specific interaction.
Passport is designed to evaluate whether a wallet has credible human identity signals over time.
A CAPTCHA asks:
“Is a human present right now?”
Passport asks:
“Does this wallet look like it belongs to a real person?”
CAPTCHA can be useful for low-risk forms and spam prevention. But it does not solve the Web3 wallet problem. A Sybil farmer can solve CAPTCHAs across many wallets. CAPTCHA farms and AI tools can also bypass many challenges.
Passport is more useful for:
- Airdrop eligibility
- Community access
- Quest filtering
- Wallet scoring
- Grant protection
- DAO participation
- Reward distribution
It is heavier than CAPTCHA but lighter than traditional KYC.
Gitcoin Passport vs Wallet Reputation
Wallet reputation systems analyze onchain behavior.
They may look at:
- Transaction history
- Contract interactions
- Wallet age
- Gas spent
- Token balances
- NFT holdings
- Bridge usage
- DeFi activity
- Network diversity
- Known Sybil patterns
- Cluster analysis
Human Passport overlaps with wallet reputation but is broader.
It can include onchain signals, but it can also include offchain Stamps, social credentials, attestations, and other identity proofs.
Wallet reputation is useful, but it can be gamed. Attackers can farm onchain activity if they know what signals matter. New users may also be penalized for having little history.
Passport’s advantage is that it can combine multiple types of evidence.
Its disadvantage is that more signals can create more complexity, opacity, and privacy tradeoffs.
How Passport Helps Airdrops
Airdrops are one of the clearest use cases for Passport.
A token project may want to reward real users. But if eligibility is based only on wallet activity, professional farmers can create many wallets and simulate usage.
Passport can help an airdrop team:
- Require a minimum humanity score.
- Filter obvious Sybil wallets.
- Weight rewards toward credible users.
- Reduce duplicate claims.
- Combine wallet activity with personhood signals.
- Protect community rewards from bots.
- Make the distribution feel fairer.
For example, a project might say:
- Wallets must have used the protocol before a snapshot date.
- Wallets must meet a minimum Passport score.
- Wallets flagged as likely Sybil clusters receive less or nothing.
- Users can appeal or provide additional proof.
That kind of layered approach is often better than a single hard rule.
Airdrops create strong financial incentives, so no system is perfect. But Passport can raise the cost of fake-user farming.
How Passport Helps DAOs
DAOs often struggle with voting design.
Token-weighted voting can concentrate power in wealthy wallets. One-wallet-one-vote is easy to manipulate. Reputation-based voting is hard to bootstrap.
Passport can support more human-aware governance.
A DAO might use Passport to:
- Restrict voting to wallets above a humanity threshold.
- Weight votes based on human credibility.
- Prevent newly created Sybil wallets from joining governance attacks.
- Support one-human-one-vote experiments.
- Gate proposal creation.
- Reduce spam in governance forums.
- Protect community grants.
This does not mean Passport solves DAO governance. A verified human can still vote badly, sell votes, coordinate attacks, or follow bribery incentives.
But Passport can reduce one basic failure mode: one person pretending to be many voters.
How Passport Helps Grants and Public Goods Funding
Gitcoin became closely associated with public goods funding and quadratic funding. That is one reason Passport became so important.
Quadratic funding rewards projects based on the number of contributors, not only the amount donated. This makes it more democratic, but also more vulnerable to Sybil attacks.
If one person can create many fake donor accounts, they can manipulate matching funds.
Passport helps reduce that risk by giving grant systems a way to evaluate whether donors are likely to be real humans.
A grants platform may use Passport to:
- Verify donor humanity.
- Weight donations by trust score.
- Reduce matching for suspicious accounts.
- Detect clusters of related wallets.
- Require stronger proof for high-impact participation.
- Preserve pseudonymity while fighting abuse.
This is one of the most natural use cases for proof of humanity.
How Passport Helps Web3 Apps and Communities
Passport is not only for airdrops and grants.
Web3 apps can use it anywhere they need trustworthy participation.
Examples include:
Quest platforms
Quest platforms can require Passport verification before users earn rewards, reducing bot farming.
NFT allowlists
Projects can prioritize wallets with stronger human signals.
Community gating
Discord, Telegram, or token-gated communities can use Passport to reduce spam and fake members.
DeFi campaigns
DeFi protocols can protect incentive programs from farmers who create many wallets.
Testnets
Projects can identify real testers and reduce low-quality farming.
Onchain games
Games can reduce multi-account abuse and bot activity.
Social apps
Decentralized social networks can label or prioritize verified-human accounts.
Marketplaces
Marketplaces can use Passport signals to reduce fake reviews, spam, and fraudulent sellers.
The key is not that Passport makes every user trustworthy. It helps filter the lowest-quality and most suspicious identities.
Privacy: What Users Should Understand
Passport can be more privacy-preserving than KYC, but it still has privacy tradeoffs.
When users collect Stamps, they may connect accounts, wallets, or credentials. Depending on the Stamp and implementation, this could reveal relationships between identities.
For example, a user might link:
- A wallet
- A GitHub account
- A social account
- An email-related credential
- A POAP history
- DAO memberships
- Onchain activity
Even if the system minimizes personal data, linking signals can create a richer identity graph.
Human Passport’s public materials emphasize privacy-by-design and minimal personal data handling. But users should still understand that any multi-signal identity system can create correlation risk.
Privacy-conscious users should ask:
- Which Stamps am I collecting?
- What accounts am I linking?
- What does each Stamp reveal?
- Can apps see individual Stamps or only a score?
- Is my score tied to a wallet?
- Can my wallet activity be linked to my social accounts?
- Can I remove or refresh Stamps?
- What data is stored?
- What data is hashed or minimized?
- What happens if I use the same wallet everywhere?
The safest mental model is:
Passport is lighter than KYC, but it is still identity infrastructure. Treat it carefully.
Privacy: What Builders Should Understand
Builders should also be careful when integrating Passport.
The goal should be to reduce abuse while collecting as little information as possible.
Good builder questions include:
- Do we need individual Stamp details, or is a score enough?
- What threshold is appropriate for our use case?
- Are we excluding legitimate new users?
- Can users appeal if they fail?
- Are we storing Passport data unnecessarily?
- Are we combining Passport data with other tracking signals?
- Are we transparent about how the score affects eligibility?
- Can attackers farm the specific Stamps we require?
- Do we need a fallback verification method?
- Are we using Passport as if it were KYC?
A bad implementation can turn a useful human signal into a confusing gatekeeping system.
A good implementation should be proportional, transparent, and privacy-aware.
Accuracy and Limitations
Passport is useful, but it is not perfect.
It can produce false positives and false negatives.
False positives
A false positive happens when an attacker looks legitimate. For example, a Sybil farmer may collect enough Stamps across many wallets to pass a threshold.
False negatives
A false negative happens when a legitimate user looks suspicious or under-verified. For example, a real user may be new to crypto, privacy-conscious, or unwilling to connect social accounts.
Both errors matter.
If a threshold is too low, attackers pass. If it is too high, real users are excluded.
This is why many projects should avoid using Passport as a single binary gate. A better approach may be:
- Use Passport as one signal.
- Combine it with app-specific activity.
- Offer appeals.
- Provide multiple verification paths.
- Adjust thresholds based on risk.
- Monitor abuse after launch.
Passport improves Sybil resistance. It does not eliminate the need for judgment.
Can Passport Be Farmed?
Yes, to some extent.
Any system that creates financial value will be attacked.
If an airdrop requires certain Stamps, attackers may try to create or buy those Stamps. If a score threshold becomes standard, farmers may optimize for that threshold. If account linking creates value, black markets may develop.
This does not mean Passport is useless. It means Passport raises attacker costs rather than making attacks impossible.
Good defenses include:
- Changing signals over time.
- Using model-based detection.
- Combining onchain and offchain data.
- Looking for wallet clusters.
- Requiring higher proof for higher rewards.
- Avoiding public over-disclosure of exact scoring logic.
- Offering appeals for legitimate users.
- Monitoring behavior after verification.
Sybil resistance is an arms race.
Passport is a tool in that arms race, not the end of it.
What Is Model-Based Detection?
Human Passport and related systems increasingly use more than Stamp-based verification.
Model-based detection analyzes wallet behavior, onchain history, transaction patterns, and other signals to classify or cluster wallets.
This can help detect Sybil wallets even if they have some credible-looking activity.
For example, a model might look for:
- Wallets funded from the same source.
- Similar transaction timing.
- Similar contract interactions.
- Repeated farming patterns.
- Coordinated bridge usage.
- Shared gas funding.
- Identical quest behavior.
- Suspicious wallet clusters.
- Thin but optimized activity.
Model-based detection can be powerful, especially for airdrops and grants.
But it also introduces transparency questions. Users may not know why they were flagged. Legitimate users may resemble suspicious patterns. Builders should provide clear communication and appeals when decisions are high-stakes.
What Passport Proves — and What It Does Not Prove
Passport can provide useful evidence, but it should not be overinterpreted.
Passport can help show:
- A wallet has human-related credentials.
- A wallet has meaningful onchain or offchain signals.
- A user may be less likely to be a bot.
- A wallet may meet a project’s Sybil-resistance threshold.
- A participant may be eligible for a human-gated action.
Passport does not prove:
- The user’s legal identity.
- The user’s real name.
- The user’s citizenship.
- The user’s age.
- The user’s location.
- The user’s intentions.
- The user is honest.
- The user controls only one wallet.
- The user will not rent or sell access.
- The user satisfies regulatory KYC.
This distinction is important.
Passport is a proof-of-humanity and Sybil-resistance signal, not a universal identity oracle.
How to Use Passport as a User
A typical user flow may look like this:
- Visit the Human Passport app.
- Connect your wallet.
- Review available Stamps.
- Choose the Stamps you are comfortable verifying.
- Complete verification steps.
- Build your Unique Humanity Score.
- Use your Passport with supported apps.
- Refresh or update Stamps when needed.
Users should think strategically about privacy.
Do not connect accounts casually. Understand what each Stamp reveals. Use wallets intentionally. Consider whether you want one public wallet for reputation or separate wallets for different activities.
A single wallet with many Stamps may be convenient, but it can also become a durable identity anchor.
How to Use Passport as a Builder
A typical builder flow may look like this:
- Define the abuse problem.
- Decide whether Passport is appropriate.
- Choose a score threshold or verification requirement.
- Integrate the Passport API, SDK, or supported partner tool.
- Test the user flow.
- Explain the requirement clearly.
- Offer fallbacks or appeals.
- Monitor results.
- Adjust thresholds over time.
- Avoid collecting unnecessary data.
Builders should avoid saying “Passport proves this user is real” too strongly. A more accurate phrase is:
“Passport provides a Sybil-resistance signal that helps us evaluate whether this wallet is likely controlled by a real human.”
That wording is more honest and reduces overreliance.
Best Use Cases for Human Passport
Human Passport is especially useful when the app needs flexible, crypto-native Sybil resistance.
Strong use cases include:
- Airdrop protection
- Grant funding
- DAO participation
- Quest verification
- Community gating
- Web3 waitlists
- Testnet reward filtering
- NFT allowlists
- Onchain reputation
- Bot reduction
- Public goods funding
- Decentralized social apps
It is less ideal as a replacement for:
- Legal KYC
- Age verification where legal identity is required
- Sanctions screening
- High-assurance biometric uniqueness
- Government identity
- Financial compliance
- Proof of good behavior
Passport is most useful in the middle: stronger than no verification, lighter than KYC, and more flexible than a single biometric proof.
When Passport Is a Bad Fit
Passport may not be the right tool when:
- The app legally requires KYC.
- The use case is too low-risk to justify identity friction.
- Users are mostly new to crypto.
- The community strongly values unlinkability.
- The project cannot explain why Passport is required.
- The threshold would exclude too many legitimate users.
- Attackers have strong incentives and can farm the required signals.
- The app has no appeal process.
- The project treats the score as absolute truth.
- The user experience would be too confusing.
The best identity tools are proportional. Do not use Passport just because it is available. Use it when the abuse problem justifies it.
Passport and the Future of Web3 Identity
Human Passport represents a broader shift in Web3 identity.
Early crypto identity was mostly about wallets. If you controlled the private key, you controlled the account.
That was enough for payments and basic ownership. But it is not enough for human-centered systems.
The next generation of Web3 apps needs richer identity primitives:
- Proof of humanity
- Reputation
- Credentials
- Attestations
- Wallet history
- Privacy-preserving verification
- Sybil resistance
- Account recovery
- Selective disclosure
- Cross-app trust signals
Passport is one of the most important attempts to build that layer without defaulting to traditional KYC.
It is not the only approach. Biometric systems, zero-knowledge credentials, social graphs, and government-backed digital IDs will all play roles.
But Passport’s multi-signal model is likely to remain important because it matches how online trust actually works: not one document, but many signals.
Summary: Gitcoin Passport / Human Passport Explained
Gitcoin Passport, now Human Passport, is a Web3 identity verification and Sybil-resistance protocol.
It helps users collect Stamps, build a Unique Humanity Score, and prove that a wallet is more likely to belong to a real human. Apps can use Passport to protect airdrops, grants, DAO votes, waitlists, quests, communities, and other Web3 experiences from bots and fake accounts.
Its biggest strengths are:
- Crypto-native design
- Flexible Stamps
- Reusable human signals
- Lower friction than KYC
- Useful airdrop protection
- Strong fit for grants and DAOs
- Privacy-aware positioning
- Developer integrations
Its biggest limitations are:
- It is probabilistic.
- It can be farmed.
- It may exclude new or private users.
- It can create account-linking risks.
- It is not KYC.
- It does not prove good behavior.
- It requires careful threshold design.
The simplest way to understand Passport is this:
Human Passport helps Web3 apps decide whether a wallet looks human enough to trust for a specific action.
That makes it one of the core tools in the proof-of-personhood and Sybil-resistance stack.
FAQ: Gitcoin Passport / Human Passport
What is Gitcoin Passport?
Gitcoin Passport, now Human Passport, is an identity verification and Sybil-resistance protocol for Web3. It helps users collect identity Stamps and build a humanity score that apps can use to reduce bots, fake wallets, and Sybil attacks.
Is Gitcoin Passport now Human Passport?
Yes. Gitcoin Passport is now known as Human Passport. Many users still search for the older name, but the current product is Human Passport.
What are Passport Stamps?
Passport Stamps are credentials or signals that help verify a user’s identity, reputation, or humanity. They can come from Web2 accounts, Web3 activity, social credentials, onchain history, attestations, and other sources.
What is the Unique Humanity Score?
The Unique Humanity Score is a score based on a user’s Passport signals. It helps apps estimate whether a wallet is likely controlled by a real, unique human.
Is Gitcoin Passport KYC?
No. Gitcoin Passport / Human Passport is not traditional KYC. KYC verifies legal identity. Passport provides proof-of-humanity and Sybil-resistance signals for Web3 apps.
How does Passport help with airdrops?
Passport helps airdrops reduce wallet farming by requiring users to meet a humanity threshold, collect Stamps, or pass Sybil-resistance checks before claiming rewards.
Can Gitcoin Passport stop all Sybil attacks?
No. Passport can reduce Sybil attacks and raise attacker costs, but it cannot stop all abuse. Sophisticated attackers may farm signals, rent accounts, or mimic legitimate activity.
Is Human Passport private?
Human Passport is designed to be more privacy-preserving than traditional KYC, and its public materials emphasize privacy-by-design. However, users should understand that collecting Stamps may link wallets, accounts, and credentials.
How is Human Passport different from World ID?
Human Passport uses multiple signals, Stamps, and scores to evaluate humanity and trust. World ID is best known for biometric proof of human through Orb-based iris verification. Human Passport is more multi-signal and reputation-oriented, while World ID is more focused on strong uniqueness.
Should my Web3 app use Passport?
Your app should consider Passport if it needs Sybil resistance for airdrops, grants, quests, communities, DAO voting, or waitlists. It may not be appropriate if your app legally requires KYC or if the use case is too low-risk to justify identity friction.
Suggested Internal Links
Use these once the directory pages exist:
- Proof of Personhood Directory
- What Is Proof of Personhood?
- Proof of Personhood vs KYC
- Worldcoin / World ID Explained
- How Crypto Projects Use Sybil Resistance
- Zero-Knowledge Identity Explained
- Best Proof-of-Personhood Protocols
- Sybil Resistance Tools
- Multi-Source Identity Aggregators
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.
- Human Passport official website
- Human Passport developer docs
- Human Passport support center
- Passport Stamps documentation
- Gitcoin Passport migration / support materials
- Gitcoin Grants Sybil resistance materials
- W3C Verifiable Credentials documentation
- Ethereum Attestation Service documentation
- Research on Sybil attacks in peer-to-peer networks
- Public materials on quadratic funding and Sybil resistance
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 Gitcoin Passport?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Gitcoin Passport, now Human Passport, is an identity verification and Sybil-resistance protocol for Web3. It helps users collect identity Stamps and build a humanity score that apps can use to reduce bots, fake wallets, and Sybil attacks."
}
},
{
"@type": "Question",
"name": "Is Gitcoin Passport now Human Passport?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Gitcoin Passport is now known as Human Passport. Many users still search for the older name, but the current product is Human Passport."
}
},
{
"@type": "Question",
"name": "What are Passport Stamps?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Passport Stamps are credentials or signals that help verify a user's identity, reputation, or humanity. They can come from Web2 accounts, Web3 activity, social credentials, onchain history, attestations, and other sources."
}
},
{
"@type": "Question",
"name": "Is Gitcoin Passport KYC?",
"acceptedAnswer": {
"@type": "Answer",
"text": "No. Gitcoin Passport / Human Passport is not traditional KYC. KYC verifies legal identity. Passport provides proof-of-humanity and Sybil-resistance signals for Web3 apps."
}
},
{
"@type": "Question",
"name": "How is Human Passport different from World ID?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Human Passport uses multiple signals, Stamps, and scores to evaluate humanity and trust. World ID is best known for biometric proof of human through Orb-based iris verification. Human Passport is more multi-signal and reputation-oriented, while World ID is more focused on strong uniqueness."
}
}
]
}
Claude Code Implementation Notes
Create this as an individual blog article page.
Recommended file path options:
/content/blog/gitcoin-passport-explained.md
or
/src/content/blog/gitcoin-passport-explained.md
or, for a simple static Cloudflare Pages site:
/public/blog/gitcoin-passport-explained/index.html
Use the frontmatter fields for the blog index card, page title, SEO meta tags, canonical URL, and social sharing metadata.
Preferred route:
/blog/gitcoin-passport-explained
END POST 5
Explore the directory
See the full directory of decentralized identity and proof-of-personhood protocols, categorized and filterable.
All Blog Posts Protocol Directory