Protocol Overview
GeoProof is the verification layer built on the GEO Protocol. It provides a standard for hardware-anchored location proofs, enabling digital systems to interact with the physical world with cryptographic certainty.
By moving location verification from the software layer to the hardware layer (TEE), GeoProof eliminates the multi-billion dollar liability of GPS spoofing and location fraud on the GEO Protocol network.
How Verification Works
The GeoProof verification cycle ensures that location data is captured, signed, and validated in an untampered environment on the GEO Protocol.
01. Hardware Signing (TEE)
The GeoProof SDK communicates with the device's Trusted Execution Environment (TEE). Location signals are captured and signed using a hardware-rooted key that is inaccessible to the main Operating System.
02. Proof Generation
A GeoProof packet is created. This packet contains the coordinates, a secure timestamp, and an attestation certificate proving the signature came from a genuine secure enclave.
03. API Validation
The proof is submitted to the GeoProof Verification API, which validates the cryptographic integrity and spatial consistency of the claim using S2 spatial indexing on the GEO Protocol.
Developer Preview
The GeoProof API is currently in private alpha on the GEO Protocol. Below is the anticipated structure for location verification requests.
Verify Impression
/v1/verify/impression{
"device_id": "0x7f3a9c2e",
"proof_packet": "base64_encoded_cryptographic_proof...",
"context": {
"campaign_id": "cmp_8821"
}
}Example Response
{
"verified": true,
"verification_hash": "0x5d2f...a1b2",
"timestamp": "2026-04-29T10:12:44Z",
"spatial_index": "S2:8f3a2c"
}FAQ
Why is GPS spoofable?
Standard GPS signals are self-reported by the Operating System. Mock-location apps and emulators can inject false coordinates into the OS-level location provider, which apps then trust as real.
Why use a TEE?
A Trusted Execution Environment (TEE) is a secure area of a main processor. It runs code and stores data in an environment that is isolated from the rest of the OS. By signing location data here, we ensure that even a compromised OS cannot forge a proof.
What about privacy?
GeoProof focuses on verifying *where* an event happened, not *who* was there. We use hardware-rooted keys on the GEO Protocol to sign packets without requiring persistent identity linkage, maintaining privacy by design.
What are the current limitations?
As an alpha product, GeoProof currently requires modern mobile hardware with enclave support. Verification also introduces a small latency (~1.7s) necessary for cryptographic attestation on the GEO Protocol.