1. Summary
This proposal requests the Kleros DAO to fund and coordinate a zero-knowledge (ZK) integration for Proof of Humanity (PoH), enabling privacy-preserving Sybil resistance. Specifically, the DAO would allocate a budget of 2,000,000 PNK (and/or ETH from the treasury) to sponsor development grants, documentation, and user-education campaigns around ZK attestations in PoH.
2. Motivation
- Deepfake & Privacy Concerns: PoH’s reliance on public video submissions can deter privacy-minded users and might be vulnerable to increasingly sophisticated video forgeries.
- Expansion of PoH Adoption: Many integrators—especially those in regulated or privacy-sensitive industries—seek a “prove you’re in PoH without revealing your face or main address.” A ZK approach addresses that demand.
- Kleros Ecosystem Growth: A robust PoH with optional ZK features encourages more integrations (from DeFi to social media), benefiting both Kleros and PoH communities.
3. Scope & Deliverables
- ZK Integration Roadmap
- A 4–6 week process to define technical specifications for hooking up Sismo Connect, Iden3, or a similar solution.
- Whitepaper or spec detailing how PoH “claims” can be minted as private credentials, verified by dApps, and challenged in Kleros if misused.
- PoH-ZK Development Grant
- Allocate X PNK/ETH to a bounty or dev team that implements a minimal MVP for:
- Generating zero-knowledge proofs of PoH membership.
- Verifying said proofs on-chain or in a sidecar service.
- Deliver a test suite and deployment instructions for the PoH community.
- UI/UX Demos & Documentation
- Tutorials, user flows, and “ZK mode” within PoH’s existing front end to guide users through generating their “ZK badge.”
- Educate integrators (DAOs, DeFi apps) on hooking up ZK-based Sybil-resistance checks.
4. Budget & Timeline
-
Budget: 2,000,000 PNK (or an equivalent in DAI/ETH if approved by the DAO)
- 1,000,000 for dev grants
- 200,000 for documentation & design bounties
- 800,000 for marketing/outreach/Layer3 quests
-
Timeline:
- Phase 1 (1 month): Draft architecture, gather community feedback.
- Phase 2 (2–3 months): Develop MVP + documentation.
- Phase 3 (1 month): UI integration, pilot testing, marketing push.
5. Implementation & Oversight
- Kleros Core Team: Provide general oversight and ensure grants are disbursed according to milestones.
- PoH Lead, Devs & Community: Collaborate closely on technical choices (Sismo vs. Iden3 vs. custom approach).
- Regular Check-Ins: Bi-weekly progress updates on the Kleros forum, final deliverables posted for community review.
6. Conclusion
Adopting zero-knowledge proofs in PoH is a strategic next step for attracting the users who are more privacy concerned. Funding a structured roadmap and grants via the Kleros DAO will boost PoH adoption, reinforce Sybil resistance, and expand the overall Kleros ecosystem. We ask the community to vote FOR this proposal to allocate resources and begin the ZK integration process promptly.
Potential Discussion Topics in Comments
- Which ZK approach is best? (e.g., Sismo, Iden3, custom PLONK-based circuit).
- How large should the dev bounty be?
- Should this be a multi-phase proposal? (e.g., “feasibility study” first, then a second vote for the final budget).