Verification receipt

In plain words

A receipt is the durable output of checking a claim. A dashboard row can be edited, and a log line can be deleted. A receipt is built so that any change to it shows, and so that someone who has never dealt with the issuer can still confirm it's genuine. It's closer to a notarised document than to a database record.

How QED Proof uses it

Every QED Proof verdict is issued as a receipt in the open Proof of Agent Work format (poaw/0.1). It has three parts:

• body: the signed statement. It holds the issuer, the agent, the claim (bound by claim_digest), the observation (which verifier ran, what it read and when) and the verdict.
• signature: Ed25519 over the canonical bytes of the body.
• proof: the inclusion proof into the log, plus the on-chain anchor. It isn't signed, because it's verified on its own terms and gets extended when the anchor lands.

body and signature are immutable once issued. A receipt stores facts and fingerprints, never content, so a receipt link can be shared publicly without exposing your code or your posts.

Example

The public receipt page shows the verdict, the destination's evidence and three proof lines: signed, in the log (for example "leaf 8 of 9"), and anchored on Base Sepolia (testnet) at a block number. Each line is checked independently in the browser.