Loading vLEI.wiki
Fetching knowledge base...
Fetching knowledge base...
This comprehensive explanation has been generated from 23 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.
vcp is an abbreviation for "vdr incept" or "verifiable data registry inception". It represents a specific KERI protocol event type that signals the creation and initialization of a verifiable data registry (VDR) within the Transaction Event Log (TEL) infrastructure.
In KERI's event-driven architecture, vcp serves as a compact three-letter operation code used in event streams to indicate registry creation events. This follows KERI's pattern of using terse, standardized codes for different event types and operations throughout the protocol.
Within the KERI ecosystem, verifiable data registries track the lifecycle state of verifiable credentials - specifically their issuance, revocation, and transfer status. The vcp event marks the foundational moment when such a registry comes into existence.
The vcp inception event is part of KERI's TEL system, which provides hash-linked data structures for tracking credential state. TELs integrate with Key Event Logs (KELs) through cryptographic anchoring:
A vcp event follows the standard TEL event structure with fields i (identifier), s (sequence number), and t (type). The t field value would be "vcp" to indicate this is a registry inception event.
Implementations must ensure vcp events are properly anchored to KEL events through event source seals. The seal contains the sequence number and digest of the vcp event, encoded in CESR format with the -GAB group framing code.
Validators verify vcp events by:
The vcp event is immutable once anchored. Registry configuration changes require subsequent rotation events (vrt), not modification of the inception event.
This anchoring mechanism means vcp events derive their authenticity from the signatures on the anchoring KEL events, rather than requiring their own signatures.
The KERI specification defines two types of TELs that begin with inception events:
Management TEL: Signals the creation of a Virtual Credential Registry (VCR) and tracks the list of Registrars that will act as backers for individual credential TELs. The vcp event for a management TEL establishes the registry's governance structure.
VC TEL: Tracks the issued or revoked state of individual verifiable credentials. Each VC TEL begins with its own vcp event and contains a reference to its corresponding management TEL.
The vcp event establishes critical registry parameters including:
Once a vcp event is anchored to a KEL and validated, the registry becomes operational and can begin tracking credential lifecycle events such as issuance (iss), revocation (rev), and rotation (vrt) operations.