Check a receipt

What this proves, and what it does not

• It runs here, not on our servers. The receipt never leaves the tab. You can disconnect from the network and the check still works.
• It proves the receipt is intact and signed. The body is re-hashed and compared with the digest, so an altered body fails even if someone recomputed the digest field. The signature is then checked against the address.
• A page we serve is convenience, not independence. We gave you this checker and the address it checks against. To make it independent, take the address from /limits yourself and check the signature with any Ethereum library: it is EIP-191 over the digest string.
• The standalone tool is still unpublished. npx @askuntold/verify does not resolve yet. We would rather say that here than let this page imply a tool exists to install.
• A receipt says what was served, not that it was right. It names the model and the enclave. It does not claim the answer was correct, useful or safe, and on its own it reveals nothing about what was asked: the commitments open only with the salts, which go to the person who asked and are never stored by us.
• With the salts and the answer text, this page opens the answer's commitment and says whether the text is the one the receipt sealed; with the question as well (a file carrying request.messages, such as an export made with "include my question"), it opens the prompt too. The prompt commitment covers the conversation exactly as you sent it, on every surface and whether or not the answer streamed, and nothing Untold adds is inside it: Untold's own instructions, your saved memory and the documents you attached are outside it, pictures you attached are inside it, so you can open it with your own messages. A run of several steps commits every step to that same conversation, and a receipt without the field promptScope set to sent was issued before this rule and may not open from your messages (issue #11).