Technology · Interactive explainers

Two primitives. Deeply explained.

Most PropTech decks hand-wave on the parts that actually matter — how matches are made, and how trust is transferred. Here, you can drive both. Drag. Slide. Step through. Nothing is hidden behind a diagram.

01 On-device semantic matching 02 Zero-knowledge title transfer 03 On-screen mockups 04 Public documents
01 — Matching

Nomic Embed + cosine similarity, on the broker's device.

When a buyer sends a requirement, we don't search your database by keywords. We convert the request into a 768-dimensional semantic vector using Nomic Embed Text v1.5, then compute cosine similarity against the broker's private listing index — entirely on the broker's own laptop. No plaintext buyer brief or listing detail ever crosses the wire. The match comes back in under one second.

Below is that matching space, visualised. Each dot is a listing — nearby dots are semantically similar (location, type, price tier, amenity profile). Drag the teal query point, or pick a preset brief. The gold ring is your similarity threshold; anything inside passes. The panel on the right is the live ranked result set.

Interactive · Module 01
Semantic match space
nomic-embed-text-v1.5 · 768-D · cosine · local inference
SEMANTIC AXIS · PROJECTION 1 PROJECTION 2 QUERY
Try a buyer brief
Similarity threshold
0.85
Matches — ranked by cosine
Drag the teal query point to explore the space. For this explainer, similarity is projected into 2D for readability; in production, cosine runs on the full 768-dimensional Nomic vectors locally on the broker's device.
768
Embedding dimensions (Nomic Embed Text v1.5)
≥ 0.85
Default cosine threshold for a match surface
< 1s
End-to-end match latency on a broker laptop
0
Plaintext briefs or listings leaving the device
02 — Trust transfer

Zero-knowledge title transfer, step by step.

A counterparty needs to trust that a broker's title deed is real, issued by DLD, and covers the unit in question — without ever seeing the deed itself. That is a zero-knowledge proof, and on our stack it is not theoretical. We anchor a Xahau DocProof hash to the document, emit a cryptographic attestation, and an XRPL Hook releases escrow the moment the counterparty's verifier returns ✓.

Below is the full five-step journey, from broker signing the MOU to on-chain title transfer. Step through it, or hit auto and watch the pipeline run end-to-end with a live 3.5-second finality counter on step 5.

Interactive · Module 02
Zero-knowledge title transfer journey
Xahau DocProof · XRPL Hook · 3.5s finality
1MOU signed
2Deed verified
3Proof generated
4Counterparty ✓
5On-chain transfer
01
STEP · BROKER SIDE

Broker signs the MOU

03 — On-screen mockups

What each actor actually sees.

The interactive modules above cover how the system works. These mockups cover what it looks like in the hands of the people using it — the broker, the counterparty, the regulator, and the chain. Four screens, drawn at the fidelity we use in product specs.

Mockup · 01
Broker app — match inbox
macOS · native Rust shell
Broker Bridge · match inbox NAVIGATION ▸ Inbox Matches Escrow Listings Settings On-device gemma-2b · local BUYER BRIEF · 09:42 Marina 2BR · sea view · sub-AED 3.5M · ready Family buyer, 3-month relocation window, flexible on floor above 20. › brief hashed locally · sent as embedding only MATCHES · 4 > 0.85 COSINE Marina 2BR · Sea View · high floor AED 3.2M · Dubai Marina · ready cos 0.94 < 1.0s Marina 2BR · Boutique tower AED 2.8M · Dubai Marina · ready cos 0.91 JBR 2BR · Beachfront AED 3.5M · JBR · direct beach cos 0.88 Propose to broker →

The broker sees a ranked match list the moment a brief lands. Every score is computed on their own machine; the brief itself is hashed and never leaves as plaintext.

Mockup · 02
Counterparty — proof verified
mobile · verifier app
09:44 ••• ● BROKER BRIDGE · VERIFIER Title deed valid verified against DLD Oracle PROOF HASH 0x7a3f…b9c2 You have access to: • ✓ valid / ✗ invalid • deed contents: hidden • owner name: hidden Proceed to escrow → DEED never transmitted Zero-knowledge Xahau DocProof 32-byte attestation

The counterparty learns one bit — valid or invalid. No deed, no owner, no price history. Only the cryptographic proof crosses the wire.

Mockup · 03
Architectural cross-section
stack layers · top → bottom
LAYER 01 · BROKER DEVICE Rust core · Ollama · Nomic Embed · SQLite On-device inference · HMAC-SHA256 hashing · cosine ≥ 0.85 LOCAL Ed25519 sig LAYER 02 · PROOF LAYER Xahau DocProof · zero-knowledge attestation Generates 32-byte ZKP · statement without payload XAHAU verify(proof) LAYER 03 · SETTLEMENT XRPL ledger · Hooks (Rust / WASM) · 3.5s finality on_proof_verified() → release_escrow() → TX XRPL registry update LAYER 04 · SOURCE OF TRUTH DLD Oracle · Dubai Pulse · RERA registry Canonical title deed + property identifier + 15-min feed DLD ONE SIGNED DATA PATH

Four layers, one signed data path. Every layer is read-only or append-only — there is no writeable plaintext store anywhere in the stack.

Mockup · 04
XRPL transaction · settlement
block explorer · read-only
xrpl.brokerbridge.ae/tx/7A3F…B9C2 SETTLEMENT TRANSACTION · CONFIRMED TX HASH 7A3F0D4E…B9C2A871 ✓ FINALISED LEDGER #87,412,903 3.5s 09:44:17 GST · 22 Apr 2026 FROM · escrow account rEB7…BrokerBridge…4F2 TO · seller wallet rH4M…Seller…9D1 HOOK · on_proof_verified release_escrow(title, amount) AMOUNT · settled AED 3,200,000.00 PROOF ANCHOR xahau:docproof:0x7A3F…B9C2 · ✓ verified DLD registry: UPDATED →

A real settlement receipt: who paid whom, which Hook fired, which proof was verified, and when DLD was updated. All read-only, all public, none of the deed itself.

04 — Production UI preview

The Q3 2026 pilot build — four screens that matter most to a regulator.

These are captures from the production UI currently being built for the pilot cohort. Each screen is shown as rendered today; the visual language is being aligned with the Midnight Executive system you see on the rest of this site ahead of REES onboarding. The screens below are the four a regulator will spend most time in — matching, transacting, titling, and settling escrow.

i
Note on visual treatment

The palette of the captured screens is a pre-pilot engineering build intended for internal UX testing. It is deliberately off-brand from this pitch site — production styling sits with the REES cohort. What to read here is not the colour scheme; it is the information architecture, the compliance checkpoints, and the audit surfaces visible in every view.

Preview · 01 of 04 Layer 01 · broker-facing

Command Center — on-device matching over Dubai Pulse

The broker's landing surface. The full four-layer stack is visible in one view: Dubai Pulse live transaction feed, the on-device Semantic Matching Engine (cosine projection + vector hash), DLD Oracle status and latency in the chrome, and an active Deal Room tile tracking MOU → Deed Verified → ZKP → XRPL Hook release. The compliance mosaic sits on-screen, not in a submenu.

brokerbridge.app/command-center DLD Oracle · 15ms
Broker Bridge Command Center showing Dubai Pulse live feed, the on-device Semantic Matching Engine with a 2D cosine projection and vector hash, ranked properties including a AED 24.5M Signature Villa on Frond N, an Active Deal Room tile for a Palm Jumeirah villa with AED 12.25M in escrow, on-chain events, and a four-pillar compliance status card
1Dubai Pulse — live transaction feedSovereign pricing signal streamed directly from the authoritative source — not scraped, not inferred. The broker prices against real DLD volume and velocity.
2On-device Semantic Matching EngineCosine projection and vector hash run locally on the broker's machine. Ranked AED-denominated inventory (24.5M · 8.2M · 18.9M) is scored without any buyer PII leaving the device.
3DLD Oracle status in the browser chrome"DLD Oracle: Online · Latency 15ms" is a first-class UI element — an audit signal the regulator can read at a glance.
4Compliance mosaic, on-screenCompute: On-Device Only · Proof: ZKP Enabled · Data: DLD Oracle · Settlement: XRPL Hooks. The four pillars spelled out in the UI, reconciled against the Active Deal Room tile (MOU Signed → Deed Verified → Generating ZKP → XRPL Hook Release).
Preview · 02 of 04 Transaction workspace

Deal room — escrow funding & closing checklist

The shared surface where both agents, the buyer, and the regulator meet around a single live transaction. Designed so every pending action is visible, every completed step is time-stamped, and no one needs to email for status.

brokerbridge.app/deals/TX-8829-XRPL audit-grade
Broker Bridge deal room showing escrow funding progress, closing checklist, and real-time audit trail
1Phase tracker & blocker surfaceCurrent phase, next milestone, and any open compliance blocker — all visible in one strip.
2Closing checklistEvery required regulatory and contractual step, with who owns each action.
3On-chain escrow & DLD/RERA API statusWallet connection, NOC, escrow state — exposed as structured state, not PDF chains.
4Audit trailImmutable, timestamped record of every event — the regulator's receipt.
Preview · 03 of 04 DLD / RERA handoff

Title transfer — orchestrated DLD & RERA handoff

The highest-stakes screen for a DLD reviewer. Every form, every signature, every NOC, and every appointment is exposed — and the whole pipeline is designed to submit cleanly into the Oqood / Dubai REST flow, not around it.

brokerbridge.app/deals/TX-8829-XRPL/title-transfer DLD · RERA
Title Transfer and DLD/RERA Handoff UI showing regulatory pipeline, document requirements, and trustee appointment
1Regulatory pipelineFive-stage visualization from escrow cleared → title issued, tracking where the deal sits inside the DLD timeline.
2Document requirements checklistEach form tied to its verifier (agent, system, trustee) with its verification state.
3Trustee appointmentBuilt-in scheduling with Al Tabu Registration Trustee — no separate email thread.
4Submit to DLDSingle-action handoff; the audit log travels with it.
Preview · 04 of 04 Lean Tech · PSD2

Virtual IBAN funding — bank rails, auto-reconciled

Each transaction gets a dedicated Virtual IBAN on a regulated partner bank (Wio Business). Buyer funds are matched to the deal automatically via Lean Tech Open Banking — no manual reference fields, no reconciliation thread. The on-chain XRPL and hybrid rails remain one click away for buyers who prefer them.

brokerbridge.app/deals/TX-8829-VI/funding Lean Tech · PSD2
Virtual IBAN funding screen showing a dedicated escrow IBAN on Wio Business, Emirates NBD connected via PSD2 Open Banking, and a live Lean Tech activity feed auto-matching the incoming transfer to the deal
1Dedicated escrow IBAN per dealIssued on Wio Business (partner bank) — funds are ring-fenced to a single transaction, so commingling is impossible by design.
2Lean Tech Open Banking, PSD2-gradeBuyers connect their bank (e.g. Emirates NBD) via regulated PSD2 APIs — no card-on-file, no screen-scraping, no shared credentials.
3Auto-reconciliation, zero manual refsIncoming transfers are matched to the deal by Lean Tech webhook — the activity feed updates in seconds, and the audit trail records every state change.
4Same surface, three railsOn-chain XRPL and hybrid modes sit in the same tab strip — buyer choice, one audit log, no bespoke integration for the broker.
05 — Regulator Q&A

The questions a regulator actually asks — with direct answers.

These are the concerns DLD, VARA, and DIFC counsel have surfaced most often when the stack is described in detail. Answers are written to hold up under panel pressure, not to sound good on a slide. Appendix C of the information pack carries the full sources.

Headline question

Why Xahau today instead of waiting for XRPL mainnet?

Because Xahau is the XRPL ecosystem's production smart-contract sidechain — Hooks, Rust/WASM escrow, and ZKP document signing are live there today. On XRPL mainnet, the Hooks amendment is still listed "In Development: TBD" on the official Known Amendments page, with no activation timeline. The Boundless ZK integration announced 14 April 2026 is testnet-only and targets confidential payment values, not document attestations — a different primitive from what DocProof provides.

Choosing Xahau lets REES see a working pilot this quarter, not a 2027 roadmap. Our escrow layer is architecturally portable — xrpl-wasm-stdlib, the r-address account model, and deterministic Hook execution — so migration to mainnet Hooks is a recompile-and-redeploy, not a rewrite. No lock-in, and every Xahau escrow is already anchored to XRPL mainnet via the production bridge for settlement-grade audit trail.

Sources: XRPL.org Known Amendments (Feb 2026) · CoinDesk, Cointelegraph, The Defiant (14 Apr 2026) · Xahau 2026 roadmap · full rationale in Appendix C of the information pack.
Scope

Does this replace Oqood or MyDLD?

No. DLD portals remain the authoritative systems of record. The platform is additive — it writes a verifiable on-chain mirror and delivers cleaner, signed inputs to the existing portals. Zero portal changes are required, and the panel sees a cleaner record, not a competing one.

Positioning

How is this different from agent-productivity tools already pitching REES?

Agent-productivity platforms address the inbound leak from Instagram and WhatsApp into the broker's inbox — a valid problem. Broker Bridge + On-Chain Escrow addresses the outbound leak: broker-to-broker transmission of PII, budgets, and unit numbers — the exact supply-chain gap named in the PropTech 2033 whitepaper. Horizontal productivity versus vertical sovereign infrastructure. Complementary, not substitutable.

Security

Is on-device Ollama / Gemma secure enough for regulated flows?

The on-device model never handles KYC or any regulated personal data. It structures free-text broker notes inside the Rust runtime on the broker's own device. KYC runs through UAE Pass plus Xahau DocProof ZKP — two separate, government-grade trust domains by design.

Resilience

What happens if the DLD oracle goes down mid-transaction?

Escrow locks; it does not auto-release. The last cryptographically-valid cached valuation is honored for display only. A manual DLD override path is built in. XRPL finality is deterministic, so there is no race condition between Hook execution and oracle recovery.

Chain choice

Why XRPL / Xahau and not Ethereum?

Three reasons. Transaction cost is sub-cent versus Ethereum L1 gas volatility. Finality is 3.5 seconds, deterministic. And Ripple and Ctrl Alt already hold VARA-aligned partnerships for RWA tokenisation in Dubai. Xahau Hooks give native WASM escrow without writing a custom L1.

Capital structure

Why a PPP rather than a private raise?

Broker Bridge + On-Chain Escrow is critical national data infrastructure for Real Estate Strategy 2033 and the D33 tokenisation mandate. Anchoring DLD or DIFC in the cap table keeps sovereign IP inside Dubai, aligns regulator and operator incentives, and de-risks the sandbox. A private-only raise would leave the national-security framing unrealised.

06 — Public documents

Everything the panel sees, public on this page.

The two documents below are the complete REES submission — the 3-minute pitch deck and the 13-page regulator briefing pack. No redactions. No gate. If the whole thesis is on the page, the panel (and anyone else) can come prepared.

Document · 01
REES Pitch Deck — 28 April 2026
7 slides · PDF · Midnight Executive
Open ↗ Download
Document · 02
REES Panel Information Pack
13 pages · PDF · regulator-grade briefing
Open ↗ Download
Next step

Fifteen minutes. The product briefing.

A concise walkthrough covering the broker-facing experience, the regulatory surface, and the pilot plan. The live technical deep-dive — on-device matching on a real listing index and a complete ZKP title transfer on Xahau testnet — opens once REES confirms pilot selection and the five asks are committed.

Book a 15-min walkthrough → ← Back to overview