Location Proof Protocol is trying to standardize the envelope around location proofs, not dictate one privileged method for proving location.
The repository’s most useful contribution is its explicit taxonomy of strategy families: authority, social, near-field machine, network machine, and sensor-based approaches can all fit inside one broader protocol framework.
The schema-level split is what makes the project comparison-worthy. Subject, event timestamp, spatial reference system, location encoding, recipe identifiers, recipe payloads, media types, and media attachments are all separately modeled instead of buried inside one opaque blob.
The protocol is also deliberately broader than Earth coordinates. Its docs explicitly mention relative and non-Earth spatial reference systems such as metaverse space, co-presence with a person, or being inside a room/vehicle.
The implementation footprint is still early. Public materials emphasize core schema deployment and future recipe extensibility rather than a mature production ecosystem.
There is visible documentation drift around the deployed schema ID: the top-level README and schema/README.md cite different Sepolia schema UIDs, which suggests the project is still evolving its base layer.
Specific source signals worth retaining
Top-level README.md: best concise framing of the protocol’s purpose and the strategy taxonomy.
schema/README.md: most important source because it shows the actual field-level decomposition of the proof envelope and makes recipe/media extensibility concrete.
GitHub repository page: useful for understanding the project as standards-and-deployment infrastructure rather than as a full app stack.
EASScan links: useful for grounding the protocol in real deployed attestation schemas, even though the cited UID mismatch indicates churn.
Why this entry belongs in the corpus
It gives the corpus a lower-bound standards layer for proof-of-location systems, similar to how attestation or wallet-auth standards clarify stacks that later products hide.
It strengthens comparison work across Astral, Witness Chain, Offline Protocol, FOAM, and other geospatial systems by making schema design and proof-recipe extensibility first-class surfaces.
The durable insight is that location proof is not one mechanism; it is a family of mechanisms that can share a common attestation envelope if the schema is designed explicitly enough.