OXYON
Platform / Module 03
GeoPresence
Verify location.
In development · Working check-in layer, v1.1.x
GeoPresence turns “I was there” into evidence. A check-in layer that binds an identity, a place, and a moment into a proof — with the anti-spoofing and privacy work done before anything is published.
How a check-in becomes proof
Challenge, capture, seal.
- ChallengeThe identity signs a one-use challenge — fresh, expiring, and never replayable.
- CaptureLocation is captured with its accuracy measured, not assumed.
- ValidateFreshness, accuracy bounds, and cooldowns are enforced before acceptance.
- SplitRaw coordinates stay private; the public proof carries only a location hash.
- PublishThe sealed proof joins the participant’s verifiable history.
Capabilities
What’s built.
- Signed challengesWallet-based identity across ecosystems, proven by signature — one use, then gone.
- Accuracy validationA reading that can’t meet the accuracy bar doesn’t become a proof.
- Replay resistanceFreshness windows and per-identity cooldowns close the obvious cheats.
- Privacy splitPrivate raw storage, public hash-only proofs. Presence without surveillance.
- Participation historyStreaks, awards, and leaderboard-ready stats derived from verified check-ins.
- Durable storageDatabase-backed with graceful fallback — a check-in is never silently lost.
Status
What exists today.
A working starter with the complete check-in flow: challenge issuance and validation, browser location capture, the privacy split, and participation stats. Reward adapters are stubbed and honest about it. Proof formats align with the GeoProof presence schema; anchoring rides the same path as the rest of the platform.