Last updated 4 months ago
Current talent platforms expose too much personal data. Developers must reveal identity and full history just to prove skills. There is no private way to verify qualification without over-sharing.
A DApp that stores encrypted skill profiles and uses selective disclosure so developers reveal only required skills. Projects verify fit without learning identity or unnecessary details.
Please provide your proposal title
Privacy Preserving Skill Matchmaker on Midnight
Please specify how many months you expect your project to last
3
Please indicate if your proposal has been auto-translated
No
Original Language
en
What is the problem you want to solve?
Current talent platforms expose too much personal data. Developers must reveal identity and full history just to prove skills. There is no private way to verify qualification without over-sharing.
Supporting links
Does your project have any dependencies on other organizations, technical or otherwise?
No
Describe any dependencies or write 'No dependencies'
No dependencies
Will your project's outputs be fully open source?
Yes
Please provide here more information on the open source status of your project outputs
Open Source Status: This project will be fully open source from day one. All code including smart contracts, frontend, matching logic, tests, and documentation will be published in a public GitHub repository.
License Type: The project will use the MIT License because it is permissive, easy to reuse, and aligns with the goal of providing a clear reference implementation for the Midnight ecosystem.
Please choose the most relevant theme and tag related to the outcomes of your proposal
Business Services
What is useful about your DApp within one of the specified industry or enterprise verticals?
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.
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 repo will follow a clear structure:
The README includes setup instructions, test commands, architecture diagrams, and an explanation of the selective-disclosure pattern. Developers can fork or extend the contract to support different matching logic or new proof types.
Useful for DApp builders, zk-curious developers, and integrators exploring private qualification checks.
Adoption will be measured through concrete OSS signals. Within 3–6 months after release, we target:
These metrics show whether the reference pattern is useful enough to be reused in other Compact-based DApps.
Please describe your proposed solution and how it addresses the problem
Current hiring and matching platforms force developers to expose identity, full work history, and unnecessary personal data, even when a project only needs to verify specific skills. This over-exposure creates bias and removes control from the developer.
Our solution is a privacy-preserving matching DApp where developers store encrypted skill profiles and reveal only the minimal proofs required. Projects can check whether a candidate meets skill thresholds without learning identity or underlying data. This approach directly leverages Midnight’s selective-disclosure and private-state capabilities, which cannot be replicated on a public ledger.
The project primarily engages DApp builders, zk-curious developers, and teams exploring private qualification checks. It provides a reusable reference pattern that demonstrates how Compact enables privacy-first business workflows. By showing how to implement “verify capability without revealing the data”, this project helps establish core building blocks for future Midnight applications.
Please define the positive impact your project will have on Midnight ecosystem
This project provides a practical selective disclosure pattern that allows skills to be verified without revealing the underlying data. It gives the ecosystem a clear example of how Compact can support real qualification workflows and helps future developers build privacy focused business applications.
Impact will be measured through adoption indicators such as forks, stars, downstream examples, and external issues or pull requests. A target of more than ten forks and several extensions within three to six months will demonstrate meaningful value to the ecosystem.
All outputs including contracts, the demo application, documentation, and tutorials will be released openly on GitHub. The results will be shared with the Midnight developer community through forums, Discord, and other channels to encourage reuse and further experimentation.
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 more than six years of professional TypeScript experience, along with hands on development across multiple blockchain architectures including EVM, Solana, ICP canisters, and Cosmos SDK. This background gives me a deep understanding of smart contract design, state models, and privacy oriented or zero knowledge aware workflows. Combined with production experience in Go and Solidity, I am well suited to deliver a technically complete Compact reference DApp.
My experience with Midnight is practical and recent. I participated in the Midnight London Summit Hackathon, where our team built NextMed, a privacy-preserving medical data prototype that won the Midnight Club Award. During the event, I also created lightweight developer tools for the Midnight network, including an RPC Explorer, an Indexer Explorer, and a wallet connection verification tool. Building these gave me hands-on familiarity with Compact development flows, RPC interactions, indexer queries, and the real-world behavior of the current Midnight toolchain. This direct experience significantly reduces project risk and accelerates implementation.
Feasibility is ensured through a clear three milestone plan focusing on Compact contract implementation, UI and Lace integration, and full end to end testing. Each milestone produces verifiable outputs such as working contract logic, test results, UI demos, and GitHub commits, allowing progress to be independently validated.
All development will be tracked in a public GitHub repository with transparent commit history, milestone artifacts, and documentation updates. This ensures accountability and demonstrates responsible management of project funds.
Please provide a cost breakdown of the proposed work and resources
The total requested budget covers the developer’s time required to design, implement, test, and document a fully functional reference DApp within the three-month timeline. No external services or subcontractors are used; all work is completed by a single developer.
Estimated time commitment
10–12 hours per week x 12 weeks
Total: ~120-140 hours
Hourly rate
Based on typical independent blockchain engineering rates and my experience across multiple chains (EVM, Solana, Cosmos, ICP) and six years of TypeScript development, an hourly rate of $70–$85 is reasonable for specialized Compact/Midnight work.
Cost allocation by milestone
Total Requested Budget: $10,000
Justification
This budget reflects the full development effort required to deliver a technically complete, reusable, open-source reference DApp that demonstrates the selective-disclosure matching pattern on Midnight. All deliverables map directly to the expected outputs defined for this category: contract, UI, wallet integration, tests, documentation, PoC demonstration, and final report.
How does the cost of the project represent value for the Midnight ecosystem?
The requested budget represents strong value because it produces a complete, open-source Reference DApp that demonstrates a new selective-disclosure pattern on Midnight. All costs map directly to hands-on engineering work: Compact contract development, UI and Lace integration, full test coverage, and clear documentation.
By delivering a reusable technical blueprint under a permissive license, this project lowers the barrier for future builders and accelerates ecosystem growth. The scope is efficiently executed by a single experienced developer, making the investment both cost-effective and high-impact for the Midnight ecosystem.
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
I Agree
Yes
This project will be delivered by a single developer, foxytanuki, who will be responsible for all technical and implementation tasks.