Mock receipts vs hash proofs vs OpenTimestamps
6 min · Everyday language
What each proof means — and what none of them mean (not a token, not ownership of Bitcoin).
Myth vs fact
Myth: A mock receipt means something was written to Bitcoin.
Fact: Mock receipts are educational sandboxes only. They are labeled MOCK and never mint an asset.
Myth: An OpenTimestamps file means I own a coin or NFT.
Fact: OTS timestamps a hash. It proves a document’s fingerprint existed by a certain time — not ownership, not a tradeable asset.
Myth: “Pending confirmation” means it failed.
Fact: Calendars issue a pending stamp quickly; full Bitcoin confirmation can take longer. You can download the .ots and upgrade later.
Three layers on this site
1) Mock receipt — practice badge/certificate payload after the educational loop. Shareable demo. Not on-chain.
2) Hash proof — we store a SHA-256 of content or of a receipt JSON so anyone can recompute and compare.
3) OpenTimestamps (.ots) — calendars stamp that hash; later, Bitcoin anchors the calendar. Still not a token.
What “pending confirmation” means
When status is ots_pending / stamped_pending_confirmation, a calendar accepted your hash and returned a proof file. Bitcoin may not have included the calendar’s commitment yet. That is normal.
Download the .ots from the proof page. When you want a fully verified Bitcoin path, use OpenTimestamps tools (ots upgrade / ots verify) offline. This site does not sell chain settlement as an “asset.”
Safe next step
Run a mock loop, open the receipt, create a hash proof, download .ots if offered. Never paste seed phrases. Never treat a proof page as financial ownership.
Takeaways
- Mock = practice only
- Hash = fingerprint anyone can recompute
- OTS = timestamp of that fingerprint, not a coin