Midnight Wallet - Mobile First Midnight Access

[Proposal setup] Proposal title

Please provide your proposal title

Midnight Wallet - Mobile First Midnight Access

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

Users and builders lack a native mobile first Midnight wallet that securely connects both mobile apps and mobile web DApps to zero knowledge features.

[Proposal Summary] Project Dependencies

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

No

Describe any dependencies or write 'No dependencies'

This project depends on Midnight infrastructure only - a stable Midnight testnet, Compact toolchain and reference node or API endpoints provided by IOHK/Midnight. It does not depend on any third party companies or agencies to deliver the prototype, and all development will be done by me and my teammates.

[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

Yes. All outputs - the Midnight Wallet Flutter app, Flutter demo client, Compact contracts, tests and any helper libraries - will be fully open source under a permissive license (MIT or Apache 2.0) in a public repository.

[Theme Selection] Theme

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

Developer Tools

[Campaign Category] Category Questions

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

• Midnight Wallet is general purpose infra, but the reference DApp focuses on privacy preserving identity and access.
• Core pattern - a user proves they satisfy a condition (member of group, has verified attribute, over 18, employee of X) without revealing full identity or all stored data.
• The wallet holds keys and signs Compact proofs, the membership.compact contract verifies them privately on Midnight.
• This pattern is useful across multiple verticals:
  • governance - private but verifiable participation
  • finance - eligibility checks without full KYC leakage
  • health - access to records without exposing all details
  • internal or regulated apps - role or attribute based access with minimal data exposure

Developers get a concrete, end to end example of a mobile first privacy enabled access flow that they can adapt to their own sector.

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.

• Compact contract
  • contracts/membership.compact
    • Stores private membership or attribute commitments for users.
    • Provides zero knowledge proofs that a user belongs to a group or meets a condition without revealing the full member list or raw values.
    • Serves as a minimal identity and access pattern that other apps can reuse or extend.
• Midnight Wallet Flutter app
  • wallet-app/ - native, mobile first Flutter wallet for Midnight that:
    • Manages Midnight wallets, keys and addresses.
    • Shows NIGHT and DUST balances and recent transactions on testnet.
    • Presents a clear signing screen for Compact based transactions and proofs.
    • Exposes intents or app links so other mobile apps can request connection and signatures from Midnight Wallet.
• Flutter demo client (reference DApp UI)
  • demo-client/ - small Flutter app that:
    • Lets a user request access to a protected resource.
    • Calls a backend or SDK that interacts with membership.compact.
    • Uses intents or app links to hand off the signing step to Midnight Wallet.
    • Displays a simple Allowed / Denied result based on the Compact proof.
• Lace (Midnight) browser example
  • lace-demo/ - minimal web example that:
    • Connects to Lace in a desktop or mobile browser.
    • Runs the same membership proof flow against membership.compact.
    • Confirms that the Compact pattern works with both Lace and Midnight Wallet and produces the same result.
• Test plan
  • Contract tests
    • Unit tests for membership.compact covering:
    • adding and updating members or attributes
    • successful proofs for valid members
    • rejected proofs for non members or invalid data
  • Integration tests
    • Scripts or commands that drive the full proof flow against Midnight testnet.
• Manual mobile tests
  • Device level checklist for Midnight Wallet and demo-client focusing on:
    • wallet creation and import
    • signing UX
    • end to end access proof flow using intents or app links.

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
  • contracts/ - membership.compact plus contract tests.
  • wallet-app/ - Midnight Wallet Flutter project.
  • demo-client/ - Flutter reference DApp that talks to the contract and wallet via intents or app links.
  • lace-demo/ - minimal browser demo that uses Lace for the same proof flow.
  • docs/ - optional diagrams or extended guides if needed.
• README and docs
  • Root README.md will include:
    • short overview of the project and its role as a reference DApp plus wallet infra
    • privacy rationale - what is proven, what stays hidden
    • quick start for running contracts, wallet app and demo client locally
    • step by step walkthrough of the full flow:
      • run membership.compact and backend
      • start wallet-app/ and demo-client/ on device or emulator
      • connect to Midnight Wallet for signing
    • links to sub READMEs in contracts/, wallet-app/, demo-client/ and _lace-demo/ _with concrete build and test commands
  • At least one tutorial markdown file showing how to change the scenario, for example from "membership" to "age over 18" or "employee of company X", to encourage forking and remixing.
• Extension points
  • membership.compact structured so new attributes and proof types can be added cleanly.
  • demo-client/ has a clear integration layer where apps can swap in their own API endpoints or Compact contracts.
  • Wallet intent / app link scheme documented so other teams can integrate Midnight Wallet signing into their own mobile apps.
• Developer personas
  • Mobile and Flutter developers who want a working example of integrating a Midnight wallet into their apps.
  • Compact and smart contract developers who need a minimal identity or access control pattern using zk proofs.
  • Tooling and wallet builders who may reuse or extend the wallet code and the intent based integration.
• Measuring impact
  • Public signals such as GitHub stars, forks, issues and pull requests on the repository.
  • References, feedback and questions from Midnight and Cardano developer channels once the project is shared there, especially from teams that adopt the wallet or the membership pattern in their own DApps.

[Your Project and Solution] Solution

Please describe your proposed solution and how it addresses the problem

Midnight Wallet is a mobile first native wallet for the Midnight network. It will manage Midnight wallets, hold NIGHT and DUST, show balances and recent transactions, and provide a clear signing screen for Compact based interactions.

To close the current gap for builders, the wallet will expose a simple integration surface for other apps on the same device. A small companion Flutter demo client will call a Compact contract (membership.compact) and use intents or app links to hand off signing to Midnight Wallet, then display the result of an access check.

The repo will also include a minimal browser example that runs the same Compact flow using the Lace (Midnight) wallet, so developers can verify that the Compact contract and demo logic behave the same with either Lace or the native Midnight Wallet.

Together these pieces form a complete reference DApp - Compact contract, wallet, demo client, Lace example, tests and documentation. Builders can run everything locally, see exactly how the flows are wired end to end, and adapt the patterns for their own privacy focused Midnight mobile applications.

[Your Project and Solution] Impact

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

How it brings value

• Provides a focused, open source mobile wallet that is built for app integration, not just standalone use.
• Intent / app link interface plus the Flutter demo client give a ready made pattern for "call wallet for Compact flow and read back result".
• App teams can add Midnight based features without rebuilding wallet plumbing or zk UX, so more products can safely adopt Midnight.
• Over time this should make Midnight based identity and access checks feel like a normal part of mobile apps, not a separate Web3 silo.

How I will measure impact

• GitHub stars, forks, issues and pull requests on the Midnight Wallet repo.
• Install counts and basic analytics from Google Play and App Store.
• Number of projects that reference or fork the wallet or demo client as their starting point.
• Qualitative feedback from Midnight and Cardano developer channels about integrations and requested enhancements.

How outputs will be shared

• All code, tests and docs published in a public repo under a permissive open source license.
• Midnight Wallet binaries distributed via Google Play and Apple App Store so non technical users and integrators can install it easily.
• Clear quick start guides and integration docs shared in Midnight and Cardano dev communities, plus short walkthrough videos where helpful.

[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 been building mobile apps professionally for over 6 years and web applications for more than 18 years, mainly with PHP, JavaScript, TypeScript and Flutter. I already have a working proof of concept of the Flutter based Midnight Wallet, so the core approach is proven rather than theoretical and I know the patterns needed to finish it.

I attended the Midnight Summit hackathon in London, where I worked directly with the Midnight stack, Compact language and the expectations of the Midnight Foundation. For this project I will be the main builder and can collaborate with teammates who have extensive smart contract and blockchain experience, including designing and deploying production contracts on other networks.

The scope is intentionally focused and realistic for 3 months: one Midnight Wallet Flutter app, one Compact contract (membership.compact), a Flutter demo client and a Lace based browser example, plus tests and documentation. Feasibility will be validated by running everything against Midnight testnet, confirming that the same Compact flow works with both Lace and Midnight Wallet, and gathering early feedback from Midnight and Cardano developers who clone the repo and try the examples.

All work and milestones will be tracked in a public repository with tagged releases and clear reports so reviewers can see how funds are used and what has been delivered.

[Final Pitch] Budget & Costs

Please provide a cost breakdown of the proposed work and resources

Total requested budget: 10 000 USDM for a 3 month project. The distribution follows the Midnight category rules (M1 20 %, M2 30 %, M3 50 %).

Milestone 1 - Midnight Wallet MVP on testnet: 2 000 USDM

Upgrade the existing Flutter PoC into a working wallet MVP connected to Midnight testnet, with create/import wallet, balances, recent transactions and basic signing. Covers setting up the public repo structure and initial UX so other developers can already build and run the wallet.

Milestone 2 - Compact contract and external signing flow: 3 000 USDM

Main build phase. Design and implementation of membership.compact, its tests, the Flutter demo client and the external signing flow via intents or app links. Also includes the Lace browser example so the same Compact pattern works both with Lace and Midnight Wallet.

Milestone 3 - Hardening, full test suite, docs and close out: 5 000 USDM

Harden the wallet and demos based on testing, complete the test suite (contract, scripted end to end flows, manual device checks), write high quality documentation and tutorials, and produce the Project Close Out Report and demo video. Also covers preparing early distribution builds for app stores so developers can install the wallet without compiling.

The budget is primarily my development and testing time across Flutter, Compact, integration work and documentation. There are no agency fees, marketing costs or infrastructure purchases included.

[Final Pitch] Value for Money

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

This project delivers several reusable building blocks for the Midnight ecosystem for a relatively small budget:

• a working mobile first Midnight wallet that other projects can integrate or fork
• a concrete Compact example for private membership or attribute checks
• a tested external signing pattern between mobile apps and wallets
• a Lace compatibility example plus documentation that ties everything together

Any team that wants Midnight integration on mobile can start from this reference instead of spending their own time solving wallet plumbing, intents and basic Compact patterns. The time saved across multiple teams should quickly exceed the 10 000 USDM cost of funding a single, well documented reference implementation.

Because everything is open source under a permissive license, the value compounds over time: as more projects fork, report issues and contribute improvements, the wallet and examples become more polished and useful for future Midnight builders at no additional cost to the Midnight Foundation.

[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