Second Eye receipt verifier

Check a Second Eye receipt in this browser. Nothing is uploaded, and the check runs offline.

Check a Second Eye receipt

Got a folder from second-eye export? Drop it here or pick it. Otherwise select the receipt, and the session log if you have it: with the log, every recorded event is checked against the signed receipt. Timestamp proofs (.tsr, .ots) are optional.

expected key: the fingerprint you got from the builder through another channel (optional) or their key-card.json

Drop the exported folder (or its files) here

exported folder

receipt (.json) session log (events.jsonl, optional) timestamp proofs (.tsr / .ots, optional)

Other checks

Checks an ed25519 signature, an RFC 3161 timestamp token and an OpenTimestamps proof. The only network access on this page is a GET for a Bitcoin block header, and only when you ask for an online proof check.

…

Bitcoin-anchored reference proof

This is the public hello-world.txt.ots example from opentimestamps-client. Verifying it makes two GETs to mempool.space.

Your own files (read locally)

message .sig (64 B) signer.pub (32 B) .tsr .ots

Other receipt formats (obsigna v0.5.0, sharif-05)

Paste one obsigna receipt, an array of obsigna receipts (a chain), or an array of sharif-05 audit records. Neither format says how to find the signer's key, so you supply it: a PEM Ed25519 key for obsigna, a JSON array of P-256 JWKs for sharif-05. Checked locally; nothing is sent.

receipt / chain / trail (JSON) key (PEM, or JWK array)

sharif-05: Construction test; no published signed interop vectors; not an interoperability verdict. Signatures are checked as standard ES256 over the canonical bytes (the pinned reading of the draft's ambiguous §6.2).

sharif-05 construction mode: check the other §6.2 reading (ES256 over the digest). Never gives VERIFIED; the result is INTEROP_NOT_ESTABLISHED.

Network log (this page)

(no requests)