Module log 

Client-side transparency-log verification (ACDP 0.3, RFC-ACDP-0012 §9): checkpoints (§9.3) and inclusion proofs (§9.1) against the registry’s DID document.

All failures map to AcdpError::InvalidLogProof — deliberately not InvalidReceipt: a proof failure indicts the log (tree membership, history consistency, checkpoint signature), never the body, receipt, or head-receipt verdicts, which are independent results and reported independently (RFC-ACDP-0012 §9.3, §11). Transport-level DID-resolution failures keep their transient/permanent classification so retry logic still works.

Functions

verify_log_checkpoint_value

Verify a log_checkpoint value end-to-end per RFC-ACDP-0012 §9.3:

verify_log_inclusion_value

Verify a log_inclusion value end-to-end per RFC-ACDP-0012 §9.1 (steps 2–6; step 1 — reconstructing the leaf from verified material — is the caller’s, since only the caller holds the verified body, the recomputed content_hash, the resolved producer key fingerprint, and the RFC-ACDP-0010-verified receipt):