Why Sui and Walrus

This topic explains the infrastructural reasons PaperProof is built on Sui and Walrus rather than treating those choices as incidental.

PaperProof uses Sui and Walrus because the protocol needs both programmable object state and durable large-content storage. What Sui contributes Sui provides object-centric protocol state. PaperProof models artifacts, versions, comments trees, likes books, governance vaults, proposals, registries, and memory capability entries as explicit objects with relationships. Sui Programmable Transaction Blocks also let applications compose compatible Move calls into one user-signable workflow. This reduces signature burden while preserving wallet approval. What Walrus contributes Walrus stores large content that should not become Sui object bytes: PDFs, datasets, source archives, software packages, images, long comments, prompt packages, and static sites. PaperProof records commitments and references to that content so applications can retrieve and verify it....