Sigelith Timestamp records that a file existed at a point in time \u2014 without sending the file anywhere.<\/p>\n\n
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.<\/p>\n\n
[sigelith_stamp id=\"123\"]<\/code>. 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.<\/li>\n- Honest by design<\/strong> \u2014 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.<\/li>\n
- Gets stronger with time<\/strong> \u2014 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.<\/li>\n<\/ul>\n\n
Free, no account, no API key.<\/p>\n\n
How the log and the proofs work, precisely enough to check them yourself: sigelith.org\/spec<\/a>. A court-appointed expert can follow the step-by-step check in section 11<\/a>.<\/p>\n\nExternal services<\/h3>\n\n
This plugin connects to the Sigelith service at https:\/\/sigelith.org to record and check timestamps. It sends nothing until you stamp a file.<\/p>\n\n
\n- When you stamp a file<\/strong> (by clicking \"Stamp with Sigelith\", by the bulk action, or \u2014 only if you switched it on \u2014 automatically after an upload), the plugin sends the file's SHA-256 fingerprint (64 hexadecimal characters) to
https:\/\/sigelith.org\/api\/proof\/stamp<\/code>. The file itself, its name and the address of your site are never sent.<\/li>\n- Once a day<\/strong>, 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<\/code> to read their status.<\/li>\n- Visitors<\/strong> of your site never contact Sigelith unless they click \"Verify independently\" on a badge, which opens the public verification page.<\/li>\n<\/ul>\n\n
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.<\/p>\n\n
Terms of use: https:\/\/sigelith.org\/terms\/ \u2014 Privacy policy: https:\/\/sigelith.org\/privacy\/<\/p>\n\n\n
\n- Upload the
sigelith-timestamp<\/code> folder to \/wp-content\/plugins\/<\/code>, or install the plugin from the Plugins screen.<\/li>\n- Activate it.<\/li>\n
- In Media \u2192 Library (list view), choose \"Stamp with Sigelith\" under a file.<\/li>\n
- Optional: Settings \u2192 Sigelith Timestamp.<\/li>\n<\/ol>\n\n\n
\nDoes my file leave my server?<\/h3><\/dt>\nNo. Only its SHA-256 fingerprint does.<\/p><\/dd>\n
Which file is stamped?<\/h3><\/dt>\nThe file behind the attachment's URL \u2014 the one your readers download. For large images WordPress serves a scaled copy; that copy is what gets stamped.<\/p><\/dd>\n
What happens if I replace the file?<\/h3><\/dt>\nThe badge disappears and the Media Library shows that the file changed. Stamp the new version to get a new badge. Earlier stamps stay in the public log and in the attachment's history.<\/p><\/dd>\n
Is this a qualified electronic timestamp under eIDAS?<\/h3><\/dt>\nNo. It is evidence anyone can check, not a qualified trust service, so it carries no legal presumption. See https:\/\/sigelith.org\/spec\/#attest<\/p><\/dd>\n