OXYON

Evidence Experimental

Evidence you can check without trusting us.

Each record is committed on XL1, and each check runs in your browser against GitHub and XYO.

A record here says what Oxyon claims, where the data came from, and what was committed on chain. Open one, and your browser recomputes every hash, checks every signature and authorization, and refetches the source file. It also tells you what the evidence does not prove.

Oxyon is independent. Records are committed on the public XL1 network; this does not mean XYO endorses or verifies them.

Published records

Evidence records.

  1. Loading the published index…

Who may anchor

Authorizations.

 

How to read a record

Five separate questions.

  1. CommitmentXL1 recorded these exact hashes in finalized blocks. The data existed, unchanged, no later than that.
  2. SignaturesThe transactions were signed by the keys they name.
  3. AuthorizationThe signing key was authorised by Oxyon's identity, for this record, network and time.
  4. Source integrityThe committed bytes are exactly the file at a pinned GitHub commit.
  5. TruthNot established. A valid hash means the bytes are unchanged. It does not mean the numbers in them are right.