For WordPress or self-hosted sites: on publish/update we submit the manifest and retry until an OpenTimestamps proof anchors. We do not host article bodies; proofs stay independently verifiable even if the service pauses.
Publish/update → generate manifest → submit to OTS → receive manifest.json and .ots. Background retries reduce manual work.
We handle digests/manifests, not article bodies. The .ots proof verifies with standard OpenTimestamps tools—no vendor lock-in.
Per-site quotas, queue weights, and retry policies—isolated from public queues; supports multiple sites in parallel.
Manifest and OTS can be CDN-hosted; verify via public page or offline tools for easy sharing.
| Dimension | Free | Pro (site license) |
|---|---|---|
| Submission quota | Auto submit after ~7 days or manual submit for content older than 72h | Configured per site with priority queueing |
| Trigger | Manual click or delayed auto submit | Auto on publish/update with background retries |
| Plugin support | Basic: delayed stamping (72h/7d) | Licensed: immediate stamping and Pro features |
| Use cases | Occasional evidence / low-frequency publishing / lower risk | Production: news, disclosures, high-value content, anti-plagiarism |
After installing the plugin, find the generated site_id in “Settings” (no login needed). Bring it here if you like.
Send your site_id / domain and desired quota to the admin or business contact to configure the license.
Refresh the WordPress plugin within 24h to pull updated account info. Questions? [email protected].
Yes. We don’t store article bodies. Keep your export, manifest, and .ots files; they verify with standard OpenTimestamps tools.
Quotas and retry policies are per site. Provide the site ID and we can update limits promptly.
Yes. Even with Pro you can use the public OTS calculator or manual export/manifest upload as a fallback.