Acre Estate's Re-Scope: The Front Door Ships First, the Vault Waits
Last week’s audit post mentioned Acre Estate in one paragraph and promised more detail later. This is that detail.
What Acre Estate actually is
Acre Estate is a tokenized real-estate platform built around three layers: an agent network that pairs Traditional Licensed Agents with Certified Blockchain Real Estate Agents, a dual-rail property-services layer that runs traditional and on-chain management side by side, and an education sandbox that walks people through Learn → Simulate → Certify → Launch before they touch anything real. The repo has a working demo of all three — Foundry contracts for an ERC-3643-lite property token that compile and pass tests, and a full Next.js frontend covering every layer on mock data and a mock wallet.
The engineering is real. The problem was what it was sitting on top of.
The part that requires becoming a securities issuer
Property tokens, under the current design, are securities. Issuing them for real means operating under Regulation D Rule 506(c) — every investor accredited, with verified proof rather than a checkbox — enforced on-chain through ERC-3643’s compliance modules and ONCHAINID identity claims. It means a Special Purpose Vehicle per property, most likely a Wyoming LLC or DAO LLC, isolating each property’s ownership and liability. And it means a regulated partner — Securitize or tZERO, still an open decision — providing the broker-dealer, transfer-agent, and trading-venue functions the project isn’t itself licensed to perform.
None of that is optional detail. It’s the actual product for the tokenization half of Acre Estate, and a small independent team doesn’t have it yet. Building the demo further without it wouldn’t make the platform more real — it would just mean more UI sitting on top of an unresolved regulatory dependency, which is exactly the kind of gap the audit was built to surface.
What we actually did about it
Split the platform along the line that was already implicit in it. The agent network, the education sandbox, and dual-rail property listings — shown for direct comparison, not sold — carry zero securities exposure. None of them require becoming an issuer, a broker-dealer, or anything requiring outside licensing. Those ship first. Live tokenized issuance becomes a distinct, later phase, sequenced behind an audited contract stack and an actual signed regulated partner — not before.
This isn’t a new decision so much as making an existing one explicit. The project’s own roadmap already sequenced things this way — foundation and education first, compliance and contracts third, live issuance last — but “we’ll get to compliance eventually” reads very differently from “the compliance-gated half doesn’t ship until the compliance is real.” Saying the second one out loud, on the site, is the actual change.
What’s real right now, and what isn’t
Real: the contracts compile, are tested, and are explicitly unaudited. The frontend runs all three layers end to end, on mock data and a mock wallet, and builds clean. That’s a legitimate demo of the architecture, labeled as exactly that.
Not yet real, and gated behind Phase 3 of the roadmap on purpose: ONCHAINID identity verification, the Securitize or tZERO integration, Chainlink CCIP for cross-chain data, the actual SPV formations, and a contract audit. None of it ships to a live audience until it’s actually there.
Why this is worth writing down
The audit post’s whole point was that a claim a technical visitor can disprove in five minutes is worse than no claim at all. The same logic applies here in the other direction: a demo that’s honest about which half of it is real is worth more than a roadmap that quietly hopes nobody asks. Acre Estate’s front door — the agent network, the education layer, the side-by-side comparison — is real enough to open now. The vault stays closed until the people licensed to run a vault are actually in the room.