What Makes a Federation Proof Verifiable (and Why It Matters for Land Registries)

The Problem with Current Cross-Registry Verification

When a bank in one country needs to verify a land title from another country's registry, the options today are poor. Direct API access requires a bilateral agreement. Certified copies take weeks to authenticate. Data exports require knowing what format the source registry uses. All of these approaches share a common dependency: continuous trust in the source institution's availability and honesty.

This matters because land rights disputes do not wait for institutions to be available. A disputed title in a jurisdiction with irregular government services, or an ownership claim following the death of a registry official, or a cross-border land transaction involving two different legal systems — in all of these cases, the current approach fails.

What a Federation Proof Contains

A federation proof is a structured JSON document produced by a registry in response to a specific query. Its verification properties come from what it contains, not from who issued it.

The core fields of every federation proof:

• Registry identifier — the unique, persistent identifier of the issuing registry
• Registry state hash — a cryptographic hash of the complete registry state at the time of query
• Merkle root — the root of a Merkle tree over all registry records, enabling selective disclosure
• Authorizing DID — the decentralized identifier of the authority that signed the proof
• Workflow instance reference — the specific administrative process that produced the record being attested
• ECDSA signature — the cryptographic signature over the proof content
• Validity window — the time period during which the proof is considered current

Here is a representative excerpt from an ownership verification proof, abbreviated for readability:

{
  "queryId": "fed-own-2026-002",
  "queryType": "OWNERSHIP_VERIFICATION",
  "registryId": "novaterra-national-registry",
  "timestamp": "2026-04-30T10:17:30Z",
  "result": {
    "status": "VERIFIED",
    "owner": {
      "did": "did:spruce:novaterra:party:001",
      "rights": ["OWNERSHIP"],
      "restrictions": []
    }
  },
  "proof": {
    "type": "FederationProof",
    "registryState": "0x8f2a3b4c...",
    "merkleRoot": "0x3c4d5e6f...",
    "authorityDid": "did:spruce:novaterra:authority:national-registry-001",
    "workflowInstanceId": "wf-2026-001",
    "signature": {
      "algorithm": "ECDSA-secp256k1",
      "value": "0x7b3f9a0b...",
      "signedAt": "2026-04-30T10:17:31Z"
    },
    "validUntil": "2026-07-30T10:17:30Z"
  }
}

How Verification Works

An external party verifying this proof does not need to call the issuing registry. Verification proceeds in three steps:

1. Resolve the authority DID — retrieve the public key associated with authorityDid from the DID network. This is the registry's public key, published and independently resolvable.
2. Verify the signature — confirm that the ECDSA signature over the proof content is valid for the retrieved public key. If it is, the proof was issued by the registry that claims to have issued it.
3. Check the registry state hash — compare the registryState hash against the on-chain anchor published by the registry. If they match, the proof reflects a state that was anchored at the claimed time.

None of these steps require the issuing registry to be online. The proof is self-contained for the purposes of verification.

Why This Architecture Matters Specifically for Land

Land rights have several properties that make federation proofs particularly valuable:

• Permanence. Land rights are intended to persist across changes in government, institutional restructuring, and technological transitions. A proof format that requires the original institution to exist and be reachable is inadequate for this timescale.
• High-stakes verification. Courts, lenders, and inheritance proceedings all require authoritative evidence of land rights. The cost of verification failure is high. A cryptographically verifiable proof reduces the reliance on institutional trust.
• Privacy. Land ownership is sensitive personal data. The Merkle root structure allows selective disclosure — a party can prove ownership without revealing unrelated fields in the same registry record.
• Sovereignty. The proof is issued by the jurisdiction's own registry, under its own DID, with its own legal authority behind it. The Landblock protocol does not intermediate — it provides the shared proof schema that makes proofs from different registries mutually legible.

What a Federation Proof Does Not Do

A federation proof is not a legal judgment. It attests to what a registry recorded, under what process, and when. Whether that registration is legally valid in the context of a specific dispute is a question for courts, not for cryptography.

This is the correct scope. The purpose of a federation proof is to make registry records verifiable without requiring bilateral trust arrangements — not to replace legal due process.