Loading vLEI.wiki
Fetching knowledge base...
Fetching knowledge base...
This comprehensive explanation has been generated from 181 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.
Interoperability is the characteristic of systems, products, or protocols to work together effectively, enabling information exchange and coordinated operation across different implementations, platforms, and trust domains without requiring centralized coordination or shared infrastructure.
Interoperability represents the fundamental capability of diverse systems to exchange information, verify data, and coordinate operations without requiring centralized authorities, shared ledgers, or platform lock-in. In the context of decentralized identity and verifiable credentials, interoperability encompasses multiple dimensions: technical compatibility of data formats and protocols, semantic agreement on meaning and interpretation, and cross-domain trust establishment across organizational and jurisdictional boundaries.
The concept extends beyond simple data exchange to include the ability to verify authenticity, establish trust relationships, and maintain security guarantees across heterogeneous systems. True interoperability enables participants to choose their own infrastructure, governance frameworks, and technical implementations while still achieving seamless interaction with other ecosystem participants.
The KERI/ACDC glossary identifies four distinct types of interoperability relevant to decentralized identity systems:
Identifier interoperability enables users to reuse identifiers and their associated data across different applications and contexts. This goes beyond technical compatibility to encompass the purpose and community of use for identifiers. According to the Digital Object Identifier (DOI) Foundation, identifier interoperability requires consideration of both technical aspects and the social/organizational context in which identifiers operate.
In KERI, identifier interoperability is achieved through Autonomic Identifiers (AIDs) that are completely independent of any specific infrastructure. Unlike blockchain-based DIDs that lock identifiers to specific ledgers, KERI AIDs can be verified using only the and do not require access to any particular distributed ledger or centralized registry.
Implementations must strictly follow KERI specifications to maintain interoperability:
Cross-implementation testing is critical:
The vLEI Ecosystem Governance Framework specifies version upgrade policies:
These policies ensure ecosystem-wide interoperability during protocol evolution.
For ACDC interoperability:
Implementers have flexibility in infrastructure while maintaining interoperability:
All choices maintain interoperability through protocol compliance.
Syntactic interoperability exists when systems use common data formats and communication protocols, enabling them to exchange information structurally. Examples include XML, SQL, JSON, and character encoding standards like ASCII and Unicode. This level focuses on the ability to parse and process data without necessarily understanding its meaning.
KERI achieves syntactic interoperability through CESR (Composable Event Streaming Representation), which provides a dual text-binary encoding that maintains perfect round-trip conversion. CESR enables the same cryptographic primitives to be represented in human-readable Base64 text or compact binary format, with guaranteed composability across both domains. This allows KERI implementations in different programming languages and environments to exchange data seamlessly.
Semantic interoperability goes beyond structural compatibility to enable automatic, meaningful, and accurate interpretation of exchanged information. Systems achieve semantic interoperability when they not only exchange data but correctly understand its intended meaning, producing useful results as defined by end users.
For KERI and ACDC (Authentic Chained Data Container) credentials, semantic interoperability is achieved through:
The ACDC specification deliberately avoids JSON-LD's @context mechanism because dynamic context changes can alter semantic meaning unpredictably. Instead, ACDCs use static, cryptographically bound schemas that ensure consistent interpretation across all verifiers.
Cross-domain interoperability addresses the most complex scenario: multiple social, organizational, political, and legal entities working together across boundaries. This type recognizes that technical interoperability alone is insufficient when different governance frameworks, jurisdictions, and organizational policies must align.
The vLEI (verifiable Legal Entity Identifier) ecosystem exemplifies cross-domain interoperability by:
KERI's fundamental design principle is infrastructure independence. Unlike blockchain-based identity systems that require all participants to use the same distributed ledger, KERI identifiers can be verified using only the cryptographic Key Event Log (KEL). This means:
This independence is achieved through KERI's duplicity detection mechanism rather than distributed consensus. Instead of requiring all participants to agree on a single global state, KERI enables any verifier to detect if a controller has created conflicting versions of their KEL. This approach provides security guarantees without requiring shared infrastructure.
KERI implements the hourglass model of protocol design, where a narrow spanning layer enables broad diversity above and below. The KERI protocol serves as this spanning layer, providing:
This design allows different applications, governance frameworks, and use cases to build on KERI while maintaining interoperability at the protocol level.
CESR (Composable Event Streaming Representation) provides text-binary composability, enabling perfect interoperability between systems that prefer different encoding formats:
This dual-domain capability means KERI implementations can choose the encoding that best suits their environment while maintaining perfect interoperability with implementations using different encodings.
KERI provides interoperability with W3C Decentralized Identifiers through the did:keri and did:webs methods. These methods:
The did:webs specification demonstrates how KERI can provide enhanced security for web-based DIDs while maintaining interoperability with existing web infrastructure.
ACDC credentials achieve interoperability through:
The ACDC specification defines multiple media types (credential+acdc+json, credential+ld+json) with transformation mechanisms to maintain interoperability across different credential formats.
Interoperability enables ecosystem growth without requiring all participants to coordinate on infrastructure choices. In the vLEI ecosystem:
This flexibility reduces barriers to entry and enables organic ecosystem growth.
KERI's interoperability design prevents vendor lock-in:
This independence protects participants from being locked into specific vendors or platforms.
Cross-domain interoperability enables global operations:
KERI's interoperability enables multiple implementations in different programming languages:
All implementations maintain interoperability through protocol compliance, enabling developers to choose the best tools for their environment.
Achieving true interoperability requires careful protocol design. KERI's approach adds complexity in areas like:
However, this complexity is concentrated in the protocol layer, enabling simplicity and flexibility at higher layers.
Interoperability requires adherence to specifications:
This standardization is necessary for interoperability but requires coordination and compliance testing.
Some interoperability mechanisms have performance implications:
These trade-offs are generally acceptable given the security and flexibility benefits, but must be considered in system design.
Interoperability in KERI represents a comprehensive approach spanning technical, semantic, and governance dimensions. By achieving infrastructure independence through cryptographic verification rather than shared consensus, KERI enables true interoperability without platform lock-in. The protocol's design allows diverse implementations, governance frameworks, and use cases to coexist while maintaining security guarantees and verification capabilities. This approach positions KERI as a spanning layer for decentralized identity, analogous to how IP serves as the spanning layer for internet protocols.