Advertisement · 728 × 90
#
Hashtag
#opentimestamps
Advertisement · 728 × 90
This document is an implementation specification for an Auto-Registration Permanent Archive Service — a system that automatically preserves web content at the moment of publication, with cryptographic tamper-evidence and legally admissible timestamping.

Key technical components: WARC-format full-page capture (ISO 28500) via Headless Chrome, RFC 3161 trusted timestamping (multi-TSA, parallel), OpenTimestamps anchoring to Bitcoin blockchain, independent observation nodes across 3 geographic regions for cross-validation, platform integration via OAuth 2.0 and Webhooks (WordPress, note, Wix, Medium, Ghost), PDF + JSON tamper-proof certificates with public verification endpoint, and genre-specific persistent identifiers (vio.paper, vio.text, vio.art, etc.).

This specification addresses a critical gap in the AI era: the inability to prove "this content existed in this exact form on this date." It serves AI provenance verification, academic citation integrity, and legal evidence use cases.

The service is owner-initiated, not third-party archiving — fundamentally different from Internet Archive or existing cache services.

This work also positions itself in relation to C2PA (Coalition for Content Provenance and Authenticity), identifying areas where WARC-based capture-time authenticity complements C2PA's current coverage.

This document is an implementation specification for an Auto-Registration Permanent Archive Service — a system that automatically preserves web content at the moment of publication, with cryptographic tamper-evidence and legally admissible timestamping. Key technical components: WARC-format full-page capture (ISO 28500) via Headless Chrome, RFC 3161 trusted timestamping (multi-TSA, parallel), OpenTimestamps anchoring to Bitcoin blockchain, independent observation nodes across 3 geographic regions for cross-validation, platform integration via OAuth 2.0 and Webhooks (WordPress, note, Wix, Medium, Ghost), PDF + JSON tamper-proof certificates with public verification endpoint, and genre-specific persistent identifiers (vio.paper, vio.text, vio.art, etc.). This specification addresses a critical gap in the AI era: the inability to prove "this content existed in this exact form on this date." It serves AI provenance verification, academic citation integrity, and legal evidence use cases. The service is owner-initiated, not third-party archiving — fundamentally different from Internet Archive or existing cache services. This work also positions itself in relation to C2PA (Coalition for Content Provenance and Authenticity), identifying areas where WARC-based capture-time authenticity complements C2PA's current coverage.

Just published on Zenodo 🗂️
Auto-Registration Permanent Archive Service — proves "this content existed in this exact form on this date."
Owner-initiated. Tamper-proof. Blockchain-anchored.
For the AI provenance gap.

zenodo.org/records/1957...

#WebArchiving #AIProvenance #C2PA #OpenTimestamps #WARC

0 0 0 0
Video

onto any other project that could solve blockchain anchoring effectively of every event that takes place inside the pipeline. I'd like to hear some opinions on your experiences with #Bitcoin chain, #OpenTimestamps or #Ethereum Layer2 chains. I need to write transactions for compliance as they occur

0 0 0 0
Original post on fosstodon.org

Some more `git subtree push` quirks:

• `git subtree push` (obviously) does not push :gitannex: #gitAnnex files to the remote. Syncing annexed files there is unergonomic.
• git subtree push` also strips commit signatures (e.g. GPG and as such #OpenTimeStamps timestamps). The truth lies in the […]

0 0 0 0
Haskell library and client for OpenTimestamps Haskell library- and client for OpenTimestamps

#Haskell library and -client for working with #OpenTimestamps.

(OpenTimestamps is a protocol for creating and verifying timestamps for digital files, which can be used to prove that a file existed at a certain point in time.)

photonsphere.org/post/2025-09...

0 0 1 0
Preview
Das Leben in Git (Annex) Ein Einblick, wie man alles Mögliche (nicht nur Code, auch Notizen, Fotos, Videos, Dokumente, etc.) mit der bekannten Versionsverwaltung ...

Hier ist die Aufzeichnung meines #TdF4 talks letzten Samstag über „Das Leben in Git (Annex)”:

https://media.ccc.de/v/tdf4-26-das-leben-in-git-annex-

:git: #git :gitannex: #gitAnnex #radicale #opentimestamps #annextimelog #passwordStore

0 1 0 0
Preview
OpenArchive What truly defines a storage system as decentralized, beyond data distribution, is the underlying principle that the computers hosting the data are controlled by different entities and that no single ...

#tahoelafs, #storj, @ff.bsky.social, @ffdw.bsky.social sky.social, #DatDotOrg, #Swarm, @arweave.bsky.social, #Codex_storage, #Bitcoin, #Opentimestamps, #hashd0x, #TheAlexArchive

👇
open-archive.org/news/mapping...

0 0 0 0