Skip to content
Glossary

Receipt

A receipt, in our usage, is a real linkable artefact -- a transaction, filing, or signed statement -- that backs or contradicts a specific claim. It is our term, not an industry standard.

On The Crypto Online, a receipt is our working term for a real, linkable artefact that supports or contradicts a specific claim: a transaction hash, a contract address, an attestation, a regulator filing, or an archived page with its timestamp. It is not an industry-standard term — it is the name we use for the thing every verification piece is built around.

Why it matters

A claim without a receipt is not automatically false, but it is unverifiable, and that is itself worth saying plainly. Naming the receipt forces a check to point at something concrete instead of resting on who said it or how confidently they said it.

What it doesn’t prove

A receipt supports a narrow claim. A valid transaction hash proves a transfer happened between two addresses for a given amount at a given time — it does not prove who controls either address, why the transfer happened, or what it means for anything else the project has said. Our full grading rules for what counts as a receipt live on the methodology page.

Example

A project claims it burned a large batch of tokens. The receipt is the burn transaction itself, visible on a block explorer, sending the tokens to a verifiable unspendable address. Without that transaction, the claim has no receipt, and the piece says so.

About the author

The Crypto Online Editorial Team

A collective byline for a claim-verification desk. Every piece is human-edited and checked against a primary record; AI assistance is disclosed in our editorial guidelines.

All work by the team → Methodology Corrections

Not financial advice. Human-edited; AI-assisted drafting is disclosed in our editorial guidelines. Spotted an error? See how corrections work.