Transparency

Public trust log.

OTRUST publishes operational trust signals so users can distinguish real cryptographic records from marketing claims. The counters below are served from the live system.

Open raw stats Open source repo

recordsha256:3b7f...a91cstored

IDzk:id_8f1e...c2verified

anchorbitcoin:block -public

-Registered records

-Hashes computed

-Timestamp tool visits

-Claim attempts

-Verified records

-Anchored on Bitcoin

-Latest Bitcoin block

What is counted

Registered records are unique receipts stored in the database (timestamps, sign packages, ID proofs). Hashes computed counts local SHA-256 operations in the browser — including verify/compare flows — without storing content.

Re-hashing the same file counts as activity but not as a new record.
Claim attempts include duplicates that return “already registered”.
No artificial baseline is added. All numbers come from /stats.

Privacy posture

The product is designed around hashes, signatures, ID metadata, and explicit user-controlled sharing. Raw content is not needed for public verification.

File timestamping hashes in the browser.
Timestamp and Sign history lists are stored in your browser only (localStorage or extension storage) — not on the server and not shareable by public key or URL.
The server does not expose per-key receipt lists; individual proof URLs still work if you have the receipt ID.
Optional notification emails are stored separately.
ID views do not reveal underlying personal data.

Independent verification

OTRUST uses open verification formats where possible and keeps the provider boundary visible. Production can be used hosted or self-hosted from the public repository.

OpenTimestamps support for Bitcoin anchoring.
Public verification URLs and downloadable receipts.
MIT-licensed open source implementation.