Loading vLEI.wiki
Fetching knowledge base...
Fetching knowledge base...
This comprehensive explanation has been generated from 32 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.
vrt is an abbreviation for 'verifiable data registry rotation' - a KERI operation code that performs rotation operations on verifiable data registries (VDRs), which are systems that mediate the issuance and verification of ACDCs.
vrt (verifiable data registry rotation) is a KERI operation type code that enables rotation of control authority over verifiable data registries (VDRs). A VDR is a system that mediates the issuance and verification of ACDCs (Authentic Chained Data Containers), and the vrt operation allows the controller to update the authoritative keypairs that govern the registry.
Within the KERI ecosystem, vrt represents a specific event type in the broader family of establishment events. Just as AIDs (Autonomic Identifiers) undergo rotation events (rot) to update their controlling keys, verifiable data registries require their own rotation mechanism to maintain security and enable key management.
The vrt operation is particularly relevant to Transaction Event Logs (TELs), which track the issuance and revocation state of credentials. A TEL is anchored to a controlling KEL through cryptographic seals, and the vrt operation enables rotation of the keys that authorize TEL events.
A vrt event follows standard KERI event structure with:
v): KERI protocol versiont): Set to "vrt" for registry rotationi): The VDR identifier being rotateds): Registry-specific sequence counterp): Links to prior registry eventk): New authoritative keypairsn): Pre-rotated key commitmentkt): Signature threshold for current keysVDR rotation events must be anchored to the controlling KEL through event source seals. The KEL event containing the seal must be signed by keys authorized under the current key state, creating a cryptographic commitment to the vrt event digest.
For VDRs with witness pools, the vrt operation may require coordination with witnesses to ensure proper event validation and receipt generation, similar to standard AID rotations.
In the vLEI ecosystem, VDR rotations have governance implications as they affect the authority to issue and revoke credentials. The vLEI Ecosystem Governance Framework may impose additional requirements on when and how vrt operations can be performed.
Like other KERI rotation operations, vrt benefits from KERI's pre-rotation mechanism, which provides:
The vrt operation is used when:
The vrt operation follows the same cryptographic principles as other KERI establishment events but applies specifically to the governance of credential registries rather than individual identifiers.