Skip to main content

Crate alexandria_verify

Crate alexandria_verify 

Source
Expand description

Alexandria credential verification.

Everything needed to decide whether an Alexandria credential is genuine: the VC envelope types, JCS canonicalization, the Data Integrity proof (DataIntegrityProof, cryptosuite eddsa-jcs-2022), did:key resolution, and Bitstring Status List revocation and suspension. Around them sit the checks a reader makes of what a credential says: device attestation evidence (attestation), organisation backing (org), the coverage statement registry (coverage), the issuance policy rule an issuer and a hosted service share (policy), and the evidence entry naming the credential a role credential was issued on (assessed).

The crate performs no I/O. Verification needs to consult persistent state in four places — the key registered for an issuer whose DID is not self-resolving, a status list’s bits (revocation and suspension alike), whether something supersedes the credential, and an observed ledger anchor of its hash — and each of those arrives through VerificationStore rather than a database handle or a chain client. Callers implement the trait over whatever they have: SQLite in the app, a credential bundle in the CLI, Postgres on a server.

That indirection is the point. A verifier should link a signature checker, not an application.

Re-exports§

pub use did::Did;
pub use did::DidError;
pub use did::KeyRegistryEntry;
pub use did::VerificationMethodRef;

Modules§

access
Access grants: an organisation asks to see some of a learner’s skills, the learner decides, and the learner can take it back.
assessed
The evidence entry naming the credential a role credential was issued on.
attestation
Device attestation evidence: what it is, what it binds, and how a verifier checks it.
course
Course completion policy and endorsement verification.
coverage
Coverage statements: what an integrity session under a trust profile and a verification rung checked, what it did not, the platform ceilings, and the error rates the profile was certified at.
did
did:key identities for the VC-first credential model.
exchange
The credential exchange: an organisation asks a holder for a credential, and the holder answers with a W3C Verifiable Presentation.
governance
Verifiable quorum certificates for governance submission and close events.
hash
integrity
The vocabulary of an integrity assertion: trust profiles, the signals they add, verification rungs, and how a policy floor is judged against a profile.
json
Bounded parsing for untrusted JSON.
org
Organisation identity: a name an organisation has proven by its domain.
policy
The issuance policy and the one rule that judges it.
qualification
Subject qualification policies.
talent
Talent-index records: the wire format, and its signature.
trust
Credential trust classification.
vc
Verifiable Credential domain types (VC-first credential model).

Structs§

NullStore
A store that knows nothing.

Enums§

StoreLookup
Result of consulting verification state supplied by a caller.

Traits§

VerificationStore
Persistent state that verification consults.