dpp-vc 0.21.0

W3C Verifiable Credentials, did:web documents and status lists for Odal Node
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62

//! `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 lives in `dpp-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.

pub mod credential;
pub mod did_builder;
pub mod jsonld;
pub mod local_service;
pub mod passport_credential;
pub mod sd_jwt_vc;
pub mod snapshot;
pub mod status_list;

#[cfg(test)]
mod test_support;
#[cfg(test)]
mod tests;

pub use credential::{
    AllowAllIssuers, Audience, CredentialBuilder, CredentialRole, CredentialStatus,
    DppAccessCredential, DppCredentialSubject, RevocationOutcome, StaticTrustedIssuers,
    TrustedIssuerRegistry, VerificationResult, check_revocation, verify_credential_claims,
    verify_credential_claims_with_trust, verify_credential_with_revocation,
    verify_credential_with_revocation_and_trust,
};
pub use did_builder::build_did_document;
pub use jsonld::{REMOTE_CONTEXTS, context_value, frame_passport, passport_context, strip_context};
pub use local_service::LocalIdentityService;
pub use passport_credential::{PassportCredential, PassportCredentialSubject};
pub use sd_jwt_vc::{SdJwtVcError, TYP as SD_JWT_VC_TYP, build_issuer_metadata, vct_for};
pub use snapshot::{CLOCK_SKEW_TOLERANCE, SnapshotBound, verify_snapshot_bound};
pub use status_list::StatusList;

/// Compile-checks this crate's README examples.
///
/// A README example is a public claim about the API, and nothing else in the
/// build compiles one. Without this, a README can advertise a function that
/// does not exist — which is exactly what happened before this harness landed.
#[cfg(doctest)]
#[doc = include_str!("../README.md")]
struct ReadmeDoctests;