Real-Estate Identity & Tokenization DApp on Midnight

[Proposal setup] Proposal title

Please provide your proposal title

Real-Estate Identity & Tokenization DApp on Midnight

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

Buying or renting a home forces people to overshare income, ID and documents with many strangers and platforms, and there is no clear private on-chain pattern for builders.

[Proposal Summary] Supporting Documentation

Supporting links

• https://x.com/IvanJRomeroS
,
• https://x.com/AnGPT_pe
,
• https://x.com/SenseEarn
,
• https://www.senseearn.com/

[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 produced must be under a permissive open-source license (MIT or Apache-2.0) and source available from day one.

[Theme Selection] Theme

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

Real Estate

[Campaign Category] Category Questions

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

Real-estate is one of the clearest examples of where privacy actually matters in everyday life. A single transaction can involve passports, bank statements, pay slips, ownership deeds, addresses and contact details. Today this information is copied again and again across email threads, messaging apps and centralized portals.

Our DApp shows how Midnight can change that.

Instead of sending private information everywhere, we model a simple privacy-first real-estate flow on the Midnight test network, where:

• Properties are represented on-chain, but only non-sensitive information is visible.
• Buyers or tenants prove that they “fit” the requirements (for example, income range or residency) using privacy-preserving techniques, without revealing the underlying data.
• Both sides stay private until there is a mutual decision to move forward.

This is useful for the finance / Real World Assets (RWA) space because it:

• Demonstrates how tokenized assets can be handled without exposing all details to the world.
• Shows regulators and institutions a path to compliant, privacy-respecting real-estate platforms.
• Provides a concrete example that banks, notaries, agents and future builders can understand and extend.

Our key: a reference DApp that others can run on Midnight testnet, play with, and then adapt for their own ideas.

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 a three-module reference DApp running on the Midnight test network:

a) Identity Module

This module handles how people and organizations are represented.

• Each participant (property owner, buyer/tenant, agent, etc.) will be represented as a certificate that contains private information.
• We will explore two options, depending on the status of Lace and Midnight’s roadmap at the time of development. Option 1: Use decentralized identifiers (DIDs) and verifiable credentials (VCs) integrated with Lace. Option 2: Use a simpler, custom identity layer where we issue our own certificates for the PoC.
• The exact choice will be made during development to keep flexibility and align with Midnight’s evolution.

b) Tokenization Module

This module handles how properties appear on Midnight.

• Each property is represented as a token (NFT) on Midnight testnet.
• Some parts of the property description are public (for example: region, type of property, high-level description).
• Other details remain private (for example: exact address, identity of the owner, sensitive documents).

c) DeFi / Marketplace Logic Module

This module handles basic matching logic and regulatory-friendly flows.

• It creates a simple marketplace where owners can list properties and potential buyers/tenants can express interest.
• Private information is preserved during interactions; only what is needed for matching is revealed.
• The emphasis is on showing how privacy-preserving, rule-based matching can be built on Midnight, without locking ourselves into one rigid workflow.

Development structure (3 stages)

1. Smart contracts and unit testing

• Implement the basic logic for identity, tokenization and marketplace matching in Midnight’s smart contract language.
• Write unit tests to check the core behaviours.

1. Contract APIs, providers and text-based interface (TUI)

• Expose simple APIs for interacting with the contracts using available providers (node, indexer, proof server where applicable).
• Build a basic text-based interface (command line / TUI) to test the flows end-to-end, even before a web UI exists.
• Run integration tests at this stage.

1. Web UI (React) and wallet integration

• Build a small React web interface that talks to the contract APIs.
• Integrate a web browser wallet (Lace for Midnight) so users can connect, list properties and apply to them on the test network.
• Keep the UI minimal but clear, focused on demonstrating the concept.

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

This project is designed from the start as a learning tool and not as a startup product.

Developers will be able to:

• Clone the repo and run it locally against the Midnight test network.
• Inspect how the three modules (Identity, Tokenization, DeFi logic) are arranged at a conceptual level.
• Follow the development progression: smart contracts + unit tests, APIs + providers + TUI, web UI + wallet integration.

We will keep the structure simple and well documented:

• A clear README explaining: What the DApp does in plain language, why privacy is important in real-estate, how to run the contract tests, how to use the text-based interface, and how to start the web UI and connect with a wallet.
• Comments and short guides showing where a developer could: Replace our simple certificates with a more advanced DID/VC system, change the property fields or matching rules, and adapt it to other types of assets.

We will look at impact through:

• Stars and forks on GitHub.
• Issues and pull requests from other builders.
• Mentions or reuse in later Midnight / Catalyst proposals (“built on top of the real-estate reference DApp”).

[Your Project and Solution] Solution

Please describe your proposed solution and how it addresses the problem

When dealing with property, people share private information too early. We want to protect personal data with an alternative model using Midnight, where:

• Owners publish just enough information to attract interest, but sensitive details stay protected.
• Buyers/tenants prove they meet certain conditions without disclosing their entire financial history.
• Both sides only share identities and documents once there is a clear mutual interest.

We do not lock ourselves into one complex workflow. Instead we:

• Build a simple, understandable example on Midnight testnet.
• Focus on human concepts: “list property”, “show interest”, “prove eligibility”, “agree to move forward”.
• Keep the technical details inside the three modules, which are explained at a high level.

This approach makes the DApp easier for thousands of voters to understand and gives the development team enough flexibility to adjust the inner design as the Midnight ecosystem evolves.

[Your Project and Solution] Impact

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

The project provides Midnight with:

• A flagship reference DApp in the real-estate / finance space, showing a real-life use case where programmable privacy matters.
• A clear example for new developers of how to: Think about identity in a privacy-preserving way, tokenize real-world assets with a mix of public and private data, and build simple matching logic that respects user privacy.
• A natural starting point for many future projects: private rentals, collateralized loans, property registries, or other RWA ideas.

By keeping the DApp open and easy to understand, we help more builders feel confident exploring Midnight and reusing patterns in their own proposals.

[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 combines technical delivery and financial discipline.

Iván Romero – Project Lead & Technical Architect

PhD in Science (Germany), Master’s in Renewable Energy (Sweden) and Electronic Engineering (Peru). Iván has experience building full-stack web platforms and IoT systems, and has worked with modern web tools, authentication systems and blockchain integrations.

For this project he will:

• Lead design and implementation of smart contracts and tests.
• Build and integrate the APIs, TUI and React web interface.
• Implement wallet integration on Midnight testnet and maintain code quality.

Angelica Rojas – Finance & Operations

MBA (Germany) and Accountant (Peru) with experience in treasury management, financial control and reporting. Angelica ensures that:

• Ensure the liquidity of the project by allocating the necessary resources to each milestone and monitoring their efficient use.
• Financial reports to Catalyst and the Midnight Foundation at any time when required or at the end of each milestone.

The team has previously delivered the SenseEarn pilot (www.senseearn.com) and built up a small community around it, proving we can ship working software and communicate progress.

To validate feasibility and maintain trust:

• We will provide GitHub and X profiles in the final proposal so reviewers can verify our history.
• All core work will be done directly by us, not outsourced.
• The repo will be public from the beginning, with a permissive license.
• We will start by validating a minimal flow on the Midnight test network, then gradually layer on functionality.
• We will share regular updates (code tags, short videos, written summaries) so progress is visible.

[Final Pitch] Budget & Costs

Please provide a cost breakdown of the proposed work and resources

Total requested: 10,000 USDM for 3 months.

• Milestone 1 (Month 1): 3,000 USDM

• Milestone 2 (Month 2): 3,500 USDM

• Milestone 3 (Month 3): 3,500 USDM

The budget covers:

• Smart contract design and implementation.

• API layer, TUI and integration tests.

• Web UI development, wallet integration and documentation.

There are no marketing or outsourcing costs; it is purely for building and documenting the reference DApp.

[Final Pitch] Value for Money

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

For 10,000 USDM, Midnight gains:

• A clear, practical example of how to handle a real-world asset (property) with programmable privacy on testnet.

• A reusable, open-source learning resource that future teams can fork and adapt, saving time and avoiding repeated basic work.

• A demonstration that is understandable to non-technical people while still being useful for developers.

The cost is modest compared to the number of future projects that can reuse the patterns and code. It helps turn Midnight’s privacy vision into something people can actually see, run and build on.

[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