Goal: Get 1,000+ developers aware of UHP in the first month, recruit 10-20 contributors, validate demand before building.
✅ 1. Create GitHub Organization
- Create
uhp-protocolorganization - Add repository:
uhp-protocol/uhp - Upload files:
README.mduhp-whitepaper.mdUHP-Explainer.mdLICENSE(MIT)CONTRIBUTING.mdCODE_OF_CONDUCT.md(Contributor Covenant)
✅ 2. Create GitHub Discussions
- Enable Discussions tab
- Create categories:
- 💬 General
- 💡 Ideas
- 🙏 Q&A
- 📣 Announcements
- 🔐 Security
✅ 3. Create Initial Issues
- Create "good-first-issue" issues:
- "Design UHP logo"
- "Set up Discord server"
- "Write CONTRIBUTING.md"
- "Create protocol specification template"
- "Research PQC WebAuthn standards"
✅ 4. Add Topics/Tags
- Add GitHub topics:
decentralized-identity,post-quantum-cryptography,oauth,webauthn,blockchain,quantum-resistant,self-sovereign-identity
Title: "Universal Handle Protocol: Replacing email-based identity with quantum-resistant handles [pdf]"
Submission URL: github.com/uhp-protocol/uhp/blob/main/uhp-whitepaper.md
Comment (post immediately after submitting):
Hi HN! I'm Ethan, a self-taught developer who's been studying cryptography
and decentralized systems for 6-7 years.
I've designed the Universal Handle Protocol (UHP) - an open-source,
quantum-resistant identity protocol to replace email-based authentication.
Key ideas:
- Handles like @username (not email addresses)
- XMSS signatures on QRL blockchain (quantum-safe)
- Federated like email (anyone can run an instance)
- OAuth 2.0 compatible (easy Web2 integration)
- WebAuthn passwordless auth
The 25-page whitepaper is here: [link]
2-page summary: [link]
I'm looking for:
1. Cryptographers to review the security model
2. Developers interested in building the reference implementation
3. Feedback on whether this solves a real problem
This is 100% open-source (MIT license). No company, no ICO, just a protocol.
What am I missing? What would you change?
Best time to post: Friday 9-11am PST or Saturday 10am-2pm PST Expected upvotes: 50-300 (if it resonates) Follow-up: Respond to EVERY comment within first 2 hours
r/CryptoCurrency (9.58M members)
- Title: "I'm building an open-source quantum-resistant identity protocol to replace email-based logins. Here's the whitepaper."
- Post 2-page explainer + link to GitHub
- Flair: "INNOVATION"
- Best time: Tuesday-Thursday 7-9am EST
r/Ethereum (3.3M members)
- Title: "Universal Handle Protocol: A quantum-safe alternative to ENS that works on any blockchain"
- Focus on multi-chain support vs ENS's Ethereum-only
- Best time: Wednesday 8-10am EST
r/Technology (15M members)
- Title: "An open protocol to replace Google/Apple OAuth with quantum-resistant, decentralized identity"
- Focus on privacy + quantum threat
- Best time: Monday 9-11am EST
r/OpenSource (200K members)
- Title: "Universal Handle Protocol: MIT-licensed decentralized identity standard (looking for contributors)"
- Focus on open-source collaboration
- Best time: Any day, 10am-2pm EST
r/Crypto (300K members)
- Title: "[Technical] Post-quantum identity protocol using XMSS signatures - feedback wanted"
- Focus on cryptography
- Best time: Any day, 9am-12pm EST
Create Twitter account: @UHProtocol (or @UniversalHandle if available)
Launch thread template:
🧵 After 6 years studying cryptography and decentralized systems,
I've designed a protocol to replace email-based identity with
quantum-resistant handles.
It's called the Universal Handle Protocol (UHP). Here's what it is:
1/ The Problem 🚨
You use email for EVERYTHING online. But:
• Google/Apple control your identity
• RSA/ECDSA will break when quantum computers arrive (2030-2035)
• Privacy = zero (they scan all your emails)
• 130 accounts = 130 passwords
2/ Existing "solutions" don't solve it:
• ENS: Ethereum-only, $5-640/year, gas fees
• Google OAuth: Centralized surveillance
• Unstoppable: No comprehensive auth
• DID (W3C): Too complex, zero adoption
3/ The UHP Solution 💡
One handle for everything: @yourname
Works on:
✅ Web2 (Netflix, Spotify, Reddit)
✅ Web3 (DeFi, NFTs, DAOs)
✅ Professional (company tools)
✅ Social (Twitter, Discord)
No email. No passwords. No tracking.
4/ How it works under the hood:
• XMSS signatures (quantum-resistant, NIST-approved)
• QRL blockchain (post-quantum by design)
• WebAuthn (Face ID, fingerprint, hardware keys)
• OAuth 2.0 (developers already know it)
• Federated (like email - anyone can run an instance)
5/ Why now? ⏰
• NIST released PQC standards (2024)
• BlackRock warned of quantum threat (May 2025)
• "Harvest now, decrypt later" attacks are happening TODAY
• People are tired of Big Tech surveillance
6/ This is an OPEN PROTOCOL, not a company.
• MIT licensed (like Linux, Bitcoin, HTTP)
• Anyone can run an instance
• Community-governed
• No ICO, no token (yet - maybe DAO later)
Think: OAuth 2.0 meets Bitcoin meets Post-Quantum Crypto
7/ I need YOUR help 🙏
Looking for:
• Cryptographers (review security)
• Developers (build reference implementation)
• Community (spread the word)
• Feedback (is this solving a real problem?)
25-page whitepaper: [GitHub link]
2-page explainer: [GitHub link]
8/ This is the launch tweet.
No company behind this. No VC funding (yet).
Just me (a self-taught dev in Jacksonville, FL) and whoever
wants to build the post-email internet.
Star the repo if you're interested: [GitHub link]
Let's make email-based identity obsolete. 🚀
/end
Accounts to tag (after posting):
- @VitalikButerin (Ethereum founder - identity interested)
- @naval (decentralization advocate)
- @balajis (crypto thought leader)
- @punk6529 (NFT thought leader, identity focused)
- @evan_van_ness (Ethereum community)
- @QRLedger (QRL official account)
- @FIDOAlliance (WebAuthn standards)
Hashtags: #DecentralizedIdentity #PostQuantum #Crypto #Web3 #OpenSource #BuildInPublic
Create UHP Protocol Discord Server
Channels:
- #announcements (read-only)
- #general
- #introductions
- #whitepaper-discussion
- #protocol-design
- #reference-implementation
- #cryptography
- #dev-chat
- #off-topic
Invite early supporters:
- Post Discord link on GitHub README
- Share in Reddit comments
- Share in Twitter thread
Moderation:
- You + 2-3 trusted moderators
- Contributor Covenant Code of Conduct
1. Dev.to
- Write article: "Building a Quantum-Resistant Identity Protocol: Lessons Learned"
- Include whitepaper link
- Tags: #cryptography #security #opensource #blockchain
2. Medium
- Cross-post Dev.to article
- Publish to relevant publications:
- "Better Programming"
- "Level Up Coding"
- "The Startup"
3. Substack
- Create "UHP Development Blog"
- Publish weekly updates
1. Hacker News (follow-up posts)
- Day 7: "Show HN: UHP Protocol - Looking for contributors"
- Link to GitHub with initial code (if ready)
2. Lobsters (lobste.rs)
- Submit whitepaper
- Tag: cryptography, distributed
3. Bitcoin Talk (bitcointalk.org)
- Post in "Altcoin Discussion" or "Project Development"
- Focus on quantum resistance angle
4. IETF Mailing Lists
- Subscribe to: oauth@ietf.org, saag@ietf.org (Security Area)
- Post introduction: "New Internet-Draft proposal: Universal Handle Protocol"
- Link to whitepaper
5. IACR ePrint Archive (eprint.iacr.org)
- Submit whitepaper to cryptology preprint archive
- Requires academic-style formatting
- Gives credibility to cryptographic design
Target: 20-30 professors
Tier 1 (Aspirational - 5 professors):
- Dan Boneh (Stanford)
- Silvio Micali (MIT)
- Dawn Song (Berkeley)
- Andreas Hülsing (TU Eindhoven)
- Dustin Moody (NIST)
Tier 2 (Regional - 10 professors):
- University of North Florida
- Florida State University
- University of Florida
Tier 3 (Broader reach - 10 professors):
- Georgia Tech
- Carnegie Mellon
- UT Austin
- USC
- UIUC
Template: See professor-outreach-email.md
Follow-up schedule:
- Day 8: Send 5 emails (Tier 1)
- Day 9: Send 10 emails (Tier 2)
- Day 10: Send 10 emails (Tier 3)
- Day 22: Follow up with non-responders (once only)
Target conferences (2025-2026):
Tier 1 (Academic):
- IEEE S&P (Oakland)
- USENIX Security
- ACM CCS
- NDSS
Tier 2 (Industry):
- RSA Conference
- Black Hat
- DEF CON
- OWASP AppSec
Tier 3 (Web3):
- ETHDenver
- Consensus
- DWeb Camp
Submission strategy:
- Start with Tier 3 (easier acceptance)
- Work up to Tier 1 (prestige)
- Target: 1 accepted talk in Year 1
Week 1:
- Blog: "Introducing the Universal Handle Protocol"
- Twitter: Launch thread + daily updates
Week 2:
- Blog: "Deep dive: How XMSS signatures work"
- Twitter: Cryptography explainer thread
Week 3:
- Blog: "Federated identity: Learning from email's success"
- Twitter: Architecture diagram + explanation
Week 4:
- Blog: "First month of UHP: What we've learned"
- Twitter: Metrics (stars, contributors, feedback)
Crypto Podcasts:
- Bankless (bankless.com)
- Unchained (Laura Shin)
- Epicenter (epicenter.tv)
- The Defiant (thedefiant.io)
- Zero Knowledge (zeroknowledge.fm)
Tech Podcasts:
- Software Engineering Daily
- Changelog
- CoRecursive
Outreach template:
Subject: Guest Pitch: Building a Quantum-Resistant Identity Protocol
Hi [Host Name],
I'm Ethan, a self-taught developer working on the Universal Handle
Protocol (UHP) - an open-source, quantum-resistant alternative to
email-based identity.
Potential episode angle:
• Why email is broken for modern authentication
• Post-quantum cryptography for developers
• Building internet protocols in the open-source era
• The path from self-taught dev to protocol designer
Traction so far: [X GitHub stars, Y contributors, Z media mentions]
Would this be a fit for [Podcast Name]?
Whitepaper: [link]
Thanks,
Ethan
YouTube:
- Create UHP Protocol channel
- Videos to make:
- "UHP in 60 seconds"
- "Why quantum computers will break your passwords"
- "How federated identity works"
- "Code walkthrough: Integrating 'Sign in with UHP'"
TikTok/Instagram Reels:
- Short explainer videos (15-60 seconds)
- Reach non-technical audience
- Example: "Did you know Google reads all your emails? Here's the alternative..."
Reach out to:
- ENS Labs: Position UHP as complementary, not competitive
- Unstoppable Domains: Explore integration possibilities
- Gitcoin: Apply for grants, join community
- Protocol Labs: Request grant for decentralized identity infrastructure
- MetaMask: Integrate UHP handle resolution
- Coinbase Wallet: OAuth integration
- Rainbow Wallet: Handle-based contacts
- Trust Wallet: Cross-chain identity
- BanklessDAO: Present to community, get feedback
- Developer DAO: Recruit contributors
- Crypto, Culture & Society (CCS): Educational partnership
- Brave Browser: Privacy-first identity integration
- Firefox: Open-source alignment
- ✅ 100+ GitHub stars
- ✅ 50+ Discord members
- ✅ 5+ contributors (issues, PRs, feedback)
- ✅ 1,000+ Twitter impressions
- ✅ 1 professor response (out of 20 emailed)
- ✅ 500+ GitHub stars
- ✅ 200+ Discord members
- ✅ 10+ active contributors
- ✅ 5,000+ Twitter impressions
- ✅ 3+ blog posts written
- ✅ 1+ podcast interview
- ✅ 2,000+ GitHub stars
- ✅ 500+ Discord members
- ✅ 25+ contributors
- ✅ Reference implementation (alpha)
- ✅ 5+ media mentions
- ✅ Academic feedback received
Free:
- GitHub (free for open-source)
- Discord (free)
- Twitter (free)
- Reddit (free)
- Dev.to, Medium (free)
Paid (Optional):
- Domain name: $12/year (uhprotocol.org)
- Twitter Blue: $8/month (verification badge)
- Canva Pro: $13/month (design graphics)
- Cloudflare Pro: $20/month (DDoS protection)
Total: $12-500/year (depending on choices)
Response:
- Don't panic - most projects take 3-6 months to gain traction
- Keep building in public
- Focus on quality over quantity (write better content)
- Reach out personally to 50 developers 1-on-1
Response:
- Listen carefully - they might be right about specific issues
- Don't get defensive
- Thank them for feedback
- Ask: "What would you change to make this work?"
- Update whitepaper based on valid critiques
Response:
- Research the existing solution thoroughly
- If they're right, acknowledge it and pivot
- If they're wrong, explain the differences clearly
- Example: "ENS does naming, but not federated OAuth. UHP does both."
Response:
- This is actually GOOD - they took time to review!
- Ask for specifics
- Fix the flaw
- Thank them profusely
- Ask if they'd review v0.2
Response:
- Don't let hype go to your head
- Focus on converting stars to contributors
- Set up infrastructure (Discord mods, GitHub templates)
- Keep quality high (don't rush to ship broken code)
1. Think Long-Term
- Protocols take 5-10 years to become standards
- Linux: 1991 → 2000s (mainstream)
- Bitcoin: 2009 → 2017 (mainstream awareness)
- UHP: 2025 → 2030-2035 (potential mainstream)
2. Build in Public
- Share everything: successes, failures, learnings
- People root for transparent builders
- Document the journey (blog, Twitter)
3. Stay Humble
- You're NOT Satoshi Nakamoto (yet)
- Listen to criticism
- Admit when you're wrong
- Thank everyone who helps
4. Avoid Burnout
- This is a marathon, not a sprint
- Take days off
- Don't check GitHub/Twitter every 5 minutes
- Celebrate small wins
5. Find Co-Founders
- You can't do this alone long-term
- Look for:
- Technical co-founder (backend/crypto expert)
- Community co-founder (marketing/DevRel)
- Equity split: 40/40/20 (you/tech/community)
Morning (8am-12pm):
- 8:00am: Push all files to GitHub
- 9:00am: Post to Hacker News
- 9:05am: Post first comment on HN thread
- 9:30am: Post to r/CryptoCurrency
- 10:00am: Post to r/Ethereum
- 10:30am: Post Twitter launch thread
- 11:00am: Create Discord server
- 11:30am: Email 5 professors (Tier 1)
Afternoon (12pm-6pm):
- 12:00pm: Lunch break
- 1:00pm: Respond to all HN comments
- 2:00pm: Respond to all Reddit comments
- 3:00pm: Engage on Twitter (reply to everyone)
- 4:00pm: Post to r/Technology
- 5:00pm: Post to r/OpenSource
- 6:00pm: Evening break
Evening (7pm-10pm):
- 7:00pm: Check all platforms again
- 8:00pm: Write first blog post (Dev.to)
- 9:00pm: Schedule tomorrow's content
- 10:00pm: Sleep (set notifications for HN/Reddit)
Daily routine:
- Morning: Check GitHub, Discord, Twitter, Reddit
- Mid-morning: Write code or content (blog, docs)
- Afternoon: Community engagement (respond to everything)
- Evening: Personal outreach (email developers)
Year 1: 10,000 GitHub stars, 100 contributors, reference implementation live Year 2: 100,000 handles registered, 1,000 websites using "Sign in with UHP" Year 3: Mainstream adoption begins, IETF RFC submitted Year 5: UHP becomes de facto standard for privacy-first authentication Year 10: Email-based identity is legacy, UHP is everywhere
Ultimate goal: When someone asks "How do I log into this website?", the answer is: "With your handle."
Now go build the future. 🚀
You have everything you need:
✅ Whitepaper
✅ GitHub README
✅ Professor email template
✅ Launch strategy
Next step: Push to GitHub and launch on Hacker News.
The only thing stopping you is hitting "publish."
"The best time to plant a tree was 20 years ago. The second best time is now."
Good luck, Ethan. The post-email internet starts today.