Proof
Don't take our word for it.
If something can be demonstrated safely, it is demonstrated here.
Every demonstration on this page runs in your browser. Nothing you type is sent anywhere, no account is needed, and the cryptography is the same code the GeoProof reference standard runs on.
Four things to try
Generate. Verify. Replay. Protect.
Want the format itself? Inspect the record types →
Generate
Fingerprint an observation.
A fingerprint (a SHA-256 hash) is the starting point of every proof. It is tiny, it is unique to the exact input, and it cannot be run backwards. Change one character and it changes completely.
A fingerprint alone is not a proof
A fingerprint shows that something hasn't changed — not who said it, or whether anyone checked it. A GeoProof record adds the rest: the observer's signature, where and when, an independent receipt locked to the fingerprint, and an anchor that makes the record public and permanent.
Human-readable and machine-readable
The same record, read two ways.
A person should be able to read a proof. A machine should be able to check it. This is a real record — the receipt Oxyon's verifier key issued for the GeoProof Standard.
verification receipt- What
- A verdict on one exact attestationLocked to it by fingerprint
- Verdict
- VerifiedEarned: the attestation's signatures were checked first
- Who judged
- Oxyon verifier keyA different key from the one that signed the attestation
- When
- 5 July 2026, 03:07 UTC
- Check it
- Replay it yourself →
oxyon.geoproof.receipt.v1{
"schema": "oxyon.geoproof.receipt.v1",
"proofHash": "6fc31c70932ff66a81e0c3db4a4ceb45
de310b57149d9e22bc6133db2d0c6896",
"verifier": "f117e95f8e7e4422c0d4967293d7599f42911a4a",
"verdict": "verified",
"verifiedAt": 1783220827911
}
Across the ecosystem
What can be checked, and by whom.
This covers everything Oxyon and WinLEW let you check today, including the demonstrations above. Some checks you re-run yourself from public data; others a service runs for you. Each item says which.
Check it yourselfRe-run it from public data. No account, and no need to trust us.
-
- What
- That the GeoProof Standard v1 files are exactly the ones Oxyon signed.
- Limit
- Oxyon's keys come from one organisation: this shows process integrity, not third-party independence.
How it is checked
- How
- Your browser replays every fingerprint and signature in Oxyon's published record.
-
- What
- What a transaction or signature request will actually do, before you approve it.
- Limit
- It explains a request; it cannot vouch for the site that sent it.
How it is checked
- How
- GeoShield decodes the request on your own device, before the wallet signs anything.
-
- What
- That GeoHackers recorded a wallet verification, faucet send or community proof on XL1, and that the record is unaltered.
- Limit
- The wallet's own signature is checked by the GeoHackers bot; the chain holds the bot's signed result, not a replay of that check.
How it is checked
- How
- Each is a signed XL1 transaction. Oxyon's XL1 Proofs page recognises them and re-checks their signatures in your browser.
-
- What
- That a cash-out from the game was paid.
- Limit
- Whether a round was really played is checked by the arcade's server. The ranked replay that would let a score be re-derived from its moves (Proof of Trick) is in development.
How it is checked
- How
- Every arcade payment is an XL1 Mainnet transaction from the arcade's distributor wallet, and the arcade page publishes its earned and paid totals.
-
- What
- That an XL1 block or transaction is intact and signed by the address it names.
- Limit
- Producer names come from an evidence-backed registry; owners that are not established are shown as Other.
How it is checked
- How
- Press Verify: your browser recomputes the hashes and checks the signatures with XYO's open-source libraries.
-
- What
- An evidence record's commitment, signatures, authorisation and XL1 Sequence receipts.
- Limit
- Proves integrity and provenance, not that the claim inside the record is true.
How it is checked
- How
- Every check re-runs in your browser, reading the record from GitHub and the chain from XYO directly.
-
- What
- That a cash-out was paid, and how much the arcade has earned and paid in total.
- Limit
- Whether a round was really played is checked by the arcade's server. The chain holds the payment, not a replay of the game.
How it is checked
- How
- Every payment is an XL1 Mainnet transaction from the arcade's distributor wallet, visible in XYO's explorer; the arcade page publishes the earned and paid totals.
-
- What
- WinLEW's token supply, burns, pools and locks.
- Limit
- Only as complete as the sources WinLEW links; a figure without one is shown as unavailable, not guessed.
How it is checked
- How
- Follow each figure to the on-chain account or transaction behind it, in a public Solana explorer.
Checked for youThe service runs the check and shows you the result. Useful, but you are trusting the service.
-
- What
- That you control the wallet you link to your WinLEW account.
- Limit
- A private account link, not a public record: only WinLEW holds it and can check it.
How it is checked
- How
- You sign a one-time challenge (never a transaction). WinLEW's server checks the signature and records the link.
-
- What
- Your participation score and tier.
- Limit
- The method is public; your records are private to your account, so only you see your breakdown.
How it is checked
- How
- WinLEW's server recomputes it from your quiz, faucet, game and verification records every time your profile shows it.
Honest limits
What these demonstrations do not prove.
- The standard's batch is localThe anchor batch for the GeoProof Standard's own record is signed but not on a chain. Evidence records are already anchored on XL1 Sequence, the test network: check one. Mainnet anchoring is not authorised yet.
- One organizationOxyon's attester, verifier and anchorer keys come from one company seed. The receipt shows process integrity, not third-party independence.
- A draft specificationThe GeoProof specification is published as draft v1.0. Its open questions are listed in the document itself.