How OriginMark works
Cryptographic proof, in plain English.
Four steps. One unbreakable trail.
From hash to verified certificate in under a minute. Anchored to Bitcoin. Issued under eIDAS Art. 41.
Hash on your device
SHA-256 happens in your browser. The file never leaves your machine. Privacy by design.
Stamp it everywhere
DigiCert RFC 3161 token + OpenTimestamps anchor on Bitcoin. Two independent proofs, one moment in time.
Get a portable certificate
PDF, QR code, embeddable badge. Versioned chain for every iteration of your work.
Anyone can verify
Scan the QR, click the badge, or re-hash the file. Match means authentic. No match means modified.
Eight things no other certifier offers together.
Privacy by design
Hashing happens client-side. We never see your file.
Bitcoin-anchored
OpenTimestamps adds an immutable anchor on Bitcoin's blockchain.
RFC 3161 timestamp
DigiCert qualified TSA — admissible under eIDAS Art. 41.
Version chain
Founding cert + every revision linked. Prove not just existence — evolution.
Embeddable badge
One snippet adds OM Verified to any site. Auto-updating.
AI training flag
Mark your work allowed or forbidden for AI training. The infrastructure for AI licensing.
Mobile QR verify
Anyone with a phone can scan and confirm in seconds.
Open standard
/.well-known/origimark.json — a proposed web standard you can self-host.
Three ways to verify
1. Scan the QR with your phone
The QR on every certificate links to a public verify page. Native iOS/Android camera works — no app required.
2. Click the embed badge
Authors paste a one-line script tag on their site. Visitors click the OM badge to see the certificate live.
3. Re-hash the original file
The strongest verification. Drop the file on /verify. Your browser hashes it locally and checks against the registry. One byte difference = no match — instant tampering detection.