Module ndn 

did:ndn resolver — resolves via NDN Interest/Data exchange.

Two resolution strategies, chosen by decoding the binary DID back to the underlying NDN name and inspecting the first component type:

CA-anchored (name components are all GenericNameComponents): Fetches the certificate at <identity-name>/KEY and converts it to a DID Document via cert_to_did_document.

Zone (first component is BLAKE3_DIGEST type): The zone root name IS the DID. The resolver fetches a published DID Document Data packet at <zone-root-name>. Zone owners must publish their DID Document as a signed Data packet for resolvers to find it. The resolver verifies that blake3(ed25519_pubkey) in the fetched document matches the zone root name component.

Stub mode (no fetcher configured): returns DidError::Resolution. Wire up a live fetcher via NdnDidResolver::with_fetcher / NdnDidResolver::with_did_doc_fetcher.

Structs

NdnDidResolver

Resolves did:ndn DIDs by sending NDN Interests.

Type Aliases

NdnDidDocFetchFn

Fetch an NDN DID Document Data packet by name (used for zone DIDs).

NdnFetchFn

Fetch an NDN certificate by name (used for CA-anchored DIDs).