Clockdo

Lightweight verification for publication records.
Verification overview

Calm, verifiable, and easy to share.

Clockdo records a deterministic fingerprint of published content and timestamps it using the OpenTimestamps (OTS) standard. This is a timestamp record — not a legal decision and not an ownership claim.

Records a content fingerprint
Standard OpenTimestamps (OTS)
Doesn’t decide ownership
See verification steps → Read FAQ

What is OpenTimestamps (OTS)?

OpenTimestamps is an open standard for timestamping hashes. A proof file (.ots) can be verified independently and may be anchored into widely used blockchains. Reference: opentimestamps.org.

What is timestamped?

A stable sha256 fingerprint of a canonical representation of content (e.g., extracted text under a defined canonicalization version). The fingerprint — not the original file — is what gets timestamped.

Disclaimer: This page explains a timestamping workflow and verification. It does not provide legal advice, does not determine authorship, and does not certify ownership.
How verification works

Simple steps

Verification confirms that a specific fingerprint existed by a certain time (via an OTS proof). If you need verification materials, ask the site owner for the exported proof files from the WordPress dashboard.

Step 1 — Fingerprint

Copy the sha256 fingerprint for this record.

Step 2 — Proof file

Obtain the matching .ots proof file (exported from WordPress).

Step 3 — Verify

Use an OpenTimestamps verifier to validate the proof against the fingerprint.

Step 4 — Confirm time

The verifier will show the anchored timestamp (and often transaction details).

Advanced: export → hash → manifest → .ots (full chain)

A typical export contains a manifest (hash directory) and an OTS proof. Workflow: 

1) Export from WordPress dashboard
   - manifest.json (or evidence.json)
   - proof.ots

2) Recompute fingerprint (same canonicalization rules)
   - content_hash = sha256(canonical_text)

3) Check manifest references
   - URL, canonicalization version, content_hash, timestamps, etc.

4) Verify OTS proof
   - Verify proof.ots for content_hash (or manifest_hash, depending on export type)

Result:
   - A verifier confirms the content hash existed by the anchored time.
Note: This page is designed to be understandable even without specialized tooling. Higher-tier plans may offer public online verification (re-checking page content automatically).
Plans at a glance

From delayed settlement to faster recording

Free plans typically record after a delay (settlement-style). Paid plans unlock faster workflows, and can optionally include draft-time / event-based recording.

Free

Delayed settlement & basic record display.

  • Eligible after 72 hours (settlement-style)
  • Display verification footer
  • Proof files via dashboard export

Pro

Faster workflows for active creators.

  • Faster recording cadence
  • Manual “record now” for eligible changes
  • Draft-time / event-based recording (optional)

Public

Public-facing verification experience.

  • Public verify page (re-check & validate)
  • Designed for disputes / platform review
  • Optional retention / backups
FAQ

Common questions

Short, practical answers. For OTS references, see opentimestamps.org.

Does this prove ownership?

No. It proves a specific fingerprint existed by a certain time. Ownership/authorship depends on broader evidence and jurisdiction.

Why can on-chain time be later than publish time?

Recording can happen after publication (e.g., delayed settlement on free plans). The anchored time reflects when that fingerprint was independently timestamped.

What happens if the article is edited later?

Edits produce a new fingerprint. Timestamping applies to content states; older records remain valid for the earlier state.

Do you store my full article?

Not necessarily. Timestamping is performed on a hash (fingerprint). Proof files are delivered to the site owner via export.

Can verification be done without Clockdo?

Yes. OpenTimestamps is a public standard. Clockdo automates recording and provides a clean record entry point.

What should I share in a dispute?

Share the record link, the fingerprint, and (if requested) the exported proof files. A verifier can validate the proof independently.

Is the verification footer required?

No. It’s optional. If enabled, it displays a calm, public record indicator — designed to be informative, not promotional.

Will this affect SEO?

The footer should be minimal and non-intrusive. Avoid keyword-heavy text. If linking out, consider rel="nofollow" by default.

Wording note: We avoid “certified / trusted / guaranteed” language. The goal is clarity and independent verification.