Verify a proof

Check that a record is intact, who sealed it and when it existed. Choose the proof file below.

A PubPhys record (.json, from "Download proof" on a record's page) is checked in this browser and never uploaded. A timestamp (.ots, from PubPhys or anywhere else) is checked against Bitcoin.

A revealed seal: add the sealed record's proof

If your proof file is a reveal, add the proof of the sealed record it reveals. Both are checked, and the pair checks out only if the reveal names that sealed record and both carry the same ORCID iD. The seal date is the sealed record's earliest valid Bitcoin confirmation, never its created; it is checked only with the values under Advanced. Sealing and reveals

Advanced: check a PubPhys proof without trusting this site's keys

Without these, a PubPhys proof is checked for being intact only. With your own copies of the two values below, the page also checks who sealed it, the public log, the ORCID signature and the Bitcoin date: it builds PubPhys's keys from the public mirror on GitHub, fetches ORCID's current keys from orcid.org and Bitcoin headers from blockstream.info. Take the values from somewhere other than this page: the verifier's defaults.json, a colleague, printed material (DNS, dig +short TXT _pubphys.pubphys.com, corroborates them but is not enough on its own).

Even so, this page runs code PubPhys serves you. To trust no one, run the verifier on your own machine (the steps) with the signed standalone release v0.2.0 (commit 2595ccd68f93, tarball SHA-256 09841fe7dc19e972828d2a8778bef7bd52ca1958021dd0c9315f42c4c5ffbe7d).

Timestamp checks run against the public OpenTimestamps calendars and the Blockstream block explorer. For a check that trusts no one, use a command-line client with your own Bitcoin node, or the independent verifier at opentimestamps.org.