Loading vLEI.wiki
Fetching knowledge base...
Fetching knowledge base...
This comprehensive explanation has been generated from 22 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.
Perfect security is a special case of information-theoretic security where ciphertext provides zero information about the encryption key, making cryptanalysis impossible regardless of computational resources. This represents the highest achievable cryptographic security level, exemplified by one-time pads and secret splitting schemes.
Perfect security represents the theoretical pinnacle of cryptographic protection—a security property where an adversary with unlimited computational power, including quantum computers, gains absolutely zero information about the encryption key through analysis of ciphertext. This concept, formalized by Claude Shannon in his 1949 paper "Communication Theory of Secrecy Systems," establishes that certain cryptographic schemes can achieve provable security that cannot be broken through any algorithmic means.
The defining characteristic of perfect security is information-theoretic completeness: the ciphertext is statistically independent of the plaintext when the key is unknown. Mathematically, this means that for every possible plaintext message, there exists a key that could have produced the observed ciphertext, and all such keys are equally probable. An adversary observing the ciphertext learns nothing about which plaintext was actually encrypted.
Perfect security is a special case of the broader category of information-theoretic security (ITPS). While ITPS encompasses any cryptographic system that cannot be broken algorithmically (only through brute force key enumeration), perfect security adds the stronger requirement that ciphertext analysis provides no information whatsoever about the key. This distinction is critical: some information-theoretically secure systems may leak partial information about key properties while remaining computationally infeasible to break, but perfectly secure systems leak nothing.
Perfect security exhibits three fundamental properties:
Unconditional Security: Security does not depend on computational assumptions or the difficulty of mathematical problems. Unlike RSA (which relies on factoring difficulty) or elliptic curve cryptography (which relies on discrete logarithm hardness), perfectly secure systems remain secure even if P=NP or quantum computers become arbitrarily powerful.
Zero Information Leakage: Ciphertext provides no information about the key, plaintext, or any relationship between them. An adversary with infinite computational resources and complete knowledge of the cryptographic algorithm gains no advantage over random guessing.
Perfect security requires true random number generation, not pseudorandom generation. Acceptable entropy sources include:
Never use: Algorithmic PRNGs seeded with low entropy, timestamp-based seeds, or user-provided "random" input without proper entropy measurement.
KERI adopts 128 bits as the minimum for perfect security because:
When implementing secret splitting for perfect security:
For one-time pad backup of seeds:
backup = seed ⊕ padPerfect security for keys does not eliminate all security concerns:
Key Length Requirements: Perfect security typically requires keys at least as long as the message being encrypted, and keys must be truly random (not pseudorandom) and used only once. This creates practical limitations that distinguish perfect security from computationally secure systems.
Claude Shannon's 1949 work established the mathematical foundations of perfect security through his analysis of the one-time pad (also called the Vernam cipher). Shannon proved that the one-time pad achieves perfect security when:
Shannon's proof demonstrated that under these conditions, every possible plaintext is equally likely given any observed ciphertext, making cryptanalysis fundamentally impossible.
Two primary cryptographic schemes have been proven to achieve perfect security:
One-Time Pad (OTP): The classical example combines plaintext with a random key using modular addition (XOR for binary data). Given ciphertext C = P ⊕ K (where P is plaintext and K is the random key), an adversary cannot determine P without K because every possible plaintext has an equally probable key that would produce the observed ciphertext.
Secret Splitting/Sharing: Schemes like Shamir's Secret Sharing can achieve perfect security for the secret splitting operation itself. When a secret is split into N shares using truly random coefficients, any subset of fewer than the threshold M shares provides zero information about the original secret. This is perfect security for the splitting operation, though reconstruction requires secure channels.
Historically, perfect security has been reserved for the most critical communications due to severe practical constraints:
These limitations led to the development of computationally secure cryptography (AES, RSA, etc.) for most applications, reserving perfect security for scenarios where the highest security level justifies the operational burden.
KERI's architecture recognizes perfect security as the highest security level for protecting the most critical cryptographic material: seeds, salts, and private keys. The KERI whitepaper explicitly identifies perfect security as a design goal for the foundational entropy that generates autonomic identifiers.
KERI's approach to perfect security focuses on key generation and storage rather than message encryption. The critical insight is that while perfect security for all communications may be impractical, achieving perfect security for the root entropy that generates an entire identity system is both feasible and essential.
KERI adopts 128 bits of entropy as the practical threshold for perfect security in key generation. This standard, documented in the XORA whitepaper and SeedQuest presentation, provides security equivalent to requiring an adversary to perform 2^128 brute force trials.
The practical implications are staggering: even with 1 million supercomputers each performing 1 quadrillion (10^15) key trials per second, exhaustive search would require approximately 8.6 billion years. This makes brute force attacks completely infeasible with any conceivable computational resources, including quantum computers.
KERI's Three R's of Key Management (Reproduction, Rotation, Recovery) incorporate perfect security principles:
Reproduction: Hierarchically deterministic key derivation from a perfectly secure seed enables generation of unlimited derived keys without storing each key individually. Only the root seed requires perfect security protection.
Recovery: Secret splitting schemes enable perfect security for seed backup and recovery. When a 128-bit seed is split into N shares using truly random splitting values, any subset smaller than the threshold M provides zero information about the original seed.
Rotation: While key rotation events themselves use computationally secure signatures, the pre-rotation mechanism protects unexposed future keys with perfect security through cryptographic hiding. An adversary who compromises current signing keys gains no information about pre-rotated keys that have never been exposed.
The XORA (Exclusive Or Accumulator) design demonstrates KERI's application of perfect security principles to cryptographic accumulators. XORA leverages the mathematical properties of XOR operations to create accumulators with information-theoretic security:
XORA's approach shows how perfect security principles can extend beyond traditional encryption to novel cryptographic constructions needed for verifiable credentials and selective disclosure.
SeedQuest represents KERI's practical implementation of perfect security for seed generation and recovery. The system achieves 128-bit perfect security through:
Gamified Mnemonic Generation: A role-playing game generates cryptographic seeds through gameplay, creating 128 bits of entropy from:
Elaborative Encoding: The game leverages human memory capabilities for complex spatial-temporal-visual-auditory experiences, making the 128-bit seed memorable through dramatic, exciting gameplay rather than requiring memorization of random strings.
One-Time Pad Recovery: SeedQuest supports optional one-time pad backup where the seed is XORed with a random pad, providing perfect security for the backup. The pad can be stored separately from the XORed result, and both are required for recovery.
This approach solves the fundamental tension between perfect security (requiring high entropy) and human usability (requiring memorability) by encoding the entropy in memorable experiences rather than random strings.
Perfect security in KERI applies to specific, critical components:
Root Seed Protection: The seed or bran that generates an autonomic identifier should be protected with perfect security. This seed is the ultimate root of trust—compromise of the seed means complete compromise of the identity. Using 128-bit truly random seeds with perfect security storage (secret splitting, one-time pad backup) provides unconditional protection.
Key Derivation: Once a perfectly secure seed exists, hierarchically deterministic derivation can generate unlimited keys for different purposes without requiring perfect security for each derived key. The derived keys inherit security from the root seed's perfect security.
Backup and Recovery: Secret splitting with perfect security enables distributed backup where M-of-N shares are required for recovery, and any subset smaller than M provides zero information about the seed. This allows geographic distribution of backup shares without compromising security.
Delegation Hierarchies: In delegated identifiers, the root AID should use perfect security for its seed, while delegated identifiers can use computationally secure keys. This creates a bivalent security architecture where the root provides perfect security and delegates provide operational flexibility.
Perfect security provides several critical advantages for identity systems:
Quantum Resistance: Unlike RSA, elliptic curve cryptography, or other computationally secure schemes, perfect security remains valid regardless of quantum computing advances. A 128-bit perfectly secure seed cannot be broken by quantum computers because no algorithm (quantum or classical) can extract information that isn't present in the ciphertext.
Long-Term Security: Identities protected by perfect security at their root remain secure indefinitely. There is no "harvest now, decrypt later" threat where adversaries collect encrypted data hoping future computational advances will enable decryption.
Provable Security: Perfect security provides mathematical proofs of security rather than relying on assumptions about computational hardness. This eliminates uncertainty about whether future mathematical breakthroughs might compromise security.
Simplified Threat Modeling: With perfect security for root seeds, threat analysis can focus on operational security (protecting key usage) rather than cryptanalytic attacks on the keys themselves.
Perfect security involves significant trade-offs that limit its applicability:
Key Length Requirements: Perfect security typically requires keys at least as long as the data being protected. For seed protection this is manageable (128-bit seeds are practical), but for encrypting large messages it becomes impractical.
True Randomness: Perfect security requires truly random keys, not pseudorandom keys generated by algorithms. This necessitates hardware random number generators or other true entropy sources, adding complexity and cost.
One-Time Use: Keys providing perfect security generally cannot be reused. One-time pads must use each key bit exactly once. Secret splitting schemes require new random splitting values for each secret. This creates key management overhead.
Distribution Challenges: Perfectly secure keys must be distributed through perfectly secure channels, creating a bootstrapping problem. In practice, this often means physical key distribution or using computationally secure channels to distribute perfectly secure keys (accepting computational security for the distribution phase).
Storage Requirements: Storing perfectly secure keys requires secure storage infrastructure. For 128-bit seeds this is manageable, but for one-time pads matching message lengths, storage becomes prohibitive.
Usability Constraints: Perfect security often conflicts with usability. Random 128-bit strings are not human-memorable, requiring either secure storage devices or mnemonic schemes like SeedQuest that encode entropy in memorable experiences.
KERI's architecture demonstrates a pragmatic approach to perfect security:
Perfect Security Where Critical: Root seeds and splitting values use perfect security (128-bit true randomness, one-time use, secret splitting)
Computational Security Where Practical: Event signing, witness receipts, and ACDC signatures use computationally secure algorithms (Ed25519, etc.) that provide adequate security with better performance
Hybrid Schemes: Pre-rotation combines computational security (for current keys) with perfect security properties (for hidden future keys), providing practical operation with strong security guarantees
Layered Security: Delegation enables security layering where root identifiers use perfect security while operational identifiers use computational security, balancing security and usability
This balanced approach recognizes that perfect security is a tool for specific high-value targets (root seeds, critical secrets) rather than a universal requirement for all cryptographic operations. By applying perfect security selectively to the most critical components, KERI achieves strong overall security without the operational burden of perfect security everywhere.
Perfect security protects against cryptanalytic attacks but not against operational compromises like malware, physical theft, or coercion.