PaperProof Docs | Getting Started

Introduction

What PaperProof is, what it adds, and what it does not claim.

Docs Path
getting-started/introduction
Artifact Code
PaperProof-generic_file-001144-c86c5f43d31b
Series ID
0xc86c5f43d31ba62f97dac4e056c1e25d7d42fc675262357c06a9cae9c633f55a
Content Type
application/vnd.paperproof.markdown-package+zip

This topic gives the baseline mental model for PaperProof and defines the protocol in plain language before any deeper technical reading.

Important digital works increasingly live across unstable boundaries: storage links, repository releases, social posts, preprint pages, datasets, software packages, and application databases. These surfaces are useful, but none of them alone gives the work itself a durable protocol identity. PaperProof addresses this missing layer. A PaperProof artifact is not merely an uploaded file or a page in one application. It is a continuing protocol object with typed versions, Walrus content references, official comments, official likes, ownership, status, timestamps, and canonical events. Protocol, not just platform PaperProof should be understood as an artifact protocol, not merely as a content site. Walrus stores large content packages. Sui stores compact shared protocol state....

This page is part of the public PaperProof website. When JavaScript loads, the full interactive route replaces this static public preview.