-
Event
Each capture creates an INGEST event: the SHA-256 of the file bytes (AssetHash), the device clock time, a PrevHash link to the previous event in the chain (CPP v1.1 §9), camera settings and sensor data. Location, when enabled, is stored only as hashes of the coordinates. Depth analysis and a biometric record are optional.
-
EventHash
SHA-256 over the event serialized with JSON Canonicalization (RFC 8785), excluding EventHash and Signature (CPP v1.1 §6.1). Shareable proofs carry the exact signed bytes as raw_event, so a verifier hashes bytes instead of re-canonicalizing.
-
Signature
ES256 (ECDSA P-256) over the EventHash. The key is generated on the device — the Secure Enclave on iOS, Android Keystore (StrongBox if available, otherwise TEE) on Android 1.6.1 — and the public key is exported as an X9.63 point.
-
Merkle batch
Leaf = SHA-256(EventHash bytes); parent = SHA-256(left‖right); the leaf list is padded to a power of two by repeating the last leaf; the proof runs bottom to top and the index parity picks the side (CPP v1.3 §2, v1.4 Appendix C). A one-event tree has root = leaf.
-
RFC 3161 timestamp
Only the Merkle root is sent: the TimeStampReq's SHA-256 messageImprint is the root itself, with no further hashing (CPP v1.3 §4.3, §5.1), and certReq is set. The apps try rfc3161.ai.moda, DigiCert, Sectigo and FreeTSA in that order.
-
Export
Shareable proof JSON (snake_case, proof_version 1.2, with raw_event, timestamp_proof and chain_context), internal proof.json (PascalCase), Evidence Pack ZIP (media plus proof.json), and on iOS a C2PA manifest.