Expand description
High-level body / publish-request verification — RFC-ACDP-0001 §5.11 (7-step algorithm).
This layer sits above validation, types, crypto, and did: it
recomputes the content_hash, runs structural validation, resolves
the producer DID, and verifies the signature envelope. The byte-level
primitives (acdp_crypto::verify_ed25519 /
acdp_crypto::verify_ecdsa_p256) live in crypto.
Modules§
- trust
- RFC-ACDP-0020 §5.2 for a list carried out of band (§7): verify a
did:key-issued trust-list body offline and turn it into aListVersion.
Structs§
- Verifier
- Stateless verifier. Requires a DID resolver to fetch producer keys.
Enums§
- Lineage
Binding - How a verified body’s
lineage_idis bound to its lineage.
Functions§
- lifecycle_
event_ prechecks - The pure (offline) prefix of RFC-ACDP-0013 §5 lifecycle-event verification, shared by the resolver-backed and did:key paths:
- lineage_
binding - Classify how
body.lineage_idis bound, given whether a receipt for it was verified. Call afterverify_registry_assigned_bindings. - raw_
describes_ body truewhen re-parsingrawyields exactly the typedbody(compared through the canonical typed serialization).- verify_
body_ offline - Full offline body verification for
did:keyproducers — works with--no-default-features(no HTTP stack, no resolver, no async). - verify_
body_ signature_ historical - Historical-key body-signature verification (ACDP 0.2, WS-B).
- verify_
body_ signature_ historical_ since verify_body_signature_historicalwith an explicit freshness scope: a DID document fetched at or aftersinceis fresh; an older cached copy that lacks the key is re-fetched once (RFC-ACDP-0001 §5.11 “Caching”).- verify_
body_ value_ offline verify_body_offlineover the body object exactly as received (RFC-ACDP-0001 §5.7 raw-JSON hashing). Returns the parsedBodyon success. The language bindings use this so a host passing wire JSON gets the normative raw-hash path.- verify_
context_ hash - Recompute
content_hashfor a retrieved context, hashing the raw received body when available (RFC-ACDP-0001 §5.7). - verify_
ctx_ id_ binding - Verify that a served body’s
ctx_idis the one the caller actually requested — RFC-ACDP-0006 §4.1 step 7 (NORMATIVE, “Bind the resolved identity”). - verify_
did_ key_ envelope - Verify a signature envelope whose key is a
did:key— a pure function available without theclientfeature (no resolver, no network, no async). - verify_
lifecycle_ event - Verify a lifecycle event per RFC-ACDP-0013 §5 — the helper both
registries (at
/retract//republishsubmission time, §6 step 3) and consumers (before treating an event as attributable evidence) use. - verify_
lifecycle_ event_ offline - Offline counterpart of
verify_lifecycle_eventfordid:keyactors — no resolver, no network, works with--no-default-features. Adid:webactor is refused withAcdpError::KeyResolution; use the resolver-backed helper. - verify_
publish_ request_ signature - Verify the producer signature on a
PublishRequestper RFC-ACDP-0003 §2.1 steps 6–7. - verify_
publish_ request_ signature_ offline - Offline counterpart of
verify_publish_request_signaturefordid:keyproducers — used by registries (and the bindings) to verify a publish request without theclientfeature. Assumes structural validation andcontent_hashrecomputation have already run (e.g. viaPublishValidator::validate_post_schema). - verify_
raw_ body_ hash - Recompute
content_hashoverraw(the body object as received) when it describesbody; otherwise fall back toverify_typed_body_hash. - verify_
registry_ assigned_ bindings - Enforce the offline registry-assigned bindings on a retrieved body:
- verify_
signature_ with_ method - Steps 5.5–7 of RFC-ACDP-0001 §5.11 against an already-located verification method — the synchronous core shared by the resolver-backed envelope, the historical-key path, and offline callers that select the DID document themselves (RFC-ACDP-0017 evidence bundles).
- verify_
typed_ body_ hash - Typed-path
content_hashcheck for aBody(no raw JSON held). - verify_
typed_ content_ hash - Check
expectedagainst the canonical typed renderingvalue, then against the legacy whole-second rendering of the same content. - verify_
typed_ publish_ request_ hash - Typed-path
content_hashcheck for aPublishRequest.