Public verification
Check it yourself.
Paste a certificate, enter its ID, or drop the original file. SmartLedger re-checks the signature, the proof hash, and the Bitcoin anchor — and tells you which of the three failed when one does. No account required.
Certificate
Paste the certificate JSON, a 64-character certificate ID and we will fetch it, or
a { "payloadHash": …, "txid": … } pair. You can also drop a
.json certificate straight onto the box.
The file is hashed in your browser with the Web Crypto API and compared to the certificate. It is never uploaded.
Verified Grades card
Enter the card UUID from the slab label, the RFID tap, or the QR code.
Notarize
Anchor a document to the Bitcoin blockchain so its existence at this moment can be proved later by anyone. The file is hashed and signed in your browser — only the 32-byte digest, a public key, and a signature are sent.
Drop a file here
or
What this proves — and what it does not
A key is generated in this tab and used to sign the digest. That proves this exact document existed at the time it was anchored, and that it has not changed since.
It does not prove who created it. Anyone can generate a key, so the signature identifies the key, not a person. Binding a document to a verified identity needs a SmartLedger account.
What this page checks
Signature — the certificate was signed by the key it names. Proof hash — the certificate's contents hash to the value that was anchored. Anchor — that value really is in the Bitcoin transaction it claims, confirmed by SPV against block headers. All three must pass. A certificate can carry a valid signature and still fail its anchor, which is why they are reported separately rather than as one verdict.
Wired to live NotaryHash and Verified Grades services. TicketMint, CannaTrack, AUMToken, Film Forge, ProofOfESG, and OrdinalSource do not expose public verification endpoints yet; they are deliberately absent rather than stubbed.