presented/1 draft
Predicate IRI, exact bytes: https://registry.trustoverip.org/dtg/vsc/presented/1
Machine-readable: predicate.jsonld, also served at this URL with Accept: application/ld+json. Definition format: predicate.schema.json.
Definition
| Label |
| ||
|---|---|---|---|
| Meaning |
| ||
| Classification | evidence; weighed by: The community whose policy the attestation is issued under. | ||
| Object | digestMultibase | ||
| Subject–object relationship | credentialSubject.id MUST be the credentialSubject.id of the credential object.digestMultibase names, and a verifier holding that credential MUST check that it is. | ||
| Additional members | none | ||
taskContext | REQUIRED, with taskDigestMultibase | ||
| Minimum issuer scope | directed | ||
| Issuer | A member, or a VTA acting according to VTC policy. | ||
| Verification establishes | That the issuer attests that, in the exchange identified by taskContext, the subject presented the credential whose claims digest to object.digestMultibase. | ||
| Verification does not establish |
| ||
| Defined in | none | ||
| Governed by | the working group that maintains this registry |
The type-level bound of the specification's What Verification Establishes applies in full: a statement attests; it never confers representation, authority, membership, admission, governed status or task completion.
Profile
A statement under this predicate records that a party showed a credential it holds. The witness observed the holder present the credential the object names; the credential's issuer may never have been in the room. A door service attesting that a member presented their membership credential at an event is the typical case.
This is the presentation, or custody, statement asked for in review of the specification's statement credential, and it is the counterpart the witnessed/1 profile points to under What this predicate is not.
Why its own predicate
witnessed/1 binds its subject to the issuer of the referenced credential, so each statement names one direction of an edge. A presentation is observed from the other side: the observed party is the referenced credential's subject. Stretching witnessed/1 to cover both would make one IRI carry two subject–object rules, and a verifier could no longer check which one a statement meant.
What the digest binds
object.digestMultibase names the presented credential, computed as the specification's Digest Encoding section defines, over the credential excluding its top-level proof. A verifier holding that credential checks that its credentialSubject.id is this statement's credentialSubject.id. Without the credential to hand, the digest is an opaque hash, not an identified credential.
Status
No implementation issues this statement yet. It enters as draft so that the identifier exists when one does, and it stays draft until something uses it. Promotion to candidate needs two independent, interoperable consumers (GOVERNANCE §4).
Notes for implementers
taskContextand, with it,taskDigestMultibaseare required: a presentation is meaningful only relative to the exchange it happened in.- The issuer's correlation scope is
directedat minimum, for the same reason aswitnessed/1: the witness must be recognizable to the community whose policy it applies. - A verifier cannot tell from this statement whether the holder proved control of the presented credential's subject identifier, so the statement never establishes it. A verifier that needs it checks it in its own exchange.
- The example's identifiers and digests are illustrative.
Examples
examples/presented-vmc.json
{
"@context": [
"https://www.w3.org/ns/credentials/v2",
"https://registry.trustoverip.org/dtg/context/v1"
],
"type": [
"VerifiableCredential",
"DTGCredential",
"StatementCredential"
],
"issuer": "did:webvh:QmVzTd9hRkPqLu4WgXyN3c8pT2rJ6mK9sB1dF4gH7jL0n:door-service.example",
"issuerScope": "public",
"validFrom": "2026-10-02T18:30:00Z",
"taskContext": "urn:uuid:9d4e2a17-8c3b-4f6e-a1d0-3b7c5e9f2a64",
"taskDigestMultibase": "zQmWhCFfStzUE4HGseiQ1XWi2eEp1GTQEKnt2jyBe7uqzXD",
"credentialSubject": {
"id": "did:key:z6MkjRagNiMu91DduvCvgEsqLZDVzrJzFrwahc4tXLt9DoHd",
"predicate": "https://registry.trustoverip.org/dtg/vsc/presented/1",
"object": {
"digestMultibase": "zQmdfTbBqBPQ7VNxZEYEj14VmRuZBkqFbiwReogJgS1zR1n"
}
},
"proof": {
"type": "DataIntegrityProof",
"cryptosuite": "eddsa-jcs-2022",
"created": "2026-10-02T18:30:00Z",
"proofPurpose": "assertionMethod",
"verificationMethod": "did:webvh:QmVzTd9hRkPqLu4WgXyN3c8pT2rJ6mK9sB1dF4gH7jL0n:door-service.example#key-1",
"proofValue": "z3FXQjecWJKT…illustrative…"
}
}
Last changed 2026-09-30.