Gitcoin Passport is a decentralized identity verification tool that aggregates various "stamps" (identity verifications) to create a comprehensive trust score. It's primarily used for Sybil resistance in airdrops, grants, and governance .
Think of it as a Web3 credit score that proves you're a real, unique human without revealing your actual identity.
Core Concept
Multiple Identity Sources → Stamps Collected → Score Calculated
↓ ↓ ↓
GitHub, Twitter, Each stamp 0-100 score
ENS, Discord, adds points indicates trust
Google, etc. to score level
Copy link
Why Gitcoin Passport Matters
The Sybil Problem
In Web3, one person can create unlimited wallets:
Claim multiple airdrops
Vote multiple times
Farm rewards
Manipulate governance
Gitcoin Passport solves this by verifying identity across multiple platforms, making it expensive and difficult to fake.
Available Stamps
Blockchain/Web3
Stamp Points What It Verifies ENS Variable Owns .eth domain GTC Staking Up to 14.66 Staked GTC tokens GTC Holding Variable Holds GTC tokens Gitcoin Contributor Variable Donated to Gitcoin Grants Gitcoin Grant Owner Variable
Social/Online
Stamp Points What It Verifies Twitter Variable Verified Twitter account Twitter Account Age Variable Long-standing account Twitter Follower Count Variable Has followers GitHub Variable Active GitHub user GitHub Account Age Variable Long-standing account GitHub Followers
Privacy/Advanced
Stamp Points What It Verifies BrightID Variable Verified by BrightID network Proof of Humanity Variable Registered on PoH ** Idenam** Variable Verified by Idena Civic Variable Civic verification Holonym Variable Privacy -preserving verification
How Scoring Works
Score Calculation
Your score (0-100) is based on:
Number of stamps : More stamps = higher score
Stamp weight : Some stamps worth more
Uniqueness : Prevents gaming
Recency : Some stamps decay over time
Score Tiers
Score Trust Level Typical Use 0-10 Very Low No access 11-20 Low Basic access 21-50 Medium Standard features 51-75 High Most airdrops/grants 76-100 Very High Exclusive access
Example Scores
New User (Score: ~15) :
Google: 0.97
Twitter: 1.33
GitHub: 0.94
Discord: 0.91
Active Web3 User (Score: ~50) :
ENS: 3.16
GTC Staking: 14.66
Twitter: 6.18
GitHub: 3.84
Gitcoin Contributor: 13.87
Lens: 4.34
NFT Holder: 3.43
Power User (Score: ~80+) :
Multiple stamps
High-value stamps (GTC staking)
Long account ages
High follower counts
Multiple chains used
Use Cases
1. Airdrop Qualification
Most common use case:
Airdrop Announcement
↓
Requires Gitcoin Passport Score ≥ 20
↓
Users verify stamps
↓
Only qualified users claim
↓
Sybil attack prevented
Copy link
Examples :
Optimism airdrop
Various DeFi protocol airdrops
NFT mints
2. Gitcoin Grants
Quadratic funding requires Sybil resistance:
Grant Round Opens
↓
Contributors need Passport score
↓
Prevents one person from many donations
↓
Fair fund distribution
Copy link
3. DAO Governance
Prevent governance attacks:
Proposal Vote
↓
Require Passport score
↓
1 person = 1 vote (roughly)
↓
Fair governance
Copy link
Fair distribution:
NFT Mint
↓
Whitelist requires Passport
↓
Real users get access
↓
Bots excluded
Copy link
Token -gated communities:
Discord/Telegram Group
↓
Verify Passport score
↓
Quality community members
↓
Less spam/scams
Copy link
How to Get Gitcoin Passport
Step 1: Visit passport.human.tech
Step 2: Connect Wallet
MetaMask, Rainbow, etc.
Any EVM-compatible wallet
Step 3: Connect Accounts
Start with easy ones:
Google (quick, high trust)
Twitter (common, easy)
GitHub (if developer)
Discord (if Web3 user)
Step 4: Add Web3 Stamps
ENS (if you own .eth)
GTC (buy/stake if committed)
NFT Holder (if you have NFTs)
Gitcoin Contributor (donate to grants)
Step 5: Verify Advanced Stamps
BrightID (requires verification party)
Proof of Humanity (requires vouching)
** Idenam** (requires mining)
Step 6: Maintain Score
Some stamps may expire
Re-verify periodically
Add more stamps over time
Technical Architecture
Data Storage
Stamp Verification
↓
Stored on Ceramic Network
(decentralized data network)
↓
User controls their data
↓
Apps query score via API
Copy link
Privacy Features
Selective Disclosure : Choose what to share
Off-Chain Storage : Not all data on blockchain
User Control : Delete/update stamps
No PII On-Chain : Personal info stays private
Verification Process
1. User initiates stamp verification
2. OAuth/verification with provider (Twitter, etc.)
3. Gitcoin verifies account exists
4. Stamp added to Passport
5. Score recalculated
6. Data stored on Ceramic
Copy link
Gitcoin Passport vs Other Solutions
Feature Gitcoin Passport World ID Galxe Proof of Humanity Method Multi-signal aggregation Biometric iris scan Campaign credentials Social vouching Uniqueness Probabilistic Biometric guarantee Campaign-based Social consensus Privacy Pseudonymous
Benefits
For Users
Easy Setup : Most people have Google, Twitter
Free : No cost to verify
Portable : Use across all protocols
Privacy : Don't reveal identity
Progressive : Build score over time
For Projects
Sybil Resistance : Filter bots and farmers
Easy Integration : Simple API
Customizable : Set your own thresholds
Free : No cost to verify users
Trusted : Widely adopted standard
Standard : Common identity layer
Composable : Works with any protocol
Decentralized : No single point of failure
Open : Permissionless
Limitations & Challenges
Accessibility
Problem : Requires online presence
Impact : Excludes some users
Mitigation : Add more verification methods
Gaming Potential
Problem : Can buy accounts, followers
Impact : Score can be manipulated
Mitigation :
Weight long-term signals more
Use advanced detection
Require multiple signals
Centralization
Problem : Depends on Web2 platforms (Twitter, Google)
Impact : If platforms change API, stamps break
Mitigation : More Web3-native stamps
Privacy Trade-offs
Problem : Linking accounts reduces privacy
Impact : Some users uncomfortable
Mitigation :
Selective disclosure
ZK proofs (future)
Privacy-focused stamps
Score Thresholds
Problem : What score is "good enough"?
Impact : Projects set arbitrary thresholds
Mitigation : Guidelines and best practices
Best Practices
For Users
Start Early : Build score before you need it
Diversify Stamps : Don't rely on one type
Maintain Accounts : Keep stamps active
Privacy Awareness : Understand what you're sharing
Check Score Regularly : Ensure eligibility
For Projects
Set Appropriate Thresholds : Not too high, not too low
Communicate Clearly : Tell users what's needed
Give Time : Allow users to build score
Consider Alternatives : Some users excluded
Layer Defenses : Use with other Sybil methods
Future Development
Planned Features
ZK Proofs : Prove score without revealing stamps
More Stamps : Additional verification methods
Custom Scoring : Projects define their own criteria
Deeper Integration : More native protocol support
Improved Privacy : Less data exposure
Roadmap
Short-term : More stamp types, better UX
Medium-term : ZK integration, custom scoring
Long-term : Universal identity standard
Integration Guide
For Developers
// Check user's Passport score
import { PassportReader } from '@gitcoin/passport-sdk'
const reader = new PassportReader()
const score = await reader.getScore(userAddress)
if (score >= 20) {
// Allow action
} else {
// Request higher score
}
Copy link
API Endpoints
GET /score/{address} - Get user score
GET /stamps/{address} - Get user stamps
POST /verify - Verify specific stamp
Resources
See Also