OXYON

Proof  /  Lifecycle

From observation to a stranger's re-check.

Real signatures. Throwaway keys. Your browser plays every part.

Three separate keys are created in memory: an observer, an independent verifier, and an anchoring service. They are gone when you close the page. Then the whole GeoProof lifecycle runs — and you decide whether someone tampers with it.

Run it

Where were you?

    What just happened

    Five steps, five different guarantees.

    1. ObserveA presence event: who, where, when — validated before anything is signed.
    2. SignThe observer's key seals it. Authorship and integrity become checkable.
    3. ReceiptA different key checks the signature first, then signs a verdict locked to the proof's fingerprint.
    4. AnchorBoth fingerprints go into a signed batch. Here it stays in your browser; in production it goes to XYO Layer One.
    5. ReplayA stranger re-validates every signature and recomputes every fingerprint — trusting no one above.
    Technical notes

    This is a direct port of the GeoProof reference lifecycle (createPresenceProof, signProof, judgeReceipt, anchor, replay) onto the same @xyo-network 7.0.11 code. Every record is an XYO payload in a signed bound witness. In the tamper case an impostor signs a different presence event after the receipt and anchor exist; the replay recomputes its fingerprint, finds no receipt and no anchor for it, and returns inconclusive — never a false verified.

    Nothing leaves your browser. The coordinates you type are only placed into the demo record.