Content and Versioning

This topic explains how PaperProof separates durable content storage from on-chain artifact state while keeping version history verifiable.

PaperProof separates compact authoritative state from large content bytes. Version records Each published version records a shared header with: artifact series ID; artifact type; version number; previous version ID when applicable; author address; content hash; Walrus blob ID; Walrus blob object ID; content type; status and timestamp. Type-specific records add metadata appropriate to the artifact family. The version header is the chain-side statement of what bytes a client expects to retrieve. Large packages stay flexible without becoming unverifiable. Append-only lineage Adding a version does not mutate earlier version records. Applications can show a convenient current view while preserving historical auditability. This supports stable-series citation, exact-version reproducibility, release comparison, recovery from a bad update, and freshness-aware agent retrieval....