Sigelith Timestamp

Disgrifiad

Sigelith Timestamp records that a file existed at a point in time — without sending the file anywhere.

When you stamp a file, the plugin computes its SHA-256 fingerprint on your server and records those 64 characters in the public, append-only Sigelith log. Anyone can later check, with standard tools and without trusting you or Sigelith, that a file with exactly these bytes existed no later than the stamped time and has not changed since.

• Stamp with one click — “Stamp with Sigelith” next to each file in the Media Library, as a bulk action, or in the attachment details. Optionally, every new upload in the background.
• A badge under the file — under File blocks (and, if you want, Image blocks), on attachment pages, or anywhere with [sigelith_stamp id="123"]. The badge is plain HTML with one small stylesheet served from your own site: no script, no tracking, no request to Sigelith while your page is viewed. It cannot break your theme and your theme cannot break it.
• Honest by design — the badge disappears when the file is replaced, until the new version is stamped. It says what a timestamp proves: that the file existed no later than a given time. It does not claim who made the file or that its content is true.
• Gets stronger with time — once a week Sigelith seals all its entries, signs the seal and anchors it in Bitcoin. The plugin checks this once a day and adds “Weekly seal” and “Bitcoin: block” to the badge.

Free, no account, no API key.

How the log and the proofs work, precisely enough to check them yourself: sigelith.org/spec. A court-appointed expert can follow the step-by-step check in section 11.

External services

This plugin connects to the Sigelith service at https://sigelith.org to record and check timestamps. It sends nothing until you stamp a file.

• When you stamp a file (by clicking “Stamp with Sigelith”, by the bulk action, or — only if you switched it on — automatically after an upload), the plugin sends the file’s SHA-256 fingerprint (64 hexadecimal characters) to https://sigelith.org/api/proof/stamp. The file itself, its name and the address of your site are never sent.
• Once a day, for stamped files whose weekly seal or Bitcoin anchor is not yet complete, the plugin sends the same fingerprint to https://sigelith.org/api/proof/verify to read their status.
• Visitors of your site never contact Sigelith unless they click “Verify independently” on a badge, which opens the public verification page.

Fingerprints in the Sigelith log are public and permanent: an entry cannot be withdrawn. Nobody can read a file from its fingerprint, but the fact that a file with that fingerprint existed becomes public.

Terms of use: https://sigelith.org/terms/ — Privacy policy: https://sigelith.org/privacy/