Glucose ZKP Reference: Private Health Data Proofs

[Proposal setup] Proposal title

Please provide your proposal title

Glucose ZKP Reference: Private Health Data Proofs

[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?

Patients must share sensitive data entirely to prove compliance e.g. to insurers.This risks total privacy loss.We lack an openSource DApp demonstrating ZKP-powered selective data disclosure for health

[Proposal Summary] Supporting Documentation

Supporting links

• https://github.com/EsubalewAmenu/Glucose-Tracker
,
• https://github.com/dataScience-Computing/
,
• https://datascienceplc.com/
,
• https://www.linkedin.com/company/datascience-computing

[Proposal Summary] Project Dependencies

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

No

Describe any dependencies or write 'No dependencies'

We'll use the currently implemented and publicly released repository to add the blockchain features.

[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

The project will be fully open source and licensed under the MIT License. All blockchain integration features, including the on-chain glucose data storage and verification functionalities, will be made available through a public GitHub repository throughout the entire project lifecycle. This ensures transparency, community contribution, and easy adoption for future enhancements.

[Theme Selection] Theme

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

Privacy

[Campaign Category] Category Questions

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

The Glucose ZKP Reference DApp provides a foundational, open-source solution for the Health vertical, addressing the critical industry need for data privacy and selective disclosure in patient-generated health data (PGHD).

The core utility is the shift from "data sharing" to "proof sharing." This is useful for enterprises and regulated systems by:

• Enabling Compliant Health Insurance/Incentives: It allows a patient to prove they have met specific criteria (e.g., maintained a 30-day average blood glucose below 180 mg/dL) to an insurer or wellness program without exposing their raw, sensitive, and personally identifiable daily readings. This solves the privacy paradox that prevents most PGHD from being used for large-scale compliance or research.

• Creating a Trustless Auditing Standard: The Compact contract establishes a verifiable, immutable Zero-Knowledge Proof (ZKP) standard for glucose data integrity. Any third party (doctor, regulator, researcher) can verify the proof on-chain to confirm the patient's compliance claim without seeing the underlying data, making the system auditable by design.

• Accelerating DeHealth Adoption: As a Reference DApp, it provides the first tangible, fully documented template for ZK-Health DApps on Midnight, attracting health-tech builders who require high assurance for privacy-sensitive applications.

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.

We will build the Glucose ZKP Reference DApp as a three-part system:

• Compact Contract:- "One file: GlucoseProof.compact. Key functions: circuit generateProof (takes private readings, public threshold) and ledger checkProof (on-chain verification of the ZKP)."
• Demo UI & Flow:- Simple React/TypeScript web app. Flow: User enters mock data → App generates ZKP locally → User signs proof transaction using the Lace (Midnight) wallet → Proof is submitted and verified on-chain.
• Test Plan:- Focus on ZKP integrity: Positive Test (inputs meet condition → Proof generates/verifies successfully) and Negative Test (inputs fail condition → Proof generation/verification fails).

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)?

The repository is structured as a clear Midnight DApp template for maximum reusability.

Repo Structure: Standard layout (contract/, ui/, cli/) for easy navigation.

Documentation:

• README.md: The entry point explaining the ZKP pattern for selective disclosure, how to run the demo locally, and deployment steps.
• Tests: Includes passing and failing sample inputs/outputs with clear instructions to run the Compact contract's test suite.

Extension Points: Builders can easily fork the code to modify the GlucoseProof.compact circuit to test new ZKP metrics (e.g., A1C estimates) or integrate with DID systems.

Beneficiaries: The Midnight Beginner (learns core stack) and The Privacy Builder (gets a reusable code pattern for conditional data verification).

[Your Project and Solution] Solution

Please describe your proposed solution and how it addresses the problem

We are proposing to build the Glucose ZKP Reference DApp, a focused software prototype to demonstrate programmable privacy in the health sector. The problem we solve is the need for patients to prove they are managing their health without compromising their total health history.

Our Approach - The ZKP Pattern: Instead of using Plutus to anchor data hashes (which is not suitable for this category), we will use Compact to implement a Zero-Knowledge Proof (ZKP) circuit. This circuit will take a patient's local glucose readings as a private input and a compliance threshold as a public input.

The output will be a proof (the ZKP) that confirms the raw data meets the threshold (e.g., "all readings were below 180") without revealing the raw readings. This proof is then submitted on-chain and can be verified by any third party.

What is Unique & Why Midnight/Compact is Essential: The uniqueness lies in the application of ZKPs to specific health-compliance scenarios. Midnight's Compact contracts provide the necessary primitives to natively construct, deploy, and verify these ZKPs. This functionality is not possible on Cardano's main chain or through basic Web2 solutions. By building this, we provide a foundational template demonstrating how the Midnight ecosystem can support compliant, privacy-preserving interactions between patients and healthcare systems.

Target Audience:

• End-Users: Diabetic patients who want to prove health metrics to a third party (e.g., health incentive programs, insurers) while maintaining full control and privacy over their raw data.
• Developer Persona: Blockchain developers learning Midnight. Our repository will serve as the clearest example of how to implement the "selective disclosure" pattern using a Compact contract for data verification.

Current Progress

A functional glucose tracker web2 app is already developed with key features including blood glucose level tracking, A1C estimates, advanced data filtering, CSV/PDF export, and email sharing of data with healthcare providers. The web application is mobile-friendly, offering an intuitive and adaptive interface for users on different devices. Additionally, the platform supports the import of glucose data via CSV, making it easy for users to manage existing data.

https://github.com/EsubalewAmenu/Glucose-Tracker

Current system - image 1 https://mpx-temp-test-bkt.s3.us-east-1.amazonaws.com/glucose-dashboard.jpg

Current system - image 2 https://mpx-temp-test-bkt.s3.us-east-1.amazonaws.com/glucose-add.jpg

This project is important to Cardano as it showcases the practical application of blockchain technology in enhancing securely records, verifies, and shares blood glucose data, contributing to the broader adoption of blockchain in diverse sectors.

[Your Project and Solution] Impact

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

Our primary impact is accelerating Midnight developer adoption by building a high-quality, open-source Reference DApp.

• Laying Foundational Code: We will create the clearest, most reusable, and fully tested code example for implementing ZKP-powered health compliance using a Compact contract. This immediately lowers the barrier to entry for hundreds of developers looking to build on Midnight.
• Demonstrating High-Value Utility: This project proves that Midnight is essential for the multi-trillion dollar DeHealth sector. The ability to guarantee data integrity and maintain privacy is the key to unlocking real-world enterprise adoption.
• Knowledge Transfer: The repository will act as a living tutorial, reducing the reliance on theoretical documentation by providing a practical, runnable example of the core privacy feature: selective disclosure.

Measuring & Sharing Impact:

Quantitative KPI: Achieve the mandatory technical baseline (Compact contract, Demo UI, Lace integration, full Test Suite).

Sharing Outputs: The project will be fully open-source under the MIT License. We will publish a brief explanatory video, a technical blog post detailing the ZKP logic, and host one developer workshop focusing on how to fork and adapt our Compact contract code for new use cases.

[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?

Our team is uniquely positioned to deliver this project due to a proven track record within Project Catalyst, deep technical expertise, and an unmatched understanding of the local African tech ecosystem. We build trust through a history of successful delivery and transparent processes.

1. A Proven Catalyst Track Record & A Clear Progression:

We are not new to Catalyst. Our journey has been a deliberate progression, making this proposal the logical next step:

• We Built the Audience: Our previously funded project, "Cardano for 100,000+ students (https://projectcatalyst.io/funds/11/cardano-open-ecosystem/cardano-for-100000-studentsgoogle )," was a massive success with over 50,000 active users, teaching us how to create and scale educational content for a huge user base in this region.
• We Built the Tools: Our "Universal DevTools" and "Enhancing Cardano Developer Ecosystem https://projectcatalyst.io/funds/11/cardano-open-developers/enhancing-cardano-developer-ecosystem-with-open-source-tooling " projects proved our technical capability to deliver complex, open-source solutions that benefit the entire ecosystem.

2. Technical Capability & Local Expertise: Our development team is comprised of senior Cardano blockchain developers, experienced Flutter app developers, and project managers based in Africa. This gives us two key advantages:

• Technical Know-How: We have the hands-on experience to build the smart contracts and integrate them into our mobile app or website.
• Local Insight: We understand the specific challenges and opportunities for Africans youth firsthand. We are not guessing what the market needs; we are part of it.

3. How We Will Validate Feasibility:

The entire project is designed as a product to validate our approach with minimal risk. Feasibility will be proven by achieving the clear, measurable KPIs outlined in our Impact section:

• Technical Feasibility: Validated by the successful issuance of 100+ beta testers on google play.
• User Desirability: Validated by achieving a 75%+ satisfaction score from our beta testers.
• Market Viability: Validated by securing a partnership, statement of interest from a local tech hub and recruiter.

4. Trust, Accountability & Fund Management:

We manage community funds with the highest level of professionalism:

• Transparent Budgeting: Our detailed budget justifies every expense, ensuring no funds are wasted.
• Milestone-Based Reporting: As with all our past projects, funds are tied to clear deliverables. We will provide comprehensive monthly updates and a detailed final closeout report to the Catalyst community.
• Open-Source Commitment: All code developed for this project will be open-sourced under an MIT license, allowing for full community inspection and accountability.

Finally, our capability is further validated by our acceptance into the Microsoft for Startups Founders Hub, providing us with significant technical resources and business support, further de-risking the project's successful delivery.

Proof image:- https://mpx-temp-test-bkt.s3.us-east-1.amazonaws.com/MS-partnership-benefits.jpg

[Final Pitch] Budget & Costs

Please provide a cost breakdown of the proposed work and resources

M1: Compact Contract & ZKP Development:- Circuit design, Rust/ZK-tooling implementation, and contract testing.

M2: Frontend, UI/UX & Lace Integration:- Building the Demo UI, connecting the Proof Server logic, and integrating the Lace wallet

M3: Testing, Documentation & Finalization:- Writing the robust README.md, developer tutorials, comprehensive Test Suite, and project close-out.

Project Management, Oversight & Reporting:- For 3-month project oversight, weekly sprint coordination, budget tracking, and final video/report production

[Final Pitch] Value for Money

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

The proposed budget provides exceptional value by delivering a foundational, high-impact technical blueprint for the health vertical. This cost is a highly efficient way to bootstrap developer knowledge and reduce the barrier to entry for the entire ecosystem.

Key Value Drivers:

1. Accelerating Developer Adoption (High ROI): The primary value is in the educational output. Instead of funding basic documentation, we are funding a functional, complex code example (a Reference DApp) that teaches developers exactly how to implement selective disclosure—Midnight's core value proposition—using a Compact contract. This dramatically accelerates the learning curve for future builders.

2. Unlocking High-Value Use Cases: This project delivers a production-ready pattern for ZK-Health applications. The ability to handle private, regulated data (like glucose) is essential for attracting enterprise-level partners and showing that Midnight is viable for the multi-trillion-dollar healthcare market. This single reference DApp demonstrates a pathway to scalable, compliant data solutions.

3. Open-Source & Reusable IP: All code is open-source under the MIT License. The investment produces a reusable Compact contract circuit that can be forked and adapted by hundreds of developers for various conditional proof scenarios (e.g., proving minimum age, credit score compliance, or license validation), maximizing the return on investment across multiple industries.

4. Specialized Tooling Cost: The budget accounts for the highly specialized skills required for Zero-Knowledge Proof circuit design and implementation in the new Midnight tooling stack (Rust/Compact), which commands a premium. We are funding expertise to solve a complex technical challenge once for the benefit of the entire community.

[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