ZKDocuVerify - Enterprise Confidential Document Verification

[Proposal setup] Proposal title

Please provide your proposal title

ZKDocuVerify - Enterprise Confidential Document Verification

[Proposal Summary] Time

Please specify how many months you expect your project to last

3

[Proposal Summary] Translation Information

Please indicate if your proposal has been auto-translated

No

Original Language

en

[Proposal Summary] Problem Statement

What is the problem you want to solve?

Enterprise and regulated applications require sharing sensitive documents in full. Midnight lacks native infrastructure for private document proofs, increasing risk and limiting enterprise adoption.

[Proposal Summary] Project Dependencies

Does your project have any dependencies on other organizations, technical or otherwise?

No

Describe any dependencies or write 'No dependencies'

No dependencies

[Proposal Summary] Project Open Source

Will your project's outputs be fully open source?

Yes

Please provide here more information on the open source status of your project outputs

All project deliverables will be released as open source under the MIT License, including smart contracts, proof circuits, SDK components, and documentation. The full codebase will be published in a public GitHub repository to ensure transparency, reuse, and community collaboration.

[Theme Selection] Theme

Please choose the most relevant theme and tag related to the outcomes of your proposal

Infrastructure

[Campaign Category] Category Questions

What is useful about your DApp within one of the specified industry or enterprise verticals?

• Built for regulated industries like legal, finance, healthcare, and enterprise compliance.
• Lets organizations verify sensitive documents without exposing private data.
• Dramatically reduces the risk of data leaks and unauthorized access.
• Builds stronger trust between businesses, partners, and customers.
• Helps teams meet strict privacy and regulatory requirements with confidence.
• Replaces slow, manual document checking with fast, cryptographic proof-based verification.
• Unlocks a new standard for secure, private document validation in real-world enterprise systems.

What exactly will you build? List the Compact contract(s) and key functions/proofs, the demo UI flow, Lace (Midnight) wallet integration, and your basic test plan.

Build a Midnight-based zero knowledge document proof system consisting of:

• Compact confidential smart contracts to store document commitments and verify proofs.
• Core functions for document hashing, Merkle tree generation, and zero-knowledge proof verification.
• A simple demo UI that allows users to upload a document, generate a proof, and verify claims without revealing the document content.
• Lace (Midnight) wallet integration for user authentication and transaction signing.
• A basic test plan including unit tests for proof logic, smart contract validation tests, and end-to-end UI flow testing on Midnight testnet.

How will other developers learn from and reuse your repo? Describe repo structure, README contents, docs/tutorials, test instructions, and extension points. Which developer personas benefit, and how will you gauge impact (forks, stars, issues, remixes)?

• Clear repository structure separating smart contracts, zero-knowledge circuits, frontend demo, and SDK utilities
• Detailed README with project overview, architecture diagrams, and step-by-step installation
• Practical usage examples to help developers get started quickly
• Markdown tutorials explaining contract deployment, proof generation, and verification flows
• Test instructions so developers can easily reproduce results
• Modular contract design and reusable libraries to support easy extension
• Designed primarily for dApp developers, Midnight builders, and enterprise teams
• Useful for teams building privacy-preserving and compliance-focused applications

[Your Project and Solution] Solution

Please describe your proposed solution and how it addresses the problem

This project will implement a practical, privacy-preserving document verification system using Midnight’s confidential smart contract model and zero-knowledge cryptography.

Key components of the solution include:

• A document commitment layer that converts uploaded files into cryptographic hashes and stores those hashes inside Midnight confidential contract state.
• A Merkle tree module that organizes document hashes efficiently and enables membership proofs without exposing unrelated records.
• A zero-knowledge proof circuit that allows users to prove specific claims (such as “this document contains a valid signature” or “this document was issued by a trusted entity”) without revealing the full document.
• Compact smart contracts written for Midnight that validate proof correctness and manage document commitments.
• A functional web interface demonstrating the full end-to-end user flow:
  • Document upload
  • Local hash generation
  • Proof generation
  • On-chain verification through Midnight
• Lace (Midnight) wallet integration for secure authentication and transaction signing.A structured testing workflow including unit tests for hashing and Merkle logic, smart contract validation tests, and end-to-end UI testing on Midnight testnet.

[Your Project and Solution] Impact

Please define the positive impact your project will have on Midnight ecosystem

This project delivers tangible, reusable infrastructure to the Midnight ecosystem rather than a single one-off application.

• Provides developers with a working reference implementation for document-based zero-knowledge proofs on Midnight.
• Lowers the barrier for teams building privacy-preserving enterprise and compliance-focused applications.
• Creates reusable libraries and contract patterns that can be adapted for other privacy-sensitive use cases such as credential verification, private attestations, and regulated workflows.
• Demonstrates real-world enterprise utility for Midnight beyond experimental or theoretical use cases.
• Strengthens trust in the ecosystem by showing how Midnight can support real privacy requirements in regulated industries.

[Your Project and Solution] Capabilities & Feasibility

What is your capability to deliver your project with high levels of trust and accountability? How do you intend to validate if your approach is feasible?

I have over 8 years of experience building and delivering real-world software products, from early prototypes to production-ready systems. I enjoy working on complex technical problems and have a track record of consistently delivering working solutions in both professional roles and open-source projects. I actively share my work through public repositories and regularly participate in technical hackathons.

To keep this project feasible, I will build it step by step, starting with simple, working versions of each core feature before adding more advanced functionality. Each milestone will be validated through testing, testnet deployments, and public code reviews, so that progress remains transparent, measurable, and easy for others to follow.

[Final Pitch] Budget & Costs

Please provide a cost breakdown of the proposed work and resources

The total budget of 10,000 USD will be used to cover direct development time, infrastructure, and testing costs required to deliver a functional MVP.

Cost breakdown:

• 4,000 USD – Core development of Midnight smart contracts, cryptographic proof logic, and Merkle tree implementation.
• 3,000 USD – Frontend development including demo UI, Lace (Midnight) wallet integration, and user flow implementation.
• 2,000 USD – Testing, testnet deployments, and technical documentation.
• 1,000 USD – Development infrastructure, cloud hosting for demos, and operational tooling.

All work will be delivered as open-source and verified through public repositories, demo deployments, and testnet transactions.

[Final Pitch] Value for Money

How does the cost of the project represent value for the Midnight ecosystem?

• Creates open-source infrastructure that can be reused by the entire Midnight and Cardano community.
• Produces shared tools, reference implementations, and documentation instead of a single closed application.
• Reduces development effort for future builders by providing ready-made building blocks.
• Accelerates innovation by giving developers proven privacy tools and patterns to build on.
• Makes it easier for new developers to start building on Midnight through practical, working examples.
• Delivers long-term ecosystem value rather than short-term or isolated outcomes.

[Self-Assessment] Self-Assessment Checklist

I confirm that the proposal clearly provides a basic prototype reference application for one of the areas of interest.

Yes

I confirm that the proposal clearly defines which part of the developer journey it improves and how it makes building on Midnight easier and more productive.

Yes

I confirm that the proposal explicitly states the chosen permissive open-source license (e.g., MIT, Apache 2.0) and commits to a public code repository.

Yes

I confirm that the team provides evidence of their technical ability and experience in creating developer tools or high-quality technical content (e.g., GitHub, portfolio).

Yes

I confirm that a plan for creating and maintaining clear, comprehensive documentation is a core part of the proposal's scope.

Yes

I confirm that the budget and timeline (3 months) are realistic for delivering the proposed tool or resource.

Yes

[Required Acknowledgements] Consent & Confirmation

I Agree

Yes