Offline Protocol

• Name: Offline Protocol
• URL: https://docs.offlineprotocol.com/proof-of-location/intro
• Category: proof-of-location middleware / latency-witness network / EigenLayer-secured real-world attestation / offline-first infrastructure sub-protocol
• Tags: ethereum-ecosystem
• Summary: Offline Protocol is a proof-of-location middleware stack that turns latency measurement into an onchain verification rail. The public materials describe a clean layered flow: a backend creates a location commitment, the client opens WebSocket sessions with registered operators, operators timestamp ping/pong/ack exchanges, compare measured RTT against physics-bounded latency expectations for the claimed coordinates, and then sign results into an EigenLayer-secured service-manager flow before an indexer aggregates the final proof. The useful part is the explicit split across commitment creation, operator discovery, witness operation, signature validation, AVS-backed slashing, and the offchain aggregation layer that turns many witness responses into something contracts can consume.
• What it does:
  • Lets applications request onchain verification of a user’s claimed location through a decentralized witness network rather than a single GPS or IP-geolocation oracle
  • Uses client-side WebSocket exchanges with multiple operators, where the client sends ping and ack messages and operators record timestamps with nanosecond precision
  • Has operators compute geodistance with the Haversine formula and compare measured round-trip time to theoretical latency bounds before marking a claim valid or rejected
  • Pushes signed operator responses onchain through a HelloWorldServiceManager-style task flow with AVS registry, delegation manager, and ECDSA registry components in the architecture docs
  • Exposes an end-user submission flow through id.offlineprotocol.com, where profile-linked devices can submit proofs for downstream rewards, access control, or presence validation
  • Lets third parties run operators via a packaged Docker image, which makes the witness role operationally distinct from the broader Offline Protocol consumer app stack
• Key claims:
  • Offline Protocol clears the bar because its proof-of-location materials expose a reusable mechanism rather than just a feature page: backend commitment creation, operator discovery, client latency measurement, operator-side physical-bounds checking, AVS-backed response submission, and indexer-side aggregation are all legible as separate layers.
  • The docs make this analytically stronger than a generic location oracle label. Operators do not simply attest from a privileged API; they independently measure latency and validate a claim against a speed-of-light-style lower bound plus tolerance margins.
  • The broader brand is about resilient offline communication, but the proof-of-location system is a separate control plane and is better treated that way.
  • The security model is only partly decentralized today. The architecture page explicitly includes a backend for commitment creation and operator discovery, and an indexer layer that aggregates responses into the final proof published for contract consumption.
  • The operator docs are useful because they show the protocol’s actual operational surface is thin and centralized enough to be opinionated: a Docker image, an Ethereum RPC URL, and a private key are the main operator inputs exposed in the current public docs.
  • EigenLayer-style slashing is central to the trust story, but the public docs currently describe the incentives/security posture more clearly than they describe open operator admission economics or dispute-edge cases. That itself is a useful caveat for comparison work.
  • This entry belongs in the active corpus because it gives a clean app-facing example of location verification by latency witnesses, distinct from GNSS correction networks like GEODNET and from watchtower-heavy verification stacks like Witness Chain.
• Whitepaper: No standalone Offline Protocol proof-of-location whitepaper surfaced in this pass. The strongest primary materials were the official docs pages collected in ../whitepapers/offline-protocol-primary-sources-2026-05-12.md.
• Sources:
  • https://docs.offlineprotocol.com/proof-of-location/intro
  • https://docs.offlineprotocol.com/proof-of-location/architecture
  • https://docs.offlineprotocol.com/proof-of-location/security
  • https://docs.offlineprotocol.com/proof-of-location/running-an-operator
  • https://docs.offlineprotocol.com/proof-of-location/submit-pol
  • https://docs.offlineprotocol.com/index
  • https://docs.offlineprotocol.com/tech/ecosystem
  • https://docs.offlineprotocol.com/llms.txt

Internal linkages

• Strongest upward comparison on witness-network packaging and operator brokering: witness-chain

• Higher-level stack that can consume heterogeneous proof inputs instead of only RTT witnesses: astral-protocol

• Last reviewed: 2026-06-01 UTC