Timestamp as a service

Notarised since. Without trusting us.

A SHA-256 hash proves content integrity. A public timestamp proves when that content already existed. Together they give disputes, claims handling, litigation and customs reviews a portable time anchor.

Construction

Four steps, one portable proof

Verification does not require our server, your account or continued subscription.

01

Canonicalise

Normalise the record into an agreed byte sequence and calculate SHA-256.

02

Aggregate

Combine the day's records into a Merkle tree. Each record receives a proof path.

03

Anchor

Submit the daily root to a public timestamping mechanism with a widely witnessed ledger.

04

Export

Download the record hash, Merkle path and timestamp proof. Verify independently.

record_hash = SHA-256(canonical_record) leaf = record_hash root = MerkleRoot(all_leaves_for_UTC_day) proof = [sibling hashes, left/right instructions] anchor = public_timestamp_proof(root) verification = recompute(record) + verify_path(record, root) + verify_anchor(root)
Use cases

A small proof with expensive uses

  1. Commercial disputes

    Establish which evidence version existed before a contract, delivery or refusal event.

  2. Insurance claims

    Fix the evidence state at the time of loss, grading or underwriting.

  3. Customs review

    Show that shipment evidence predates an inspection or amendment request.

  4. Litigation and arbitration

    Supply a technical annex that another expert can independently reproduce.

PRICING

Priced like infrastructure

Single record¥2–5
Annual evidence bundle¥5,000–30,000
Public verificationFree
Accreditation requiredNo

A timestamp proves existence and integrity at a point in time. It does not prove that the underlying statement is true.

Request API access →
Local recomputation

Try SHA-256 in this browser

This demonstration hashes text locally. No input is transmitted.

LOCAL RESULT
Press compute. The resulting digest appears here.