GitHub Contribution Proofs for Privacy‑Preserving Developer Grants & Bounties

zkTLS

The Problem
Grants, bounties, and retroactive funding programs want to support real developers—but asking contributors to share public GitHub profiles often means doxxing themselves or revealing sensitive company contributions. Worse, bots or fake accounts can easily spoof activity to farm rewards.

How Orange Pass Solves This
Orange Pass lets developers privately prove things like how many commits, PRs, or stars they’ve earned—without ever revealing their GitHub handle, organization, or actual repositories. The developer runs a zkTLS proof locally through the browser extension. That creates a verifiable attestation, which can be used by any Web3 grant platform or DAO.

Instead of sending in links, devs can now prove:

“I’ve pushed 50+ commits in the past 90 days.”

“I’ve had 5+ PRs merged this year.”

“My repos received 100+ stars”


— all in zero knowledge, tied to their wallet.

Real-World Example
Let’s say 0xNeko wants to apply for a DevDAO builder grant. The grant portal lets applicants use Orange Pass to verify their GitHub contributions. 0xNeko privately proves she qualifies for the “Silver Builder” tier—commits ≥ 50 or stars ≥ 100—and her wallet gets a verifiable DevRep attestation. The DAO sees only that she passed the threshold, not her employer or personal identity.

Why It’s Better

  • Devs stay pseudonymous, no doxxing required
  • Grants go to real builders, not gamed accounts
  • One attestation can be reused across multiple funding rounds

Try It Out

  1. Ask devs to install Orange Pass
  2. Set your eligibility criteria: e.g., Bronze (10 commits), Silver (50 commits or 100 stars), Gold (200 commits & 20 PRs)
  3. Use our verifier smart contract to automatically approve eligible wallets

Bonus: You can also link these DevRep attestations to a developer’s Orange Humanity Score (OHS) for deeper reputation building.


Leave a Reply

Your email address will not be published. Required fields are marked *