Skip to main content
Research Preview — APIs may change. GitHub

​
Verify

The Verify service accepts a location proof and returns a verified location proof — the original proof, a credibility vector, and a signed result that can be recorded onchain as an EAS attestation. It’s a hosted implementation of the evaluation function. This page describes how the service works; the evaluation page describes what is checked and why.

​
How It Works

When a location proof is submitted to the verify endpoint:
  1. Plugin resolution — The service identifies which location proof plugins produced each location stamp in the proof and loads the appropriate verification logic.
  2. Stamp verification — Each location stamp is verified independently: signature validation, structural checks, and signal consistency assessment. Verification is plugin-specific — each plugin knows how to check its own evidence.
  3. Cross-correlation (multi-stamp location proofs) — For location proofs with multiple location stamps from independent proof-of-location systems, the service assesses independence and agreement across sources.
  4. Claim assessment — The service evaluates how well the evidence from the location stamps supports the location claim: spatial overlap, temporal overlap, and overall consistency.
  5. Credibility vector generation — The per-stamp results, correlation analysis, and claim assessment are combined into a structured credibility vector. It currently spans spatial, temporal, validity, and independence dimensions, though that structure is an open research question and will change.
All of this is designed to happen inside the TEE, so that — under attestation — the evaluation logic is attested and the signing key is protected. See the trust model for current deployment status.

​
Two Endpoints

EndpointInputOutputUse case
Verify proofFull location proof (claim + stamps)Verified location proofFull evaluation — the primary verification path
Verify stampSingle location stampStamp validity resultQuick check of a location stamp’s internal validity without a claim
The stamp endpoint is useful for confirming that a location stamp’s signatures are valid and its structure is correct — without the overhead of claim assessment and cross-correlation.

​
What Each Endpoint Returns

Verify proof returns a verified location proof containing:
  • The original proof — the location claim and location stamps as submitted
  • Credibility vector — structured assessment across (currently) spatial, temporal, validity, and independence dimensions, with per-stamp detail; the dimension structure is still evolving
  • Signed result — the verification result signed by the TEE key, independently verifiable by any downstream consumer and optionally recorded onchain as an EAS attestation
Verify stamp returns a validity result: whether signatures, structure, and signals pass their checks. A verified location proof is valuable on its own. It doesn’t need to flow into a Compute operation — many applications only need to know “how credible is this location claim?” without asking any further spatial questions.

Next: Compute

Geospatial operations inside the TEE
See also: