Loading vLEI.wiki
Fetching knowledge base...
Fetching knowledge base...
This comprehensive explanation has been generated from 85 GitHub source documents. All source documents are searchable here.
Last updated: October 7, 2025
This content is meant to be consumed by AI agents via MCP. Click here to get the MCP configuration.
Note: In rare cases it may contain LLM hallucinations.
For authoritative documentation, please consult the official GLEIF vLEI trainings and the ToIP Glossary.
The issuee is the entity to which an ACDC credential is issued, identified by their AID (Autonomic Identifier) in the credential's attribute section. Unlike the mandatory issuer, the issuee is optional, enabling both targeted credentials (with a specific recipient) and untargeted credentials (bearer-style).
In the ACDC (Authentic Chained Data Container) credential framework, the issuee is the entity to which the claims of a credential are asserted. The issuee's AID (Autonomic Identifier) appears in one of two locations within the ACDC structure:
a field)A field)Unlike the issuer, which is mandatory for every ACDC, the issuee is optional. This design choice enables two distinct credential patterns:
The issuee concept is fundamental to the ACDC credential lifecycle and plays distinct roles in different exchange patterns:
In an issuance exchange, when the origin ACDC has an issuee, the disclosee (credential recipient) MAY also be that origin ACDC's issuee. This creates a direct issuance-to-holder pattern where the entity receiving the credential is also its subject.
When implementing ACDC credentials with issuees:
For credentials using edge operators:
child.i === parent.a.i (child issuer matches parent issuee)In the GLEIF vLEI ecosystem:
Each credential type follows strict I2I or DI2I chaining rules to maintain the verifiable trust hierarchy from GLEIF root through QVIs to Legal Entities and individuals.
During presentation exchange, the issuee's role becomes more nuanced. The discloser (entity presenting credentials) may or may not be the issuee of the disclosed ACDCs. This separation enables:
The issuee plays a critical role in ACDC chaining through edge operators:
These operators define the logical relationships between credentials in a verifiable graph, with the issuee serving as the pivot point for authority delegation.
The optional nature of the issuee field enables sophisticated privacy patterns:
The issuee's AID, when present, establishes a cryptographically verifiable binding between the credential claims and the subject entity, enabling end-to-end verification of credential chains without relying on centralized registries.