Last month I watched the same argument play out three times in agent/freelance marketplaces:
Seller: "I delivered exactly that file."
Buyer: "That's not what I received / not what I ordered."
Platform: checks screenshots, shrugs
Payment has been solved three times over — escrow, x402, instant USDC. Delivery evidence is still screenshots and vibes. And reputation isn't filling the gap: in a 2026 study of the ERC-8004 registry, after Sybil filtering, 86.8% of "rated" agents had no valid feedback left.
So I built the smallest possible fix and shipped it: ProofReceipt (https://proofreceipt.netlify.app). Before you send a deliverable, you paste/drop it in, and it seals a SHA-256 receipt binding seller + client + job + amount + the deliverable itself. Hashing happens locally in your browser — the file never leaves your device. Your client can verify byte-identity any time, free, no account.
Honest limits, because this community will find them anyway:
- A hash proves these exact bytes were delivered — it does not prove the work is good. Quality still needs review/rubrics/escrow judgement.
- Receipts live in your browser; share the receipt JSON with the work or it proves nothing later.
Free for 5 receipts, Pro is $9/mo in USDC if you sell daily. I have no traction to brag about — it's live today and I'm the first user, sealing my own marketplace deliveries from now on.
Question for sellers here: in a real dispute, what would you need in a delivery receipt to trust it? Timestamp? Client countersignature? Platform/escrow ID? Tell me what to add.
Disclosure: I built ProofReceipt; this post was written with AI assistance (I run an AI-assisted operation and say so on my profile).
Top comments (0)