Problem Statement: Trusting Where Things Claim to Be
Frames proof-of-location as an attestation and verification pipeline, not a GPS logging service.
Problem statement
Design a blockchain network in which participants prove their real-world location using trusted hardware or multi-party witness checks. The ledger stores location attestations binding a subject, a place, and a time. dApps query whether a subject truly was at a given place and time. The system must resist location forgery, GNSS spoofing, sensor replay, and sybil attacks on the witness set.
A naive design signs whatever the GPS chip reports. That fails immediately: consumer GNSS receivers accept counterfeit constellation signals, software mocks can feed any coordinate to the OS, and a warehouse of cheap devices can mint unlimited fake witnesses. Therefore the core object of this system is not a coordinate but an evidenced claim: a signed bundle containing multi-source sensor evidence, a hardware attestation quote, independent witness observations that physically bound proximity, and a trustworthy timestamp. Verification is a scoring and consensus problem over that evidence, and the chain exists to make the resulting attestations immutable, auditable, and publicly verifiable.
Why the problem is distinctive
Three properties collide. First, physical truth: location is measured in the analog world, so every digital claim inherits sensor error and adversarial manipulation. Second, decentralization: no single operator may be trusted to declare where anyone was, so verification must be distributed across staked witnesses with economic penalties for lying. Third, privacy: location history is among the most sensitive personal data, so the ledger must prove presence without necessarily publishing trajectories. A strong answer separates the measurement plane (device sensors, TEE, radio ranging), the corroboration plane (witnesses, distance bounding, reputation), the settlement plane (staking, slashing, epoch commitments), and the query plane (proofs, zk selective disclosure).
Public operating baseline versus design assumptions
Public evidence shows the category is real. Helium's proof-of-coverage demonstrated radio-witness verification at roughly one million hotspots at its 2021-2022 peak. GEODNET publicly reports a decentralized RTK GNSS base-station network numbering in the thousands of stations across many countries, settling rewards on Solana. Witness Chain launched an EigenLayer actively validated service in 2024 whose witnesses verify base-station locations by radio triangulation. FOAM published proof-of-location via synchronized radio anchors measuring round-trip time, and XYO shipped a witness network with proof-of-origin heuristics. These are cited company claims, not requirements for our fictional system.
For capacity planning this answer assumes a mature network with 50 million registered subjects, 8 million daily active provers, 120 million attestations per day, 600 thousand registered witnesses with 180 thousand active, and a five-times event peak. Unless tied to a citation, every number is a stated design assumption, target, or budget.
Key Highlights
- •The atomic object is an evidenced attestation bundle, not a raw coordinate.
- •Four planes: measurement, corroboration, settlement, and query.
- •GPS alone is never sufficient: spoofing, mocking, and replay are trivial without corroboration.
- •Witnesses are staked and slashable so lying has an economic cost.
- •Public networks (Helium, GEODNET, Witness Chain, FOAM, XYO) prove the design space is operational.
Section Rescue Kit
Buzzwords to use:
Safe statements:
- "I will separate what the device measures from what the network can corroborate and what the ledger finally settles."
- "Before choosing storage, let me define the evidence bundle and the attacks each field defeats."