-
Notifications
You must be signed in to change notification settings - Fork 507
Open
Description
User Story:
As a Passport user
I want to verify my X account status and credibility
So that I can increase my humanity score using my verified X presence as proof of being human
Acceptance Criteria
Core Requirements:
- ✅ Has verified status: Premium, Premium+, Business, Government, or Legacy verification
- ✅ At least 100 followers
- ✅ Account age > 365 days
Assigned points: 3.2
Verification Flow:
GIVEN a user wants to verify their X account
WHEN they initiate X verification
THEN the system should:
- Authenticate via X OAuth2
- Retrieve user profile and verification status
- Check all 3 requirements are met
- Award points based on verification tier
Technical Implementation
https://github.com/lebraat/x-verifier
API Requirements:
- X API v2 access
- OAuth 2.0 authentication flow
- User lookup endpoint for verification status
- Rate limiting: 300 requests/15-min window
Verification Status Detection:
// Check for verified badge types
const verificationTypes = {
premium: 'blue', // $8/month
premium_plus: 'blue_plus', // $16/month
business: 'gold', // $1,000/month
government: 'gray', // Government verified
legacy: 'blue_legacy' // Pre-Elon verification
}Key Design Decisions
Why These Requirements:
- Paid verification: Direct financial cost creates strong Sybil resistance
- 100+ followers: Shows actual social presence, not just payment
- Account age: Prevents new account farming, requires time investment
Risks & Mitigation:
- API costs: X API Pro tier expensive - optimize calls
- Rate limits: Implement queueing system
- Verification changes: X frequently updates verification system
- Regional availability: Premium not available in all countries
Priority: HIGH - Extremely strong Sybil signal
Effort: MEDIUM - Need X API setup and approval
Impact: VERY HIGH - Paid verification is costly to fake
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
Prioritized