Last updated 3 months ago
Public chains expose transaction amounts and recipient addresses to anyone watching, which is unacceptable for many families, employers, and NGOs.
The project will build a private stablecoin remittance app on Midnight that shields transfer amounts and recipient identity at the ledger level, while keeping an encrypted.
Please provide your proposal title
zk-stablecoin remittance mini app inside messaging apps
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?
Public chains expose transaction amounts and recipient addresses to anyone watching, which is unacceptable for many families, employers, and NGOs.
Does your project have any dependencies on other organizations, technical or otherwise?
No
Describe any dependencies or write 'No dependencies'
Fiat on/off‑ramp partners or existing exchanges for converting between local currency and the supported stablecoin in target corridors
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, ensuring maximum freedom for developers and users. This license allows anyone to freely use, modify, distribute, and integrate the code into their own projects with minimal restrictions.
Please choose the most relevant theme and tag related to the outcomes of your proposal
Payments
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.
We will build
1.1. Stable Remittance Vault contract
Mint, deposit, withdraw private stablecoin commitments
Generate and verify proofs for “amount within range,” “sender owns funds,” and “no double‑spend”
1.2. Recipient Registry contract
Map blinded recipient identifiers to viewing keys and settlement addresses
Proof that a transfer targets a registered recipient without revealing their public address
1.3. Audit Access contract
Store encrypted logs and manage auditor keys
Proofs that a revealed log entry matches an on‑chain commitment and has not been tampered with
Onboard user with Lace (Midnight) wallet connection
KYC / basic registration via embedded flow (optional for demo)
2.1. “Send remittance” screen
Choose corridor, enter fiat amount, see estimated fees
App converts to stablecoin amount, prepares zero‑knowledge transfer, and submits transaction
2.2. “Track transfers” screen
Show pending and completed remittances with user‑friendly statuses, not raw addresses
2.3. “Auditor view”
Simulated regulator logs in with test key
Requests proof for a specific user or time period and sees decrypted transactions with full details
Use Lace for key management and transaction signing
Support connection flow from web and mobile demo
Display private asset balances and history in Lace where possible
Unit tests for all Compact contract functions and ZK circuits
Integration tests that run end‑to‑end send / receive flows on a local and public Midnight testnet
Negative tests for replay, double‑spend, incorrect proofs, and unauthorized audit access
Small user test with scripted scenarios for a “worker in corridor X sending to family Y”
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 main repo will be organized as
/contracts – Compact contracts and proof definitions
/circuits – ZK circuits, parameters, and tooling
/sdk – TypeScript / Rust client libraries for integrating private transfers and audit flows
/web-demo – Reference frontend with Lace integration
/docs – Architecture overview, threat model, and tutorials
/tests – Unit, integration, and scenario tests
The README will explain the problem, give a 5‑minute quickstart, and link to step‑by‑step tutorials such as “Build a private payout flow” and “Add selective disclosure for auditors.” Documentation will include diagrams of the commitment scheme, explanation of how Midnight privacy primitives are used, and clear extension points for adding new corridors, KYC providers, or fee models.
Developer personas
DApp developers who want to add private payouts to their own apps
Payment and remittance startups that need a compliant privacy layer
Researchers and protocol engineers exploring new Compact contract patterns
Impact will be measured through public metrics: number of forks and stars, issues and pull requests opened by external contributors, references or remixes in other Midnight projects, and usage of the SDK in community demos and hackathons.
Please describe your proposed solution and how it addresses the problem
The app creates a privacy‑preserving rail for stablecoin remittances on Midnight. When a worker sends funds, the system locks their stablecoin into a shielded vault and issues a zero‑knowledge commitment representing the transfer. The chain never shows the exact amount or the specific recipient address, only that a valid transfer occurred under the protocol’s rules. Recipients can decrypt their incoming funds using their viewing keys, while an optional auditor can, with consent or legal basis, decrypt selected records to check that the flows comply with local regulations.
This approach keeps everyday activity hidden from public analysis and chain‑surveillance tools, which is critical for vulnerable populations sending money home. At the same time, it avoids becoming a “black box” by maintaining a rigorously structured audit trail under the control of users and regulated entities. Midnight’s privacy model and Compact contracts make this blend of confidentiality and conditional transparency possible, and the app packages it into an experience simple enough for non‑crypto users.
Please define the positive impact your project will have on Midnight ecosystem
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 am experienced in stablecoin and payment gateway development, privacy‑focused protocols, and user‑centric wallet design. Previous work includes building production payment APIs, KYC flows, and zero‑knowledge proof systems. We will operate with transparent, public repos, milestone‑based reporting, and regular testnet deployments so the community can track progress.
Feasibility will be validated by
Please provide a cost breakdown of the proposed work and resources
Detailed cost breakdown
Covers smart‑contract and ZK design, backend APIs, SDK work, basic security review, and infrastructure scripting. At this budget level, most effort focuses on a solid testnet prototype rather than full production polishing.
Simple but clean web demo, Lace integration screens, and basic responsive layout. No native mobile build, just a browser‑based MVP.
Unit and integration tests, testnet scenarios for a small “worker → family” corridor, and bug‑fix iterations.
Concise README, quickstart guides, one tutorial, and a short recorded walkthrough for developers.
Cloud hosting for CI and test deployments, monitoring, and small operational tools.
How does the cost of the project represent value for the Midnight ecosystem?
This project is strong value for money for the Midnight ecosystem because a small grant unlocks reusable privacy tech, real user value, and clear ecosystem pull.
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
I'm a design engineer passionate about creating solutions that blend functionality with great user experience. I’ve worked on a range of projects where I focus on practical, elegant designs that solve real problems. You can check out my work and learn more from my socials.