Evidence · Keys Experimental
Keys and authorizations.
Which keys speak for Oxyon's evidence, what each may do, and how that ends. That these addresses are Oxyon's is Oxyon's public statement, not a cryptographic fact.
How to read this page
Three different questions.
- Cryptographic validityDid this key sign what it is said to sign? Checked on each record page and by
verify_evidence.py, against the chain. This page does not re-check it. - Historical attributionWhich records and authorizations a key has been used for, per Oxyon's public index. History, not a statement about who may sign now.
- Organizational trustThat these addresses belong to Oxyon LLC is Oxyon's own public statement, on this site and in its repository. It is not a cryptographic fact, and no key here is presented as current merely because it is the latest one listed.
Keys
Keys used for Oxyon's evidence so far.
- Oxyon identity
4e881c8217945f356900eb5e9e66fcbb05da3829· signs authorizations and revocations - Anchoring key
ee9d194be80f4bafcb9e9f10f765f3afa431a8bc· commits evidence, only under an authorization
Authorizations
What the anchoring key may do.
Loading…
Revocations
Revocations.
Loading… A revocation takes effect at its own block and never invalidates evidence anchored before it.
The count above is Oxyon's index, which is Oxyon's claim. No published revocation is not proof that none exists: for each record, the verifiers scan the chain between the authorization and the anchor (the Python verifier up to 5,000 blocks, this site up to 500). A longer interval is reported as not checked, never as unrevoked. Revocation is a rule of Oxyon's verifiers, not of the XL1 protocol.
Retired
Retired keys.
Oxyon's earlier GeoProof keys can no longer sign: c2138ec4…2e39 (anchorer), 99cb3bf6…74f1 (attester) and f117e95f…a4a (verifier). Their recovery material was lost, so they could not sign a handover. Nothing links them cryptographically to the keys above. Treat anything they sign after 2026-10-09 as not Oxyon.