Loading vLEI.wiki
Fetching knowledge base...
Fetching knowledge base...
This comprehensive explanation has been generated from 66 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.
A delegated inception event (dip) is a special type of KERI establishment event that creates a new Autonomic Identifier (AID) under the authority of a delegating identifier, establishing a cryptographically verifiable hierarchical trust relationship.
A delegated inception event (abbreviated as dip or delcept) is a KERI establishment event that creates a new Autonomic Identifier (AID) as a delegate of an existing identifier called the delegator. Unlike a standard inception event (icp) which creates an independent identifier, a delegated inception creates an identifier whose authority is cryptographically bound to and dependent upon approval from the delegating identifier.
Delegated inception is fundamental to KERI's cooperative delegation mechanism, which enables hierarchical key management and organizational identity structures. The process requires bidirectional participation:
The delegate creates the delegated inception event containing:
di field specifying the delegator's AID prefixThe delegator approves the delegation by:
Delegated inception requires careful coordination between delegator and delegate:
di field pointing to delegatorValidators must:
For multisig delegates:
isith, nsith) determines signing requirementsbt, b) provides duplicity detectionThis cooperative model prevents unilateral delegation and ensures both parties must participate for the delegation to be valid. The delegate's identifier prefix is derived from the delegated inception event itself, creating an immutable cryptographic binding between the delegate AID and the delegation relationship.
Key properties of delegated inception:
Use cases in the vLEI ecosystem:
The delegated inception mechanism is critical for implementing the vLEI governance model, where trust flows from GLEIF's root AID through QVIs to end entities, with each delegation cryptographically verifiable through the KERL structure.