crypto-paper-readerlisted

# Crypto Paper Reader Produce a version-specific research record, not a generic summary. Keep the authors' claims separate from what was independently checked. ## Scope In scope: one focal work and its versions/supplements/artifacts; claim and definition extraction; proof/reduction map; security model; ZKP/lattice details; parameter/cost evidence; limitations; dependency and follow-up map. Out of scope: exhaustive literature search, global novelty, full independent proof certification, or paper rewriting. ## Required Inputs - exact paper or accessible identifier/version; - desired depth and research purpose; - supplements/artifacts when claims depend on them; - target questions, if any. ## Success Criteria - Exact version and accessible components are recorded. - Contributions become atomic claims with evidence locations/status. - Definitions, assumptions, security notions/models, parameters, failure terms, and cost models are explicit. - Proof dependency/implication structure and omitted obligations are visible. - ZKP/lattice-specific distinctions are extracted when applicable. - Limitations, unresolved questions, closest cited dependencies, and reusable insights are separated from speculation. ## Failure Modes - Abstract/snippet only: return an abstract-level map and mark technical claims unverified. - Inaccessible supplement/artifact: mark dependent claims unverified. - Version conflict: preserve both and identify which supports each extracted item. - Undefined n