DateSealed

By egosaru

0+ active installationsVersion 0.1.2

Record the publication date of your posts on a third-party ledger. Only a SHA-256 hash is sent; your text and images stay on your site.

Description

When you publish or update a post, DateSealed calculates a SHA-256 hash of the post text (and, optionally, the featured image file) on your server and sends only that hash to the DateSealed service. The service returns a signed time stamp (RFC 3161) immediately and anchors the hash in a Bitcoin block through OpenTimestamps within hours. Anchored records can be verified from the Bitcoin ledger alone, even if the service disappears.

  • Automatic: a new record on every publish and update; earlier records are kept as a history.
  • Private: the text, images and URLs of your posts are never sent.
  • Badge: a small line after the post with the record date and a link to the record page (you can turn it off).
  • Admin: a “DateSealed” column in the post list and a box on the edit screen.
  • Record pages in the language of your site: the badge links to the record page in all the languages datesealed.com offers (50 at the time of this release); other locales get the English page.

Records made with this tool do not guarantee legal effect. If you need an accredited timestamp (certified by Japan’s Minister of Internal Affairs and Communications), please use an accredited provider.

External service

This plugin connects to the DateSealed service (https://datesealed.com), operated by Lightscend Co., Ltd., to create and check records.

  • What is sent: the SHA-256 hash (64 hexadecimal characters) of the post text, and optionally of the featured image file; the site URL appears in the User-Agent header of every request. Nothing else.
  • When: when a post is published or updated (sent from WP-Cron shortly afterwards; if the hourly limit is reached, later), when you click “Record now”, and twice a day to ask whether pending records have been anchored.
  • Terms and privacy: https://datesealed.com/terms

Installation

  1. Upload the datesealed folder to /wp-content/plugins/ and activate it.
  2. Open Settings > DateSealed to choose the post types and the badge.

FAQ

Is my content uploaded?

No. Only the hash is sent.

What happens when I edit a post?

The hash changes, so a new record is created; the earlier ones stay in the history.

Does it work if WP-Cron is disabled?

Run wp cron event run --due-now from a real cron job.

How is the hash of the post text made?

From the saved post only, so that you can make it again later and other plugins or the theme do not change it (rule 2, since 0.1.1):

  1. Title, a line break, then the post content as stored.
  2. Remove HTML comments (this removes the block editor markers), then script and style elements.
  3. Replace every remaining HTML tag with a space, and decode HTML entities.
  4. Normalize to Unicode NFC, turn every run of white space into one space, and trim both ends.
  5. SHA-256 of the UTF-8 bytes.

What happens when the hourly limit is reached?

The post waits and is sent automatically when the service accepts it again. The post list shows “Waiting to record” until then.

Screenshots

Changelog

0.1.2

  • Added: record pages for 30 more site languages (Bengali, Urdu, Malay, Tamil, Persian, Romanian, Hungarian, Greek, Catalan, Hebrew, Swahili, Filipino, Kazakh, Czech, Swedish, Danish, Telugu, Marathi, Uzbek, Serbian, Bulgarian, Croatian, Slovak, Finnish, Norwegian Bokmål, Nepali, Gujarati, Azerbaijani, Amharic, Burmese). The language table is now generated from the service’s language list; Tagalog sites (tl) go to Filipino, Serbian (sr_RS), Uzbek (uz_UZ) and Azerbaijani to the Latin-script pages, Norwegian (nb_NO/nn_NO/no) to Bokmål.
  • No change to what is sent (still only the hash) or to how records are made.

0.1.1

  • Fixed: a record was lost when the hourly limit was reached (for example when many posts were updated at once). Posts now wait and are sent later, and the post list shows “Waiting to record”. Posts that were not recorded with 0.1.0 are queued again.
  • Changed: the text hash is now made from the saved post only (rule 2), so other plugins and themes no longer change it and it can be made again later. The next update of each post creates one new record under the new rule; earlier records stay valid.
  • Fixed: older posts whose records were still pending were not checked again.
  • Removed “Media” from the post types, because attachments are never published.
  • Added a link to the terms on the settings page.

0.1.0

  • First release.