CPHAR documentation is organized by section. Start with the Overview to get oriented, then dive into the Protocol for the attestation flow and into the Threat Model to understand what each mechanism proves and does not prove.
Documentation
Protocol, architecture, threat model, examples, and specification for CPHAR — Commodity Proof with Hardware-Attested Reserves.
Overview
What CPHAR is, what it proves, what it does not prove, and the vocabulary used throughout the documentation.
Protocol
The CPHAR attestation flow — actors, lifecycle, seal attestation, reserve claims, ZK integration, and revocation.
Architecture
Reference architecture for CPHAR deployments — seal device, registry, verifier, oracle layer, and audit interface.
DraftThreat Model
Adversary capabilities, attack surfaces, mitigations, and residual risks for CPHAR-based deployments.
DraftExamples
Worked CPHAR scenarios across commodity types — fertilizer, metals, grain, warehouse-scale reserves.
DraftSpecification
Normative message formats, signature schemes, identifiers, proof bundles, and API surface for CPHAR-compatible implementations.
DraftOperations
Day-to-day operational guidance for CPHAR deployments — seal installation, inspection cadence, incident response, broken-seal handling.
DraftGlossary
Definitions of CPHAR terms used throughout the protocol, architecture, and operations documentation.
DraftFAQ
Frequent questions about CPHAR — what it is, what it is not, and how it compares to other reserve-proof approaches.
Draft