OXYON
Products / Module 01
GeoProof
Verify evidence.
Standard v1 is written, implemented and signed. The specification is not published yet; the signed records are. Status board
What it is
One shared language for evidence.
GeoProof defines how an observation becomes evidence a complete stranger can verify — without trusting the observer, the verifier, or Oxyon itself. Every product emits the same kind of record, so evidence from one app can be checked and connected by any other.
Oxyon is the company; GeoProof is the protocol. It is today's best expression of the belief, not the belief itself.
The lifecycle
One path, every proof.
- ObserveAn event is captured as a structured, validated record.
- SignThe observer signs it. Authorship and integrity are now checkable.
- ReceiptAn independent verifier judges the proof and issues a signed receipt, locked to it by fingerprint.
- AnchorThe fingerprints of proof and receipt are batched for a permanent shared record.
- ReplayA stranger recomputes every fingerprint and signature — and reaches the same conclusion alone.
What the standard defines
Proofs a stranger can check.
- Canonical schemasOne namespace for every event type —
oxyon.geoproof.*. - Signed observationsEvery record carries its author and is sealed against modification.
- Independent receiptsVerification is a separate, signed act — never the observer grading their own work.
- Hash-linked custodyReceipts bind to the exact proof they judged. Swaps and edits break the link.
- Independent replayThe full verification is reproducible from the published records alone.
- Tamper evidenceA substituted or altered proof yields “inconclusive” — never a false “verified.”
- Change over timeSupersession, revocation and key rotation keep history intact when the truth changes.
Built on XYO, not reinventing it
GeoProof events are XYO payloads, carried in signed XYO bound witnesses. The protocol defines the application-layer schemas and the verification rules; the cryptography is XYO's. Anchoring targets XYO Layer One. The protocol itself is defined independently of any single network (Law V — the mission outlives the methods).
The specification and reference standard are not published yet. What is published: the event types, the record anatomy, and Oxyon's own signed records. Developer overview →
Where it stands
What exists today.
Built
- Standard v1: eight event types — event, presence, attestation, receipt, anchor batch, supersession, revocation, key rotation
- A reference implementation of the complete lifecycle with a passing verification suite
- Conformance test vectors
- Signed provenance records for the standard itself, under durable company keys
Usable today
- Verify the standard's own signed records in your browser
- Run the full lifecycle with throwaway keys in your browser
Experimental
- An MCP server that gives AI agents GeoProof as tools (internal)
Next
- Anchor proof batches on XL1 instead of local batches
- Decide when to publish the specification and reference standard
Connects to
- XYO ProtocolPayloads and bound witnesses.
- XYO Layer One (XL1)The public chain for anchoring.
- GeoProof Standard provenanceOxyon signs its own standard.
- Oxyon core contractsOne decision format across products.