Real-World Real Estate Pre-Sale with Proof & Release

[Proposal setup] Proposal title

Please provide your proposal title

Real-World Real Estate Pre-Sale with Proof & Release

[Proposal Summary] Budget Information

Enter the amount of funding you are requesting in ADA

65000

[Proposal Summary] Time

Please specify how many months you expect your project to last

6

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

Real estate Pre-sales by developers lack auditable progress, standard evidence and timely certifications, causing distrust, delays and costly disputes for developers and avoidable risk for buyers

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

No

License and Additional Information

Whereas our project will not be fully open source, we will share information on every step, discoveries, and lessons learned, as well as data that might help develop other initiatives within the same industry.

[Theme Selection] Theme

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

Real Estate

[Campaign Category] Category Questions

Describe what makes your idea innovative compared to what has been previously funded (whether by you or others).

We apply enforcement-grade traceability to off-plan sales by coupling qualified digital signatures, standardized evidence and milestone-escrow smart contracts. Each step produces a tamper-evident record (hash + timestamp) on Cardano while documents remain encrypted off-chain. Releases are bound to certified progress by identified professionals. The result is a notarization-ready technical log that complements the registral system and creates a compliant path to future tokenization.

Describe what your prototype or MVP will demonstrate, and where it can be accessed.

The MVP demonstrates: developer onboarding; unit registry with metadata; reservation; KYC/AML; e-contract signature; creation of a milestone-escrow; upload of encrypted evidence linked by hashes; and automatic fund releases when certifiers sign. A hosted pre-prod (test environment) and a public GitHub repo will be available. Pilots run with a notary and two developers in CABA and Conurbano for community review and validation.

Describe realistic measures of success, ideally with on-chain metrics.

Six-month targets: ≥350 on-chain events; ≥100 document hashes anchored; ≥25 escrow releases; ≥120 unique wallets; simulated escrow value ≥₳1.6M across pilots. Off-chain: ≥25% faster from reservation to signature; ≤3% disputes; ≥70 NPS; ≥95% document completeness at each stage. Success is proven by mainnet deployment, public repos, and a notary-validated dossier ready for deed execution and registration.

[Your Project and Solution] Solution

Please describe your proposed solution and how it addresses the problem

**_Overview and rationale. _**Off-plan sales concentrate counterparty risk in long construction cycles. Our solution operationalizes trust by standardizing events and evidence, then binding capital releases to certified progress. The flow is Reserve → KYC/AML → digitally signed contract → deposit to milestone-escrow → certification by identified professionals → rule-based release. Each step emits an immutable anchor on Cardano (transaction metadata and datum transitions) while sensitive artifacts are kept encrypted off-chain, linked by cryptographic fingerprints.

Smart-contract design. We implement a Plutus V2 state-machine escrow with roles (buyer, developer, certifier, arbitrator). Releases are parameterized by milestone percentages, allowed certifier keys, and timeouts. Inline datums carry milestone states; reference scripts minimize fees; validity intervals and slot-bounded deadlines enforce responsiveness; fallback branches handle re-tests, re-inspections and refunds. A multi-signing pattern requires at least one certifier + developer acknowledgment for release, while the arbitrator path is only reachable after evidence review and timeout expiries.

Evidence and anchoring. For each milestone we derive a Merkle root over the evidence bundle (PDFs, drawings, geolocated photos/videos, site minutes, permits). The root is written on-chain and the bundle is stored encrypted (customer-managed keys). This yields tamper-evidence without exposing personal data. Document lineage (version, signer identity, timestamp) is tracked in an append-only log. Hashing prevents repudiation; encryption preserves confidentiality; authorized parties can reconstruct proofs off-chain and verify integrity on-chain.

**_Identity, signature and compliance. _**The platform orchestrates KYC/AML with a regulated provider and binds verified identities to platform roles. Contracts, minutes and certificates use qualified digital signatures (per Argentina’s e-signature law) to establish authorship and date-certainty. On-chain events provide independent time-stamping, while off-chain attestations preserve legal semantics. Data handling follows least-privilege, encryption-at-rest and encryption-in-transit; access is audited and revocable.

**_Data model and UX. _**We define canonical schemas for a Unit for Sale (UF), milestones and certifiers. The web app guides users through discovery, a project page with timeline and evidence, a comparator, favorites/alerts and a checkout that integrates reserve → KYC/AML → e-signature → escrow setup. Buyers see exactly “what was promised vs what was delivered” at each stage. Developers operate a back-office to invite certifiers, upload evidence and schedule releases. Notaries receive a dossier export (evidence index + hashes + signatures) “ready to deed”.

**_Observability and operations. _**A dedicated indexer (db-sync/Ogmios) tracks relevant UTxOs and emits analytics for dashboards: time-to-signature, release cadence, dispute rates, evidence completeness, wallet activity. Alerts notify when deadlines approach or when evidence is incomplete. Security employs static analysis of on-chain code, dependency scanning, secret rotation and WAF rules on the API. Incident playbooks define severity levels, response windows and disclosure.

Extensibility and tokenization-readiness. Although tokenization is out of scope for the 6-month MVP, the escrow and evidence rails are designed to underpin later issuance of participations via legally recognized structures (e.g., trusts or closed-end funds). The same on-chain anchors, signer attestations and evidence logs support audits, investor reporting and secondary-market enablement without re-engineering.

**_Why Cardano. _**Extended-UTxO and reference scripts favor transparent, deterministic workflows, which is ideal for long-lived escrows gated by external certifications. Low fees and high finality benefit evidence anchoring. The design patterns we publish (state machines, evidence Merkle anchoring, acceptance tests) are reusable by marketplaces, lenders and insurers building on Cardano.

Road to mainnet in 6 months. We compress delivery into three two-month stages: (1) scope, governance, whitepaper and legal fit; (2) core development—Plutus escrow, evidence pipeline, front/back end—deployed to pre-prod; (3) testing with pilot partners and mainnet go-live, with dispute/fallback drills and notary validation. Success is defined by measurable on-chain activity, working releases and high-quality documentation for community reuse.

[Your Project and Solution] Impact

Please define the positive impact your project will have on the wider Cardano community

**_Market impact. _**Buyers gain radical transparency: every promise and every certification appears on a milestone timeline, with evidence they can verify without needing to trust us or the developer. This reduces anxiety in long construction horizons, narrows the information gap and provides clear refund pathways if conditions fail. Developers transform compliance overhead into a competitive advantage—fewer back-and-forths with notaries, fewer disputes and faster cash cycles through predictable releases. Notaries receive a structured, signed dossier that shortens deed preparation and lowers the chance of missing documents.

Ecosystem impact on Cardano. The project delivers production-grade rails others can adopt: a generic milestone-escrow state machine; evidence-anchoring patterns; schemas for UF/milestones/certifiers; and operational playbooks for KYC/AML, signatures and releases. These assets reduce the time-to-market for marketplaces, lending desks, insurers and analytics providers who want to plug into real-world real estate flows. Dashboards and public metrics (events, wallets, releases, completion) improve the ecosystem’s credibility with institutions by demonstrating live usage beyond test demos.

Regulatory and institutional impact. By complementing the registral system—rather than attempting to replace it—we create a bridge that institutions can accept. Notary validation of the exported dossier shows how blockchain evidence can coexist with deeds and registration. As local capital-market rules mature, the same rails support tokenized participations with strong provenance. This careful sequencing increases the odds of sustainable adoption and avoids compliance dead-ends.

**_Measurable impact in six months. _**We target ≥350 on-chain events, ≥100 evidence hashes, ≥25 releases and ≥120 wallets across two pilots, while reducing the reservation-to-signature cycle by ≥25% and holding disputes to ≤3%. These outcomes are verifiable, attributable to Cardano infrastructure, and create a compelling signal for further builders and partners to enter the space.

**_Community benefits and openness. _**All smart contracts, interfaces and docs will be open to the community under permissive licenses. We will host technical walkthroughs and publish acceptance test suites so others can replicate or extend our approach (e.g., adding insurance conditions, lender covenants or municipal inspection feeds). The result is a shared foundation for real-world asset tooling on Cardano.

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

**_Team and governance. _**The team spans product leadership; real-estate legal (notary) to translate registral requirements into acceptance criteria; a Plutus engineer for escrow logic and audits; backend engineering for evidence hashing, time-stamping, identity hooks and APIs; frontend engineering for discovery/comparator/timeline/checkout; DevOps & Security for encryption, storage, CI/CD and monitoring; and a compliance lead to integrate KYC/AML. A steering routine (fortnightly checkpoints) tracks scope, risk and budget against milestone gates.

Feasibility approach. We validate feasibility by running production-like pilots with a notary and two developers. Each milestone has explicit acceptance tests: compile and coverage thresholds, release simulations, evidence completeness checks, dispute/fallback drills, and performance targets (e.g., median time <12 minutes from reservation to escrow creation). On-chain events act as objective proof of completion; off-chain artifacts (whitepaper, legal memo, runbooks) undergo external sign-off.

**_Risk management. _**Key risks include legal uncertainty, low user adoption, and security vulnerabilities. Mitigations: work inside today’s legal envelope (digital signatures + registral primacy), compress onboarding friction via guided flows and assisted pilots, and invest in audits, telemetry and incident response. Vendor risks (KYC provider, storage) are handled with redundancy and clear substitution procedures.

[Milestones] Project Milestones

Milestone Title

Project Scoping, Governance Decisions, Roadmap & Whitepaper

Milestone Outputs

We will produce a v1.0 whitepaper describing the end-to-end workflow (Reserve → KYC/AML → e-signature → escrow → certification → release), canonical data models for Units for Sale (UF), milestones and certifiers, and an evidence taxonomy listing required artifacts, signer roles, geolocation standards and hashing strategy, including Merkle-root anchoring. The package includes threat modeling, signature and identity policies, and privacy boundaries. Wireframes cover discovery, project detail with timeline/evidence, comparator, reputation and a guided checkout. A legal/registral memo documents current practices and how the exported dossier fits into deed and registration flows. A pilots plan (CABA/Conurbano) defines roles, metrics, acceptance tests and risk mitigations.

Acceptance Criteria

Whitepaper includes a process map, a parameterized milestone table and a complete evidence catalog; security assumptions and threat model are explicit; wireframes cover all primary flows; the legal memo defines signature standards, document custody and registral interactions; the pilots plan lists stakeholders, sample developments, metrics and escalation paths. Stakeholders (one notary and one developer) provide written sign-off. All artifacts are versioned, publicly accessible and each document hash is anchored on-chain as auditable proof.

Evidence of Completion

Published whitepaper v1.0; Figma links to all screens; legal memo PDF; pilots plan PDF; a changelog with commit history; written sign-off letters from the notary and a developer; and a list of transaction IDs showing on-chain anchoring of each artifact’s hash, plus a reproducibility note explaining how any third party can verify integrity.

Delivery Month

2

Cost

15000

Progress

20 %

Milestone Title

Core Development: Plutus Escrow, Evidence Pipeline & Product UI

Milestone Outputs

We deliver a Plutus V2 state-machine escrow with roles (buyer, developer, certifier, arbitrator), parameterized release percentages, timeouts and fallback branches for re-tests, re-inspections and refunds. Off-chain services anchor document hashes, timestamps and signer IDs; encrypted storage links artifacts via Merkle roots; a backend API exposes proof objects; the frontend guides reserve → KYC/AML → e-signature → escrow setup → evidence submission. Audit logs capture every state change. Unit and integration tests, static analysis and dependency scanning are included. A pre-prod deployment with seeded pilot data and telemetry (coverage, latency, error budgets) is available for review.

Acceptance Criteria

Contracts compile; unit tests reach ≥95% coverage across success/failure paths; escrow supports at least eight construction stages with configurable signers and percentages; signatures are verified and unsigned evidence is rejected; API returns proof objects (hash + timestamp + signer) and passes load tests; median time from reservation to escrow creation in the UI is <12 minutes; pre-prod telemetry reports state transitions; no open P1 security issues remain after remediation.

Evidence of Completion

GitHub repositories (contracts, services, frontend) with CI logs; API documentation; pre-prod URL; a recorded walkthrough demonstrating reservation → KYC → signature → escrow → evidence → release; transaction IDs for a simulated release; a security report (findings + fixes); and a runbook describing deployment, rollback and incident response.

Delivery Month

4

Cost

35000

Progress

70 %

Milestone Title

Testing with Pilot Partners & Mainnet Deployment on Cardano

Milestone Outputs

Closed pilots with one notary and two developers (CABA/Conurbano). We run real-data flows—reservation, KYC/AML, e-signature, evidence uploads—and achieve at least two releases per pilot. We execute dispute/fallback simulations (failed inspection, re-inspection, refund). We prepare mainnet go-live: contract addresses, metadata policies, governance and operational playbooks, dashboards with on-chain metrics, and an optional checklist that keeps the rails compatible with future tokenization through recognized legal vehicles, without altering today’s legal certainty.

Acceptance Criteria

At least one development per pilot onboarded; ≥10 signed contracts; ≥20 evidence packages hashed; ≥15 releases executed; document completeness ≥95%; disputes ≤3%; buyer NPS ≥70; an exportable “ready-to-deed” dossier is validated by the notary; a failed-milestone scenario is simulated end-to-end (re-inspection or refund); production incident drill executed; greenlight from legal counsel for mainnet deployment; public documentation (whitepaper v1.1, API, user guides) updated with pilot feedback.

Evidence of Completion

Pilot report with KPIs; anonymized list of transaction IDs; notary attestation letter; exported dossier for one UF (evidence index + hashes + signatures); mainnet URL and contract addresses; screenshots of dashboards showing events, wallets and releases; incident drill log with timestamps and outcomes; governance and operations runbooks published.

Delivery Month

6

Cost

15000

Progress

100 %

[Final Pitch] Budget & Costs

Please provide a cost breakdown of the proposed work and resources

The budget is milestone-tied for maximum accountability and maps 1:1 to deliverables:

Milestone 1 (Scoping, decisions, roadmap, whitepaper): ₳15,000

Milestone 2 (Core development—escrow, evidence pipeline, product UI): ₳35,000

Milestone 3 (Testing with pilots & mainnet deployment): ₳15,000

Total: ₳65,000

Functional allocation within milestones (indicative): engineering (smart contracts, backend, frontend) ₳30,000; compliance & security (KYC/AML integration, audits, telemetry) ₳8,000; product design & UX ₳6,000; legal & notary advisory ₳8,000; cloud & infrastructure (encryption, storage, observability) ₳6,000; pilots & field operations ₳5,000; community docs & dashboards ₳2,000. Totals reconcile to ₳65,000 and each line directly supports a milestone acceptance criterion.

[Final Pitch] Value for Money

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

High leverage per ADA spent. For ₳65,000 over six months, the community receives audited Plutus escrow contracts, an evidence pipeline, a legally grounded operating model, two real pilots and a mainnet deployment—plus reusable code, schemas and playbooks. Every tranche is gated by verifiable acceptance criteria and on-chain events, minimizing execution risk and moral hazard.

**_Capital efficiency and comparability. _**Building deterministic, reference-script-based state machines and Merkle anchoring on Cardano costs significantly less than implementing equivalent enforcement off-chain (custom back-office + manual controls). Our approach converts compliance checks into code paths, reducing human hours per transaction, shortening cash-conversion cycles and improving developer reputation—benefits that compound across future projects without additional Catalyst funding.

Ecosystem spillovers. Open components (contracts, APIs, acceptance tests) become building blocks for marketplaces, lenders, insurers and analytics teams. By publishing dashboards and live metrics we create credible reference data for institutional conversations, helping other proposers and companies justify Cardano as infrastructure for real-world asset rails. The same rails extend naturally to tokenized participations when regulation permits, giving the ecosystem an upgrade path at near-zero refactoring cost.

**_Risk-adjusted accountability. _**Funds are concentrated in the “lion’s share” development phase (₳35,000) but flanked by rigorous scoping (₳15,000) and a mainnet-oriented test/deploy phase (₳15,000). This structure front-loads design quality, enforces measurable outputs and ensures that only production-ready code reaches mainnet. The result is a persuasive cost-to-impact ratio: visible usage, credible partners and replicable patterns that strengthen Cardano’s position in real estate and beyond.

[Required Acknowledgements] Consent & Confirmation

Terms and Conditions:

Yes