Expand description
dpp-vc — the trust layer: who may read a passport, and how that is proven.
W3C Verifiable Credentials, did:web documents, Bitstring Status List
revocation, and the JSON-LD context those are expressed in.
Pure (no I/O, no network). Not a wasm32-unknown-unknown target: it depends
on dpp_crypto, whose RNG requires a platform entropy source.
§Trust, not primitives, and not policy
Three neighbouring concerns are deliberately not here:
- Cryptographic primitives — JWS, keys, the keystore — are
dpp_crypto, which this crate depends on. Signing bytes is a different job from deciding whose signature means what. - The disclosure contract —
Audience,Disclosure, the per-field disclosure map and the filter that applies it — describes what a passport is, not who is asking. It currently lives indpp-crypto::access; its settled home isdpp-domain. - Projections — GS1, AAS — render a passport for an ecosystem. They say nothing about trust.
The seam this crate sits on: a credential establishes which Audience a
caller holds; the disclosure policy maps that Audience to fields. Those
are two questions and they are answered in two places.
Re-exports§
pub use credential::AllowAllIssuers;pub use credential::CredentialBuilder;pub use credential::CredentialRole;pub use credential::CredentialStatus;pub use credential::DppAccessCredential;pub use credential::DppCredentialSubject;pub use credential::RevocationOutcome;pub use credential::StaticTrustedIssuers;pub use credential::TrustedIssuerRegistry;pub use credential::VerificationResult;pub use credential::check_revocation;pub use credential::verify_credential_claims;pub use credential::verify_credential_claims_with_trust;pub use credential::verify_credential_with_revocation;pub use credential::verify_credential_with_revocation_and_trust;pub use did_builder::build_did_document;pub use jsonld::REMOTE_CONTEXTS;pub use jsonld::context_value;pub use jsonld::frame_passport;pub use jsonld::passport_context;pub use jsonld::strip_context;pub use local_service::LocalIdentityService;pub use status_list::StatusList;
Modules§
- credential
- W3C Verifiable Credentials for DPP access control.
- did_
builder did:webDID document builder.- jsonld
- Minimal JSON-LD context builder for DPP passport payloads.
- local_
service - In-process
IdentityPortimplementation backed by a localKeyStore. - passport_
credential - Passport verifiable-credential construction.
- status_
list - W3C Bitstring Status List v1.0 — pure decoding + bit indexing.
Structs§
- Passport
Credential - A W3C Verifiable Credential 2.0 envelope binding a DPP passport to its signed payload.
- Passport
Credential Subject - Claims about the DPP passport being attested.
Enums§
- Audience
- Re-export the canonical access vocabulary from dpp-domain. Who is asking for passport data.