Skip to content

Terminology and Glossary ​

These definitions are normative where the specification uses the term.

TermMeaning
Credential family definitionVersioned metadata that identifies a credential family and its claim schema.
Credential familyIndependently released schema and family-specific circuits built on the core.
ClaimTyped statement made by an issuer about a credential subject.
Canonical encodingDeterministic byte representation used for hashing, signing, and conformance.
ChallengeApplication-defined value committed through Proof.challengeHash; only a presentation profile necessarily sources it from a verifier.
Credential subjectEntity described by the claims in a credential.
Credential statusEvidence used to determine whether a credential remains usable.
VCCanonical issuer-signed credential envelope.
VPCanonical holder-created presentation envelope.
Direct claimTyped claim carried directly in the signed credential body.
Claim commitmentDigest carried in the credential body while the opening remains private.
DisclosureClaim value intentionally exposed in a presentation.
PredicateBoolean statement proved over a claim without disclosing that claim.
Holder bindingEvidence that the presenting party controls the credential's bound key or secret.
Status bindingIssuer-signed reference binding a credential to status evidence.
Status authorityEntity authorized to make or attest credential-status transitions.
Status registryState and rules used to publish or evaluate credential status.
SchemaMachine-readable definition of a credential family's claims and constraints.
IssuerAuthority that creates and signs a credential.
HolderEntity that controls a credential and creates a presentation.
VerifierEntity that evaluates a credential or presentation under an explicit policy.
DIDDecentralized Identifier resolved to a DID document. DID methods are outside the core.
ProofCryptographic evidence evaluated under an explicit verifier policy and context.
Proof contextDomain-separated interpretation selected by the proof verification circuit.
Verification method referenceNon-zero controller contract address and fixed-width method identifier asserted by a proof or binding.
Signer authorizationScoped decision accepting one exact verification method and key for an issuer or verifier role.
Authorized signer descriptorCanonical role, method, key, scope, policy, and decision-sequence binding consumed by signer-authorization checks.
Decision sequenceAuthenticated logical ordering value for authorization updates; it is not a wall-clock timestamp.
Authorization sourceLocal application governance or external authority that evaluates policy and produces a signer authorization.
Authority domain commitmentApplication-defined commitment binding an authorization authority to the intended network and consumer, and optionally a registry profile.
Verifier authorization requestRequest signed by a verifier for a protocol-neutral scope; it is distinct from a holder-signed VP.
WitnessPrivate or public input supplied to a circuit.
Trusted timeTime evidence accepted from an explicitly configured authority or ledger source.
Prover keyCircuit-specific artifact used to create a zero-knowledge proof.
Verifier keyCircuit-specific artifact used to verify a zero-knowledge proof.
ZKIRIntermediate representation from which Midnight proving artifacts are produced.
Relying partyApplication that acts on a verifier's decision.
Canonical objectProtocol-independent object whose meaning is defined by this specification.
AdapterTransport, wallet, DID-method, or application integration outside the core.

An adapter MUST NOT reinterpret a canonical object or omit verification required by its owning credential family.

Midnight Verifiable Credentials core