repryntt

proof of work done

Check it yourself.

Every act a repryntt Bot takes — and every time a wall stopped one — is written down, signed, and linked to the act before it. You do not have to take our word for any of it: paste a receipt below, or upload the whole export, and this page will tell you whether the signatures hold and whether anything was changed after the fact.

Came here from a link in an email? It carries one signed receipt — for a note from our founder, the record of him approving that exact note — and this page checks it as it opens.

What is actually being checked

  • The contents. Each receipt carries a hash of its own fields. Change a word and the hash no longer matches.
  • The signature. That hash is signed with the Bot’s ed25519 key. Only the machine holding the private half can produce one, and the private half never leaves it.
  • The order. Each receipt names the one before it, so a receipt quietly removed or moved breaks the chain even though every receipt left is genuine.
  • The time. A signed chain proves nothing was changed, not when it was written — whoever holds the key could rebuild it today. So every day’s receipts are reduced to one hash, and that hash is put into Bitcoin through OpenTimestamps and published where the Bot’s owner cannot reach it. An errand’s proof bundle carries that day’s proof; this page follows it to the Bitcoin block and says the work happened on or before that block’s date. Change one character of the bundle and it says which check broke.

Nothing you paste here is sent anywhere. The check runs in your browser, and it is the same check the Bot runs on itself with repryntt verify. Ask whoever ran the work for their export — repryntt verify --export receipts.jsonl — and it will carry the receipts and the public key together. For one errand, ask for repryntt receipts export --task <id>: its receipts, and the proof of when.

To check when, and only for a proof bundle, the page asks for public data: the published anchor for that Bot and day, from repryntt; the status of its timestamp, from the OpenTimestamps calendars; and one Bitcoin block header, from a public block explorer. It sends hashes and a block number, never the receipts — and a header is believed only after it proves its own work. Untick “Check when it happened, online” and nothing leaves the tab at all.