Location Proof Protocol

  • Name: Location Proof Protocol
  • URL: https://github.com/DecentralizedGeo/location-protocol-extensions
  • Category: proof-of-location standard / EAS schema layer / recipe-based geospatial attestation framework
  • Tags: ethereum-ecosystem
  • Summary: Location Proof Protocol is a schema-first location-attestation standard, not a finished network. The point is the recipe layer: one common proof envelope, many proof strategies. Useful when the comparison is about how location evidence gets represented rather than which witness stack wins.
  • What it does:
    • Defines a core data model for location proofs on top of Ethereum Attestation Service rather than prescribing one single proof method
    • Uses recipe identifiers and recipe payloads so multiple proof strategies can be represented inside one common proof envelope
    • Supports arbitrary attached media and metadata alongside the proof payload, making the schema flexible enough for heterogeneous evidence sources
    • Explicitly aims to handle both Earth-based coordinates and more relative spatial contexts such as rooms, vehicles, or metaverse spaces
    • Ships repository code and documentation oriented around deploying and interacting with the protocol’s core EAS schema on Sepolia
  • Key claims:
    • Location Proof Protocol clears the bar because it exposes a real lower-layer decomposition for location attestation: subject, event time, spatial reference system, location encoding, recipe type, recipe payload, media type, and media attachment are all kept explicit instead of hidden inside one app-specific payload.
    • The repository’s taxonomy of proof strategies is the main reason to keep it in the active corpus. It treats authority, social confirmation, near-field hardware, network triangulation, and sensor inference as interchangeable strategy families that can share a common envelope.
    • This makes the project more useful than a generic proof of location standard label. It is trying to standardize representation and extension points while leaving the actual trust model open to competing recipes.
    • The protocol also matters as an EAS-native comparison layer. Rather than building a new chain or a vertically integrated witness network, it reuses attestation infrastructure and focuses on schema design plus future recipe registration.
    • The current implementation footprint is still early and narrow. Public materials emphasize schema deployment and an in-development recipe framework more than a production ecosystem of independently adopted recipes.
    • The primary docs currently appear somewhat in flux: the repository README and schema/README.md point to different Sepolia schema UIDs, which is a useful sign that the standard is still evolving rather than settled.
    • Location Proof Protocol belongs in the active corpus because it gives a clean standards-layer baseline for later proof-of-location systems that bundle schema, witness networks, scoring engines, and application logic into one product.
  • Whitepaper: No standalone whitepaper surfaced in this pass. The strongest primary materials were the project README, schema documentation, and repository pages collected in ../../whitepapers/location-proof-protocol-primary-sources-2026-05-13.md.
  • Sources:

Internal linkages

  • Thinner base-envelope and transport-neutral precursor sitting beneath this recipe-and-schema layer: location-protocol

  • Attestation backend that explains why this note stays narrow and schema-first: ethereum-attestation-service

  • Strongest higher-level proof-stack comparison once the recipe layer stops being the point: astral-protocol

  • Last reviewed: 2026-06-05 UTC