Oxyon publishes evidence records: a claim, the data behind it, and a commitment of that data on XL1. You check a record yourself in the Evidence Explorer, in your browser. The Evidence Explorer is live.
This is verified evidence, which is different from the observed data the explorer and the API serve. The rule throughout: say exactly what a check proves, and what it doesn't.
What your browser does itself
- Hashes: the record, its batch, its authorization, each transaction and each block are re-hashed in your browser, and the source file's SHA-256 is recomputed there.
- Signatures: every transaction's and block's secp256k1 signature is validated in your browser with XYO's own SDK (
@xyo-network/sdk-protocol7.4.2, the version the chain runs). That SDK is bundled and served by oxyon.io. To avoid trusting the copy oxyon.io serves, see without Oxyon's site. - Reported, not proven: finality. A block counts as final when its height is at or below the finalized head reported by XYO's RPC. That is XYO's report; there is no independent finality rule to check.
- Inferred, not proven: who produced a block (taken to be its first signer, whose signature is checked), and which chain is canonical (as XYO's RPC and block CDN present it).
The checks, by layer
Commitment
- A pass means: the record re-hashes to the hash you opened, and its batch lists it. Each transaction re-hashes to the published hash, is on the record's chain, lists the committed hashes and elevates a
network.xyo.hashof them. It sits in a block, within its validity window, whose hash re-hashes, whose signed clock is included, and whose height is at or below the finalized head XYO's RPC reports. So the data existed, unchanged, no later than that block's signed time. - It does not mean that the data is correct.
Signatures
- A pass means: each transaction carries a valid secp256k1 signature, its first signer and sender is the expected key (the issuer for the authorization, the anchoring key for the anchor), and it re-hashes to the anchored hash. Each block's signature is valid for its first signer.
- It does not mean anything about who controls those keys. That a block's first signer produced it is an inference.
Authorization
- A pass means: the record cites this authorization. The authorization names this issuer and anchoring key, this claim type and this network. The anchor's signed time is inside the authorization's validity window. The authorization was on chain before the anchor. No revocation by the issuer was found between them (see revocation).
- It does not mean that a key is Oxyon's. That is Oxyon's public statement (keys), not a cryptographic fact.
Source integrity
- A pass means: the bytes have the committed SHA-256 and length. The source is either a public file pinned to a GitHub commit (if GitHub doesn't answer, an archived copy is used instead), or, for records that have no public file, an archived copy whose file name is its own SHA-256.
- It does not mean that the file's contents are true.
Receipts
- A pass means: each published receipt (block, block hash, signed time, producer, chain, transaction) matches what the chain says.
- It does not mean anything beyond those fields.
Truth
Never established. A valid hash proves the bytes are unchanged, not that the numbers in them are right.
Some record types add their own layer. WinLEW records, for example, are checked for member identifiers, and WinLEW airdrop records are checked against Solana.
Revocation
- Up to 500 blocks between the authorization and the anchor: every block in between is read and checked.
- A longer interval: only the blocks in which the issuer sent a transaction are checked, as listed by XYO RPC's balance history. The history is read before and after the block reads, and the two must agree. The check then depends on that history being complete, and it says so.
- If any of that can't be done, the check is not evaluated, never passed.
- Revocation is a rule of Oxyon's verifiers, not of the XL1 protocol.
Reading a result
Each check is passed, failed, or not checked. A check is not checked when a source couldn't be read, a file is missing, or a transaction is still pending (its validity window reaches above the finalized head, so it may still land; check again later).
The whole run is:
- VERIFIED: every check ran and passed, within the scope above.
- FAILED: at least one check failed.
- INCONCLUSIVE: some checks couldn't be evaluated, for example a pending transaction, an unavailable source or incomplete evidence. The checks that ran are listed.
- NOT_EVALUATED: no check could be evaluated, so nothing was concluded.
An unavailable source never produces VERIFIED, and "not checked" is never shown as "OK".
Disclosures, such as which producer included each transaction, are statements shown for transparency. They are never counted as checks. A few checks only the Python verifier can make are listed by name, and are not counted in the browser either.
Downloadable receipts
After a run, the page offers a receipt: a JSON file listing every check, its result, the disclosures, the outcome and scope, and the SHA-256 of each checking-code file as served. It is unsigned: anyone could edit it, and it proves nothing by itself. To rely on a result, re-run the checks.
Without Oxyon's site
The browser checks are served by oxyon.io. To remove that dependency, follow VERIFY.md in Oxyon's public evidence repository:
- Hashes and the other checks:
sha256sumand a verifier that uses only the Python standard library. - Signatures: the Python verifier doesn't check them. Run
verify/sigcheck.mjswith XYO's own package, installed from npm.
Independence
Oxyon is independent. Records are committed on the public XL1 network; that doesn't mean XYO endorses or verifies them.