[Proposal setup] Proposal title

Please provide your proposal title

Private Health Test Verifier

[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 health data for care or compliance, but doing so risks privacy breaches and misuse

[Proposal Summary] Supporting Documentation

Supporting links

• https://github.com/jyanokye
,
• https://github.com/ThePaapyK
,
• https://github.com/orgs/Cardano-Cart/repositories
,
• https://github.com/ThePaapyK/GalamseyWatch

[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 code, UI, tests, and documentation will be open source under the MIT License and hosted publicly to enable transparency, collaboration, and reuse for privacy-preserving verification.

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

Health:

• Privacy-preserving verification of health credentials (e.g., vaccination, test results) using Compact contracts.
• Enables selective disclosure: only proof is shared, sensitive data remains private.
• Provides a reference PoC for developers building privacy-first health applications.
• Demo UI at _src/frontend _allows generating and verifying proofs locally.
• Wallet integration using Lace SDK for secure signing and verification.
• Test suite at _tests/ _validates contract functionality, privacy, and edge cases.
• Developer learning resource: clear repo structure, README, tutorial, and extension points.

Architecture diagram:

User (React UI)

│

Lace Wallet Integration

│

Compact Contract (Midnight)

│

Proof Verification & Storage (hashes on Midnight blockchain)

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.

• Project: Private Health Test Verifier (PHTV)

• Overview:
• PHTV is a privacy-first decentralized application (DApp) for zero-knowledge verification of health credentials, built on Midnight blockchain using compact contracts. The system enables patients to prove health attributes (e.g., vaccination, test results) without revealing full health data, providing a secure, privacy-preserving verification flow.

---

-

• 1. Compact Contracts & Key Functions

• HealthProof.compact

• • generateProof(patientID, healthAttribute, expirationDate)
• Creates a zero-knowledge proof of a health attribute without exposing full health records.
• • verifyProof(proofHash, patientZKProof)
• Confirms the validity of a proof on-chain.
• • revokeProof(proofHash)
• Marks a proof as invalid or expired, ensuring revoked proofs cannot be misused.

• PatientRegistry.compact

• • registerPatient(patientHash)
• Stores only the cryptographic hash of patient identity.
• • checkEligibility(patientHash, attribute)
• Returns ZK verification status without revealing sensitive patient information.

---

-

• 2. Demo UI Flow

• Patient Portal

• 1. Connect via Lace wallet.
• 1. Generate zero-knowledge health proof.
• 1. View proof status (active/expired).

• Verifier Portal

• 1. Scan proof hash or QR code.
• 1. Submit for verification.
• 1. Receive confirmation without accessing full patient records.

• Optional Revocation Flow

• • Patients or providers can revoke proofs.
• • Verifiers see updated proof status instantly.

• Wallet Integration (Lace / Midnight)

• • Authenticate users and sign proof generation/verification transactions.
• • Submit ZK proofs securely to the compact contract via wallet.
• • Receive confirmations and private credentials in Midnight-enabled wallet addresses.

---

-

• 3. Basic Test Plan

• • Unit Tests: Proof generation, verification, revocation.
• • Edge Cases: Expired or invalid proofs.
• • Integration Tests: Lace wallet authentication, proof submission, UI flow consistency.
• • End-to-End Tests: Patient → Proof generation → Verifier → Proof verification → Revocation.

---

-

• 4. Usefulness (Pattern & Necessity)

• Problem Mapping

• • Patients must share health credentials without exposing sensitive medical data.

• Data Protection Patterns

• • Selective Disclosure: Only the necessary health attribute is revealed.
• • Confidential Asset Operations: Proofs act as private assets verifiable on-chain.
• • Revocation/Expiration: Proofs can be invalidated without compromising privacy.

• Why Midnight + Compact Contracts

• • Public Cardano ledger would expose all health credentials; privacy cannot be guaranteed.
• • Midnight allows private computation, selective disclosure, and ZK proof verification while maintaining blockchain integrity.
• • Compact contracts are lightweight and optimized for on-chain proof verification.

• Enhancements Over Existing Solutions

• • Introduces private, on-chain health credential verification—unlike public NFT or credential solutions.
• • Adds a building block for privacy-preserving identity verification in healthcare and other sensitive domains.
• • Extensible to insurance, travel verification, research participation, creating a reusable framework for selective disclosure.

---

-

• Summary:
• PHTV delivers a practical, privacy-first solution for health credential verification, demonstrating the power of Midnight blockchain and compact contracts while enabling real-world use cases in healthcare, travel, insurance, and research.

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

Repo Structure (Proposed):

PHTV/

├─ contracts/

│ ├─ HealthProof.compact # Core ZK proof contract

│ ├─ PatientRegistry.compact # Patient registration & eligibility

│ └─ utils/ # Helper scripts for proof generation

├─ ui/

│ ├─ patient-portal/ # React app for patients

│ ├─ verifier-portal/ # React app for verifiers

│ └─ components/ # Shared UI components

├─ tests/

│ ├─ contract-tests/ # Unit tests for compact contracts

│ └─ ui-tests/ # Integration tests for UI flows

├─ scripts/

│ ├─ deploy.js # Deployment scripts

│ └─ demo-setup.js # Sample data & test proofs

├─ docs/

│ ├─ architecture.md

│ ├─ zk-primer.md # Overview of ZK patterns & selective disclosure

│ └─ extension-guide.md # How to fork, extend, or integrate

├─ package.json

└─ README.md

README Contents

Project Overview & Motivation

• Project overview & motivation (privacy-first health verification)

Getting Started

• Setup instructions for contracts, UI, and wallet integration

Running the Demo

• Step-by-step UI walkthrough

Testing Instructions

• Unit, integration, and end-to-end tests

Extension Points

• How to add new health attributes, integrate AI, or adapt for other domains

Contribution Guide

• Issues, pull requests, coding standards

Documentation / Tutorials

• Detailed architecture explanation showing Compact contracts + ZK flows
• Tutorials on:
  • Adding a new proof type
  • Integrating another wallet or verifier
  • Extending to other privacy-sensitive credentials
• Example scripts and test cases to help developers get started quickly

Test Instructions

• Run unit tests for contracts
• Run UI integration tests
• End-to-end demo with sample proofs
• Edge case validation: expired/invalid proofs

Extension Points for Developers

• Add new health attributes (e.g., lab tests, prescriptions)
• Fork for other domains: insurance, travel, research participation
• Replace or augment ZK circuits with custom proof logic
• Integrate AI agents for enhanced UX or verification workflows

Developer Personas & Value

Identified Developer Personas

• DApp developers – learn to build privacy-first, ZK-enabled applications on Midnight
• zk-curious developers – understand selective disclosure, proof generation, and Compact contract patterns
• Integrators / API developers – integrate privacy-preserving proofs into existing health, travel, or compliance systems

How This Repo Helps Them

• Provides a complete end-to-end example of private credential verification
• Reusable building blocks: contracts, UI patterns, wallet integration, test scripts
• Documentation teaches best practices for selective disclosure and zero-knowledge proofs

Potential to Attract New Builders

• Clear, well-documented, plug-and-play structure encourages forks and remixes
• Tutorial-driven onboarding helps zk-curious developers experiment quickly
• Demonstrates practical use of Midnight Compact contracts for privacy-sensitive DApps

Measurable Impact

• Forks / stars / issues on GitHub
• Remixes or derivative projects extending PHTV to other verification use cases
• Downstream adoption metrics: references in developer forums, tutorials, or educational content

[Your Project and Solution] Solution

Please describe your proposed solution and how it addresses the problem

Value to the Midnight Ecosystem

The Private Health Test Verifier (PHTV) will create meaningful value for the Midnight ecosystem by demonstrating a practical use case for privacy-preserving, decentralized verification. By building a zero-knowledge proof (ZKP) system for health credentials, PHTV contributes in several ways:

Showcases ZKP Capabilities

PHTV provides a tangible example of selective disclosure and on-chain proof verification, highlighting Midnight blockchain’s strengths for privacy-sensitive applications.

Attracts Developers

An open-source PoC encourages developers to experiment with compact contracts, ZKPs, and decentralized verification, fostering innovation and growth within the Midnight ecosystem.

Builds Real-World Use Cases

PHTV demonstrates the feasibility of secure, decentralized health verification, potentially inspiring other applications in travel, insurance, research, or regulatory compliance.

Measuring Impact

Quantitative Metrics

• Number of proofs generated and verified through the PoC.

• GitHub repository engagement: forks, stars, issues, and pull requests.

• Number of users testing the demo UI and interacting with the system.

Qualitative Metrics

• Feedback from users, verifiers, and developers on usability and potential applications.

• Case studies documenting how PHTV could be adapted for other privacy-sensitive credentials.

Sharing Outputs and Opportunities

• Open-Source Release: Full contracts, UI, documentation, and test suite will be publicly available under the MIT license on GitHub.

• Community Engagement: Tutorials, demo sessions, and walkthroughs will be shared with the Midnight community to encourage adoption and experimentation.

• Knowledge Transfer: Insights, lessons learned, and potential extensions will be documented and shared with developers, researchers, and ecosystem participants to maximize reuse and inspire new projects.

[Your Project and Solution] Impact

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

Value to the Midnight Ecosystem

The Private Health Test Verifier (PHTV) will create meaningful value for the Midnight ecosystem by demonstrating a practical use case for privacy-preserving, decentralized verification. By building a zero-knowledge proof (ZKP) system for health credentials, PHTV contributes in several ways:

Showcases ZKP Capabilities

PHTV provides a tangible example of selective disclosure and on-chain proof verification, highlighting Midnight blockchain’s strengths for privacy-sensitive applications.

Attracts Developers

An open-source PoC encourages developers to experiment with compact contracts, ZKPs, and decentralized verification, fostering innovation and growth within the Midnight ecosystem.

Builds Real-World Use Cases

PHTV demonstrates the feasibility of secure, decentralized health verification, potentially inspiring other applications in travel, insurance, research, or regulatory compliance.

Measuring Impact

Quantitative Metrics

• Number of proofs generated and verified through the PoC.

• GitHub repository engagement: forks, stars, issues, and pull requests.

• Number of users testing the demo UI and interacting with the system.

Qualitative Metrics

• Feedback from users, verifiers, and developers on usability and potential applications.

• Case studies documenting how PHTV could be adapted for other privacy-sensitive credentials.

Sharing Outputs and Opportunities

• Open-Source Release: Full contracts, UI, documentation, and test suite will be publicly available under the MIT license on GitHub.

• Community Engagement: Tutorials, demo sessions, and walkthroughs will be shared with the Midnight community to encourage adoption and experimentation.

• Knowledge Transfer: Insights, lessons learned, and potential extensions will be documented and shared with developers, researchers, and ecosystem participants to maximize reuse and inspire new projects.

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

Demonstrated Capability

The PHTV project team brings proven expertise in blockchain development, zero-knowledge proofs (ZKPs), and front-end engineering. Our ability to deliver high-quality outcomes is reinforced by the successful completion of a previous funded project; https://projectcatalyst.io/funds/12/cardano-open-developers/cardano-ecommerce-application where we:

• Delivered all milestones.
• Delivered a fully functional proof-of-concept (PoC).
• Maintained full accountability for allocated funds.

This prior success demonstrates our technical competence, reliability, and ability to manage funded projects effectively.

Feasibility Validation

The feasibility of PHTV will be validated through a structured, multi-step approach:

1. Incremental Milestones: A 3-month plan with clearly defined milestones, proof circuit & smart contract development, UI integration with Lace wallet, and final documentation & testing ensures measurable progress at each stage.
2. Test-Driven Development: Rigorous testing of proof generation and verification, including edge cases such as invalid or expired proofs, guarantees robustness and reliability of the solution.
3. Proof-of-Concept Demonstration: A working PoC will showcase selective disclosure, blockchain proof verification, and wallet integration, providing tangible evidence of technical feasibility.

Trust & Accountability

Our prior experience managing funded projects demonstrates that we can responsibly manage resources. For PHTV, we will maintain this high standard through:

• Budget Tracking: Clear allocation of funds to each milestone and deliverable.
• Regular Reporting: Transparent updates and progress reports to stakeholders.
• Open-Source Commitment: Publicly available code, documentation, and setup guides under the MIT license.
• Version Control & Auditability: GitHub repository ensures traceable and auditable development.

Our experience, combined with structured planning, transparent processes, and technical expertise, positions us to deliver PHTV reliably, on time, and ensuring both project execution and proper stewardship of funds.

[Final Pitch] Budget & Costs

Please provide a cost breakdown of the proposed work and resources

The total funding requested for the Private Health Test Verifier (PHTV) project is $8,000 USD, allocated to cover all resources necessary for the development and implementation of the proposed project. All funds will be used exclusively for project-related activities, in accordance with Catalyst funding rules, including labour, IT/software services, materials, and production costs.

Milestone 1: Smart Contract & Public Repository (Month 1)

• Outputs: Develop zero-knowledge proof circuit and compact smart contract for secure health verification; publish public GitHub repository with initial code, test cases, and assets.
• Completion Rate: 30%
• Cost Allocation: $2,400
• Resources & Justification: Labour costs for blockchain development by the Project Lead; IT infrastructure and software for development and testnet deployment; materials costs for datasets and test assets directly used in project implementation.

Milestone 2: UI Integration & Documentation (Month 2)

• Outputs: Demo UI connected to smart contract; Lace wallet integration; updated repository with UI code, assets, and comprehensive developer documentation.
• Completion Rate: 40%
• Cost Allocation: $3,200
• Resources & Justification: Labour costs for front-end development and integration by UI/QA Lead; software/SDK resources for wallet integration; materials for UI assets and documentation creation; optional minor software licensing if required for development tools.

Milestone 3: Project Close-Out & PoC Demonstration (Month 3)

• Outputs: Complete test suite; produce Project Completion Report; record Project Completion Video demonstrating full PoC functionality.
• Completion Rate: 30%
• Cost Allocation: $2,400
• Resources & Justification: Labour costs for QA/testing and reporting; production costs for recording/editing demo video; IT/software resources for final testing and documentation; all outputs will be uploaded and publicly accessible in the repository.

Key Notes on Fund Use

• Labour & Subcontracting: Both team members are compensated for work directly contributing to project deliverables.
• Overhead Costs: Includes provision of computers, software, and IT infrastructure required to complete the project.
• Materials Costs: Any third-party materials or assets used directly in development, UI design, or PoC demonstration are covered.
• Licensing Costs: Any necessary software licenses or SDKs required for development are accounted for.
• Excluded Costs: Travel, venue hire, hackathon prizes, or bounties are not included; all funds are strictly for development and implementation.

Budget Management & Accountability

• Funding will be disbursed per milestone, ensuring transparency and tracking.
• All project outputs—including smart contracts, UI, tests, documentation, and PoC video—will be publicly accessible under an MIT license, providing verifiable evidence of responsible fund use.
• Detailed logs of resource use and milestone progress will be maintained and submitted with the Project Completion Report.

This budget ensures that all $8,000 requested is fully dedicated to the execution of PHTV, fully compliant with Catalyst fund rules, and supports the delivery of a complete, verifiable, and high-impact privacy-first health verification system.

[Final Pitch] Value for Money

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

The requested funding of $8,000 USD represents high value for the Midnight ecosystem because it is fully dedicated to building a privacy-first, zero-knowledge proof (ZKP) health verification system that demonstrates the capabilities of Midnight's blockchain and compact contracts in a real-world application.

Reasons Why This Project Represents Good Value:

1. Demonstrates Core Midnight Technology:

   PHTV will showcase selective disclosure using zero-knowledge proofs on Midnight, providing a tangible example of how sensitive data can be securely verified on-chain without exposure. This increases confidence in Midnight’s capabilities for other developers and enterprises.

2. Supports Ecosystem Growth:

   By creating an open-source repository with smart contracts, UI, test suites, and documentation, PHTV provides reusable assets for developers looking to build privacy-focused applications in healthcare, insurance, travel, or other compliance-heavy domains.

3. Encourages Developer Adoption:

   The project includes a working demo UI with wallet integration, making it easier for new developers to understand, test, and extend the framework. This lowers barriers to entry and accelerates ecosystem adoption.

4. Maximizes ROI for Funding:

   Each dollar is allocated directly to milestone-based development, testing, and documentation, ensuring transparent and accountable use of funds. The outputs are fully public, verifiable, and designed for reuse, multiplying the impact of the initial investment.

5. Real-World Impact:

   PHTV empowers users with privacy-preserving health verification, a capability with immediate societal relevance. This demonstrates that Midnight can support high-impact, privacy-sensitive applications, strengthening the ecosystem’s credibility and visibility.

In summary, funding PHTV delivers technical, educational, and social value to the Midnight ecosystem, while providing reusable open-source resources and a fully functional PoC that highlights the unique strengths of the platform. Every milestone is designed to ensure measurable, demonstrable impact, making this project a highly efficient and strategic use of funds.

[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