Credentials
RLTP uses three verifiable credentials: the encounter credential, the
invitation credential and the admission vouch. All three are W3C
Verifiable Credentials 2.0 in the form of the
DTG credential specification,
signed with eddsa-jcs-2022 over did:key.
| Credential | DTG type | Who issues it to whom | What it does |
|---|---|---|---|
| Encounter credential | RelationshipCredential |
one party to the other, after they met | records one recognition; never revoked |
| Invitation credential | InvitationCredential |
a member to one person | offers membership in a group until validUntil |
| Admission vouch | EndorsementCredential |
a member to a candidate | supports one admission of that candidate |
Encounter credential
Section titled “Encounter credential”One step of an encounter yields one
encounter credential: the recognizing party’s signed statement that
it recognized the other in this enactment, issued to the recognized
party under a fresh Paaranker Ein für einen Begegnungsvorgang abgeleiteter Anker (DTG-Scope pairwise). Der Anker, unter dem eine Zeremonie durchgeführt wird, ist bei jedem Vorgang ein frischer Paaranker. GlossarPair anchor An anchor derived for one enactment (DTG scope pairwise). The enacting anchor of a ceremony is a fresh pair anchor at every enactment. Glossary of that enactment.
Its type is VerifiableCredential, DTGCredential,
RelationshipCredential, EncounterCredential, with issuerScope
pairwise. It has no validUntil and no credentialStatus: it is
never revoked, and a changed assessment is a new credential.
Spec: Encounter §7 ·
Schema: encounter-credential-0.26 ·
Vectors: encounter-cards.json
Invitation credential
Section titled “Invitation credential”A member who wants to admit one person into a group
issues an invitation credential to that person’s member anchor, and
sends it as the payload of membership-invite/0.2. Its type is
VerifiableCredential, DTGCredential, InvitationCredential,
MembershipInvite. The invitee answers it with a
membership-accept/0.2
that names the credential by its Credential-Digest Der multibase-kodierte Multihash über JCS des vollständigen Credentials einschließlich seines Proofs. GlossarCredential digest The multibase-encoded multihash over JCS of the complete credential including its proof. Glossary.
validUntil bounds the time in which it can be answered; no document
withdraws it earlier
(MO-8).
Spec: Membership §3.1 ·
Schema: payload-membership-invite, property invite ·
Vectors: dtg-credentials.json
Admission vouch
Section titled “Admission vouch”A member who knows a candidate, from meeting or by introduction,
issues a vouch (vouch@2) to the candidate’s member anchor once the
candidate has accepted an invitation. Its type is
VerifiableCredential, DTGCredential, EndorsementCredential,
AdmissionVouch, and it names the accept it supports. The group’s
policy counts the vouches enclosed in the admitting member.add. A
vouch counts for that one admission only: a later re-admission of the
same person needs fresh consent and fresh vouches.
Spec: Access §5.3 ·
Schema: access-vouch ·
Vectors: dtg-credentials.json
Why there is no membership credential
Section titled “Why there is no membership credential”Membership is a fact of the group’s state, not a document a member
presents. A group has one authority log, and every authorization
decision is derived from the state materialized from that log, never
from document content
(Access §3.1).
A person becomes a member by a member.add in that log, which
encloses the accept and the vouches the policy requires
(Access §5.3),
and stops being one by a member.remove, which starts a new epoch:
revocation is an epoch, prospective and honestly stated
(Access §1.1,
§7).
Every replica of the log reaches the same answer about who is a
member
(Access §3.6).
A credential a group issues outward, such as a membership
attestation, is deferred until a closed credential profile exists
(Access §15, OI-13).
Everything that moves between devices is a Trust Task document. The invitation and the vouch travel as credentials inside one; the accept, the admitting operation, key material and the removal notice are signed payloads without a credential.
Details
Section titled “Details”Securing profile
(Encounter §2.3).
Issuer and subject are did:key anchors over Ed25519, verified
without resolution. The proof is an embedded DataIntegrityProof,
cryptosuite eddsa-jcs-2022. @context is exactly three pinned
contexts: W3C credentials v2, a DTG context, RLTP v1. Verification is
JSON Schema plus the rules of the specification; no JSON-LD
expansion, no context fetched at runtime. Each schema is closed.
DTG context (Encounter §2.3, Contexts).
| Credential | DTG context pinned now |
|---|---|
Encounter credential, rltp-encounter-credential/0.26 |
https://registry.trustoverip.org/dtg/context/v1 (Working Draft 0.6.0) |
Encounter credential, rltp-encounter-credential/0.25 (read, not issued) |
https://firstperson.network/credentials/dtg/v1 (Working Draft 01) |
| Invitation credential | https://firstperson.network/credentials/dtg/v1 (Working Draft 01) |
| Admission vouch | https://firstperson.network/credentials/dtg/v1 (Working Draft 01) |
The next expected change is the wire step of the encounter credential
to the DTG context of the DTG Implementer’s Draft and the fields it
defines; the ceremony stays as it is
(Encounter, Status).
A producer issues rltp-encounter-credential/0.26; a receiver also
reads a held /0.25, because a credential is never re-issued
(Encounter §12).
Not credentials in this version.
- The Kontaktkarte Signierte Selbstbeschreibung einer Person mit dem Material, um sie zu erkennen und zu erreichen, und im Begegnungsvorgang mit einer frischen Challenge; angezeigt (zum Scannen) oder gesendet (im Vorgang übertragen, nennt den Empfänger). Kein Credential. GlossarContact card A person's signed self-description carrying the material needed to recognize and reach them and, in an enactment, a fresh challenge; displayed (shown for scanning) or sent (transmitted inside an enactment, naming its recipient). Not a credential. Glossary is signed like a credential but is a self-description (Encounter §6).
- The Annahme Die signierte Zustimmung der eingeladenen Person zu genau einer Einladung, an sie gebunden über deren Credential-Digest. Sie trägt die eigene Karte der Person, an deren Schlüsselvereinbarungsschlüssel das Willkommen versiegelt wird, und sagt, ob die Person der Gruppe vor der Aufnahme als Kandidatur gezeigt werden darf. GlossarAccept The invitee's signed consent to exactly one invite, bound to it by the invite's credential digest. It carries the person's own card, to whose key-agreement key the welcome is sealed, and states whether the person may be shown to the group as a candidacy before admission. Glossary is the signed payload of
membership-accept/0.2(Membership §3.2). - An attestation is a documented option of the Trust Layer with no artifact in this version (Trust §9.1).
- Group-issued credentials are deferred until a closed credential profile exists (Access §15).
- The succession credential belongs to the parked Succession draft (Succession, Status).