What We Shipped This Week
Phase 7 is the multi-chain infrastructure phase — the work that transforms Landblock from a Polygon-native application into a genuine chain-agnostic federation protocol. This week we completed the contract layer and deployed it to Polygon Amoy testnet.
The two contracts at the center of this work are RegistryDirectory and Federation. Both have been significantly updated.
RegistryDirectory now records each member registry's anchoring chain — the blockchain where it publishes its land record proofs — as a LayerZero endpoint ID. It enforces that this chain is on the DAO-governed supported chain list before registration is accepted. And it gives the chain manager role the ability to migrate a registry's anchoring chain if needed, subject to DAO authorization. The supported chain list itself is managed entirely on-chain: chains are added and removed by governance vote, not by us.
Federation now inherits LayerZero's OApp base contract, which means it can
receive cross-chain messages directly. When a registry anchored on a secondary
chain publishes a land record proof, that proof is relayed to Polygon's Federation
contract via LayerZero and stored identically to a locally submitted proof — with
one addition: the sourceChain field records where it came from.
This is the foundation for the end-to-end cross-chain verification that is
the goal of Phase 7.
We also deployed the LayerZero OFT adapters for both the LDBK utility token and the LGT governance token earlier this week. These adapters enable token transfers across supported chains while keeping total supply consistent — tokens locked on one chain are minted on the other, and the reverse on return.
Test results: 19/19 Federation Phase 7 tests passing. 12/12 RegistryDirectory anchoring chain tests passing. All existing tests from prior phases continue to pass. One bug was caught and fixed during testing — a subtle issue with how the contract decoded the message type from a LayerZero payload. The fix was a one-line change and is now covered by a dedicated regression test.
On-chain: All 8 core federation contracts are live on Polygon Amoy. Polygon (eid 30109) and SUI testnet (eid 30336) are both registered as supported anchoring chains on the new RegistryDirectory.
Why We Are Staying on Polygon
ADR-0026, accepted this week, formally designates Polygon PoS as Landblock's primary chain. This was not a default — it was a deliberate decision, and it is worth explaining the reasoning.
When we evaluated primary chain candidates, the question was not which blockchain is technically superior in the abstract. The question was: which chain provides the best foundation for the specific requirements of a government land registry federation protocol right now?
Polygon's case was strong on every dimension that matters for us. Ten contracts are already deployed and battle-tested on Polygon Amoy — governance, tokens, paymaster, federation, identity, all of it. The entire development stack is EVM-native. The LayerZero endpoint on Polygon is mature and well-documented. Polygon's transaction costs are low enough for the volume of proof publications a real registry network will generate. And Polygon PoS is checkpointed to Ethereum mainnet, giving it a security backstop that matters when you are talking to governments about infrastructure longevity.
The alternative that received the most consideration was migrating core governance to SUI. SUI has real technical merits — its object model is well-suited to ownership-based applications, and its throughput is impressive. But migrating governance to SUI would have required rewriting all governance contracts in Move, rebuilding the DAO tooling from scratch, and asking our founding stewards to operate a completely different development environment. The cost was high and the benefit was unclear. SUI belongs in this protocol as a secondary chain — the first secondary chain — not as the primary.
Designating a primary chain is also a governance decision, not just a technical one. The DAO's voting power, the protocol constitution, and the chain manager role all live on the primary chain. Moving that to a new chain would require migrating governance itself — a process that is risky, slow, and disruptive to do mid-development. We will not move the primary chain designation lightly. Polygon earned it, and it is the right home for Landblock's core infrastructure at this stage.
The Top 12 Supported Chain List
One of the most important governance features we shipped this week is the supported chain list — the on-chain registry of blockchains that member registries can use as anchoring chains.
The list is DAO-governed. No chain gets added without a formal proposal, a deliberation period, and a vote. No chain gets removed without 180 days' notice so registries anchored there have time to migrate. The criteria are defined in ADR-0025 and evaluated across five dimensions for every candidate:
- Technical maturity — Is the chain production-ready? Does it have a stable, audited smart contract environment?
- Decentralization — Is the validator set sufficiently distributed? Is it resistant to capture by a single actor?
- Security track record — Has the chain been exploited? How did it respond? What is the history of bridge and protocol security on this chain?
- LayerZero support — Is there a deployed, live LayerZero endpoint? Have real cross-chain applications used it in production?
- Geopolitical considerations — Are there regulatory, jurisdictional, or sovereignty concerns that would make this chain problematic for government registries in certain regions?
The "Top 12" framing reflects a deliberate design choice: we are not trying to support every blockchain. We are trying to support the chains that meet a high bar across all five criteria. A smaller, higher-quality list is better for registries than a large list that includes chains with poor security histories or insufficient decentralization.
The specific chains on the initial supported list are determined by DAO vote. Polygon (30109) and SUI (30336) are the first two — Polygon as primary, SUI as the first secondary chain added by governance action. Additional chains will be proposed, evaluated, and voted on as the network grows.
For registry administrators, this framework means something concrete: you have real choice over where you anchor your proofs. If your government has a preferred blockchain — for legal, operational, or political reasons — and that chain meets the criteria, you can propose it for addition. The decision is made by the registries in the network, not by us.
What Comes Next
The contract layer is complete and deployed. The next phase of Phase 7 is the service layer — specifically, updating the Federation Liaison Service to be chain-aware. Right now the FLS routes all queries to Polygon directly. In the updated version, it will look up each registry's anchoring chain, route local queries as before, and route cross-chain queries through LayerZero with a pending state and polling endpoint for callers waiting on delivery.
After the service layer, we will tackle multi-chain indexing — making federation
events from all supported chains visible through a single unified query endpoint,
with a sourceChain field on each event so callers always know where
a proof originated.
The end-to-end test that defines Phase 7 as complete: a registry anchored on SUI publishes a proof, LayerZero relays it to Polygon, the Federation contract receives and stores it, and the FLS serves a cross-registry verification query against it — all the way through. We expect to have that running on testnet within the next few weeks.
After Phase 7: security audit, mainnet deployment, and the first live government pilot. We are in conversations with several potential pilot partners and will share more when the time is right.
A Note on Pace
We are a small team moving fast on something that needs to be right. That combination requires discipline about what "done" means. We do not call something complete until the tests pass, the deployment is verified on-chain, and the decision rationale is documented in an ADR that the DAO can review and revisit.
This week is a good example of that discipline. The contracts shipped. The tests passed. The ADRs are filed. The supported chain list is live on-chain. That is what "Phase 7 contract layer complete" means — not just that the code was written, but that it is deployed, tested, and governed.
We will keep shipping at this pace. Updates like this one will come regularly. If you want to follow along more closely, the best place is our Slack community, where the build happens in public.
Technical details are in the public documentation at landblock.app/docs, including ADR-0024 (Multi-Chain Architecture and LayerZero), ADR-0025 (Supported Chain Governance: The Top 12 Framework), and ADR-0026 (Primary Chain Designation). Join the community on Slack or reach us at landblock.app/#contact.