Federation Protocol

How cross-registry queries work, how proofs are published, and how Trust Context is determined.

Proof publication

When a registry publishes a record to Landblock, it submits a signed proof to the Federation contract. The proof contains:

• A cryptographic hash of the record
• The registry's DID and signature
• The full bitemporal temporal envelope
• A conformance tier declaration
• An IPFS CID for supporting evidence (if applicable)

The proof is stored on-chain. The underlying record stays with the registry.

Cross-registry verification

When an institution (a bank, court, or another registry) wants to verify a record, it queries the Federation contract. The contract checks the on-chain proof and returns a verification result that includes a Trust Context label.

Trust Context

Trust Context tells the verifier how much confidence to place in the result:

• DIRECT_FEDERATION — the querying and publishing registries have a direct federation relationship. Highest confidence.
• SHARED_ACCREDITOR — both registries are accredited by the same authority.
• THIRD_PARTY_ATTESTATION — a trusted third party has attested to the record.
• NONE — proof is published but no formal trust relationship exists between the registries.

Federation Liaison Service

Complex cross-registry queries — those requiring data beyond the on-chain proof — are routed through the Federation Liaison Service. Three tiers:

• Tier 1 — Automated: AI-automated routing for standard queries against public or restricted data. No human involvement.
• Tier 2 — Facilitated: Registry-to-registry channel for queries requiring disclosure decisions. The receiving registry retains full authority over what it shares. Landblock facilitates but does not intervene.
• Tier 3 — Escalated: Human operators handle edge cases, disputes involving multiple registries, and queries where automated routing fails.

Dispute records

When a party or registry disputes a proof, they file a Dispute Record. The DisputeRecord contract supports three dispute types:

• Type 1 — Rights conflict (two registries assert conflicting rights to the same spatial unit)
• Type 2 — Identity conflict (disputed party identity)
• Type 3 — Proof challenge (the published proof is disputed as inaccurate)

Dispute records do not resolve disputes — that is for courts and governments. They create an on-chain notice that a dispute exists, visible to all verifiers, so that verification results can include appropriate caveats.

Registry authorities can issue injunctions via the DisputeRecord contract, applying a freeze mask to a spatial unit that suspends new rights registrations pending resolution.

Verification-as-a-service

Lenders and institutions can access Landblock verification without requiring a PropertyToken. The verification-as-a-service API returns a collateral bundle — a structured verification result linking the spatial unit, BA unit, active RRRs, and trust context — without any on-chain token issuance. Enforcement remains entirely with the registry and courts.