How it works — Broker Bridge + On-Chain Escrow

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.

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.

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.

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.

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.

Fifteen minutes. Live on my laptop.

The full demo — on-device matching on a real listing index, and a complete ZKP title transfer on Xahau testnet — runs in about twelve minutes on my machine. Pick a slot and see it for yourself.