What "Complete" Means Here
A software system is technically complete when it does what it is designed to do. The Landblock Registry Template does what it is designed to do: it accepts a jurisdiction configuration, runs LADM-compliant land administration workflows with human oversight, generates cryptographic audit trails, and produces verifiable federation proofs.
Technical completeness is a necessary condition for adoption. It is not sufficient. Governments do not deploy land registry infrastructure because a system technically works. They deploy it when they trust it — and trust is built differently from software.
What Trust Requires
For a government to trust land registry infrastructure, they need to be able to answer several questions that are not answered by a working demo:
- Who controls the protocol? If the protocol is governed by a single company, adopting it creates dependency. The Landblock Protocol DAO governs conformance standards, the global directory, and protocol upgrades. How that governance is structured and how it remains accountable matters.
- What happens if the vendor disappears? A land registry needs to function for decades. The answer here is the open-source architecture and standards-based design — a jurisdiction that has deployed the registry template owns a working system regardless of what happens to any external party.
- Has anyone independent reviewed this? Government procurement processes frequently require third-party security audits, independent legal opinions, and conformance certifications. Phase 7 includes engaging with the institutions that perform those reviews.
- Who else is using it? The answer to this question is currently: no one in production. That is the honest state. The Novaterra simulation is a reference implementation, not a production deployment. Changing that requires a first jurisdiction willing to proceed, which is the central goal of Phase 7 outreach.
What Phase 7 Is
Phase 7 is not a build phase. It is an adoption and governance phase with three parallel workstreams:
1. Technical transparency
Publishing the artifacts that allow external evaluation. This includes the simulation report, federation proof examples, architecture documentation, and this blog. The goal is to give technical evaluators everything they need to form an independent judgment without requiring a sales conversation.
2. Standards engagement
Engaging with ISO TC 211, OGC, and the UN-GGIM community where LADM and land administration standards are developed. A system that conforms to international standards is more credible than one that claims to — and participation in standards development builds the relationships through which pilot opportunities emerge.
3. Jurisdiction outreach
Structured engagement with governments, cadastral agencies, and development organizations that have identified land administration digitization as a priority. This is not cold outreach — it is presenting a concrete technical artifact to institutions that are actively looking for what Landblock provides.
Why No Production Pilots Yet Is Not a Problem
Procurement processes for government land administration systems take time. The typical timeline from initial contact to signed agreement for critical infrastructure is 12–36 months, depending on jurisdiction size, procurement rules, and political conditions. That is not a technology problem — it is the nature of government decision-making in high-stakes domains.
The absence of a production pilot today does not indicate a gap in the system. It indicates where the project is in that procurement timeline. Phase 6 completion positions Landblock at the beginning of that timeline with a working system — which is exactly where you need to be.
What Governments Are Looking For
Based on the questions that come up consistently when governments evaluate land administration infrastructure, the key concerns are:
- Can we maintain sovereign control over our records?
- Does it comply with the standards our technical community recognizes?
- Can it be audited by our own institutions?
- Will it work with our existing systems?
- What does implementation actually require — budget, staff, timeline?
The Novaterra simulation and the posts in this series directly address the first four. The fifth requires an implementation scoping conversation that is jurisdiction-specific.
If you are evaluating Landblock for a jurisdiction deployment or research context, the technical documentation is in the Landblock Core repository. For direct engagement, contact hello@landblock.app.
What This Blog Is For
This blog will continue to publish technical and governance artifacts as Phase 7 progresses — design decisions, standards alignment notes, and eventually reports from real engagement. Posts appear when there is something specific and verifiable to say, not on a schedule.
The purpose is simple: give governments, auditors, donors, and architects a place to do their homework. If a post answers a question you have, it has done its job.