Zero Knowledge and Advanced Cryptography

The Zero Knowledge and Advanced Cryptography bounty is part of the Kusama Vision Program, a 10M DOT initiative dedicated to advancing zero-knowledge technology and advanced cryptography on Kusama. This program is managed by community-trusted curators, independent from the Web3 Foundation and OpenGov treasury.

Program Overview

Detail	Information
Total Funding	10M DOT (shared pool)
Program	Kusama Vision
Decision Makers	Community-trusted curators
Governance	Independent from Web3 Foundation
Application	zk.kusama.vision
Status	Ongoing (rolling applications)

Core Philosophy

The Zero Knowledge and Advanced Cryptography program is built on the principle that privacy is non-negotiable and fundamental to a free society. The program aims to:

Shift trust from institutions and intermediaries to mathematics and cryptography
Enable privacy that is enforced by code, not policy
Build resilient systems with no censorship, blocking, or filtering of transactions

Why Kusama?

Kusama provides the ideal environment for ZK development:

Fast-Moving Network: Rapid iteration and early deployment
Real Conditions Testing: Production environment, not just testnets
Open Ecosystem: Contribute reusable components for the entire ecosystem
Resilient Execution: Censorship-resistant transaction processing

Funding Categories

The bounty supports projects across multiple categories:

1. Runtime Integration

Integrate ZK proof verification directly into Kusama parachain runtimes.

Examples:

Native ZK verification in runtime
Precompile additions for ZK operations
Runtime-level privacy primitives

2. Smart Contracts

Build privacy-preserving smart contract execution on PolkaVM and other contract platforms.

Examples:

Shielded pool contracts
Private DeFi protocols
ZK-verifiable contract logic

3. Applications

Real-world privacy applications deployed on Kusama.

Examples:

Private payment systems
Anonymous credential systems
Privacy-preserving identity solutions

4. Optimized ZK Libraries for PolkaVM

Develop RISC-V optimized ZK code for the PolkaVM execution environment.

Examples:

Poseidon hash implementations
SNARK/STARK verifiers
Merkle tree libraries

5. Selective Disclosure & ZK Identity

Build credentials, membership proofs, reputation systems, and Sybil resistance mechanisms.

Examples:

ZK identity protocols
Credential systems with selective disclosure
Proof of personhood without doxxing
Reputation systems with privacy

6. Private Governance

Enable privacy-preserving participation in OpenGov and other governance systems.

Examples:

Private voting systems
Hidden delegation strategies
Confidential proposal submissions

7. Private DeFi

Develop privacy-preserving decentralized finance protocols.

Examples:

Private DEX with hidden order books
Confidential lending protocols
Private stablecoins
Shielded liquidity pools

8. Quantum-Resistant ZK

Research and implement post-quantum cryptographic proof systems.

Examples:

STARK-based constructions
Lattice-based ZK proofs
Hash-based proof systems

Eligibility Criteria

To qualify for funding, projects must:

✅ Apply zero-knowledge technology in innovative ways
✅ Integrate with Kusama ecosystem (runtimes, contracts, or applications)
✅ Reduce information leakage while preserving verifiability
✅ Contribute open, reusable components to the ecosystem
✅ Work in real production conditions on Kusama

Application Process

Step 1: Join the Community

Before applying, engage with the community:

Visit ZK SPACE community hub
Discuss your ideas with other developers
Get feedback on your proposal concept
Connect with potential collaborators

Step 2: Prepare Your Proposal

Your proposal should include:

# Zero Knowledge and Advanced Cryptography Proposal

## Project Summary
[Clear description of what you're building]

## Problem Statement
[What privacy problem are you solving?]

## Technical Approach
- ZK proof system: [Groth16/PLONK/Halo2/STARK]
- Integration point: [Runtime/Contract/Application]
- Privacy guarantees: [What is hidden vs. verified]

## Kusama Integration
[How does this integrate with Kusama ecosystem?]

## Open Source Plan
[What components will be reusable by others?]

## Budget
[Requested amount and breakdown]

## Timeline
[Milestones and delivery dates]

## Team
[Relevant experience and credentials]

Step 3: Submit Application

Visit zk.kusama.vision
Click "APPLY NOW"
Fill out the application form
Submit your proposal

Step 4: Curator Review

Your proposal will be reviewed by community-trusted curators who evaluate:

Technical merit and innovation
Feasibility of implementation
Benefit to Kusama ecosystem
Team capability
Budget reasonableness

Step 5: Decision and Funding

Curators make funding decisions
Approved projects receive funding
Work begins on milestones
Regular progress updates required

Decision-Making Process

Community Curators

Unlike OpenGov treasury proposals, Zero Knowledge and Advanced Cryptography decisions are made by a group of community-trusted curators who:

Have expertise in zero-knowledge cryptography
Understand the Kusama ecosystem
Evaluate technical merit independently
Are independent from Web3 Foundation
Make decisions based on project quality, not popularity

Evaluation Criteria

Criteria	Weight	Description
Technical Innovation	30%	Novel use of ZK technology
Kusama Integration	25%	How well it integrates with ecosystem
Privacy Impact	20%	Real privacy improvements
Reusability	15%	Open components for others
Team Capability	10%	Ability to deliver

Request for Proposals (RFP)

The curators have created a list of Request for Proposals (RFPs) - specific projects and research areas they want to see developed. These RFPs represent high-priority needs for the Kusama ecosystem.

View and Apply for RFPs

codeberg.org/kusama-zk/RFP

Browse the full list of open RFPs and submit proposals for projects that match your expertise.

Why Apply for an RFP?

Priority Review: RFP proposals receive expedited curator attention
Clear Requirements: Well-defined scope and deliverables
Higher Success Rate: Aligned with curator priorities
Ecosystem Impact: Address critical Kusama needs

RFP Categories

RFPs cover various areas including:

ZK Infrastructure: Provers, verifiers, circuit libraries
Privacy Applications: Shielded pools, private DeFi, anonymous credentials
PolkaVM Optimization: RISC-V optimized ZK code
Identity & Governance: Selective disclosure, private voting
Research: Post-quantum ZK, proof aggregation, novel constructions

Responding to an RFP

Review the RFP: Read the full requirements on Codeberg
Assess Fit: Ensure your team has relevant expertise
Prepare Proposal: Address all RFP requirements specifically
Submit Application: Apply via zk.kusama.vision
Reference the RFP: Mention which RFP you're responding to in your application

Open RFP Process

RFPs are updated regularly as priorities evolve and projects are completed:

New RFPs: Added based on ecosystem needs and curator input
Completed RFPs: Marked as fulfilled when projects ship
Community Suggestions: Propose new RFP topics via ZK SPACE

What Makes a Strong Proposal?

Do ✅

Demonstrate ZK expertise: Show understanding of proof systems
Clear privacy guarantees: Explain what's hidden and what's verified
Kusama-native thinking: Design for Kusama's architecture
Open source commitment: Plan for community reuse
Realistic timeline: Achievable milestones
Production focus: Build for real-world use

Don't ❌

Vague privacy claims: Be specific about cryptographic guarantees
Generic proposals: Tailor to Kusama specifically
Closed source: Must contribute to ecosystem
Overpromising: Under-promise and over-deliver
Ignoring existing work: Build on existing ZK libraries

Reporting Requirements

Once funded, projects must:

Regular Updates: Progress reports every 2-4 weeks
Milestone Delivery: Meet agreed-upon deadlines
Open Source: Release code as agreed
Final Report: Summary of outcomes and learnings
Community Engagement: Present work to community

Kusama Zero Knowledge