Loading vLEI.wiki
Fetching knowledge base...
Fetching knowledge base...
This comprehensive explanation has been generated from 79 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.
Base64 is a group of binary-to-text encoding schemes used in computer programming to represent binary data—specifically sequences of 8-bit bytes—as sequences of 24 bits that can be represented by four 6-bit Base64 digits. In the KERI ecosystem, Base64 encoding uses the URL-safe variant (RFC-4648) with the character set [A-Z, a-z, 0-9, -, _], explicitly excluding the = pad character that appears in naive Base64 implementations.
Base64 encoding is foundational to CESR (Composable Event Streaming Representation), which provides the dual text-binary encoding infrastructure for KERI. Within CESR:
KERI specifically uses Base64 URL-File safe encoding variants that replace problematic characters (+ becomes -, / becomes _) for web-based transmission and filename compatibility. This ensures KERI prefixes, events, and credentials can be safely transmitted over HTTP, stored in URLs, and embedded in filenames without escaping.
[A-Z, a-z, 0-9, -, _] per RFC-4648= pad characters in CESR implementations= padding—strip these for CESR compliance+ and /)A critical distinction in KERI's use of Base64 is the rejection of naive conversion approaches. Traditional Base64 uses trailing = pad characters when input length isn't aligned to 24-bit boundaries. CESR instead uses pre-padding with leading zero bytes before Base64 conversion, ensuring the encoded output is always an integer multiple of 4 characters without requiring trailing pad characters. This enables: