From Screenshots to Verifiable Bitcoin Receipts

Screenshots are convenient, but they are not a strong proof of payment.

I built GhostReceipt to test a simpler idea: create a receipt that can be independently verified, without asking people to trust an image or a chat message.

What it does

GhostReceipt takes a transaction hash and creates a signed + verifiable receipt.

The flow is:

1. Fetch canonical transaction data from multiple providers.
2. Confirm consistency (consensus checks).
3. Sign the oracle payload with a tracked key.
4. Generate a proof-backed receipt that can be verified from a link/QR.

Why this approach

The goal is practical trust minimization for normal workflows:

• payroll confirmation,
• contractor payment confirmation,
• merchant settlement evidence.

Not “perfect trustlessness,” but stronger evidence than screenshots.

Design choices

• Fail closed on missing critical config.
• No silent fallback on risky verification paths.
• Readable errors for non-technical users.
• Open-source implementation so the model can be reviewed.

Limits (important)

• It does not prove legal identity or ownership intent.
• It still depends on oracle/provider availability.
• It is best treated as cryptographic evidence, not a legal judgment engine.

Current status

The project is live, tested across BTC/ETH/SOL paths, and still being hardened around reliability and operational safety.

If you work on payment verification or trust tooling, I’d value feedback on failure modes and threat assumptions.

Repo + docs: https://github.com/Teycir/Ghostreceipt