Loading vLEI.wiki
Fetching knowledge base...
Fetching knowledge base...
This comprehensive explanation has been generated from 9 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.
A control parameter in CESR stream parsing that specifies which portion of a CESR stream will be processed by which parsing code component, enabling modular and efficient stream processing.
The strip-parameter is a directive mechanism within CESR (Composable Event Streaming Representation) stream parsing that determines the routing of stream segments to appropriate parsing code. It functions as a dispatch control that tells the parser which code component should handle which portion of the incoming CESR stream, enabling modular and specialized processing of different stream sections.
Within the KERI ecosystem, the strip-parameter plays a critical role in the Parside parsing architecture. Parside is KERI's CESR stream parser responsible for extracting and processing streams of bits from CESR-encoded data. The strip-parameter enables Parside to implement a separation of concerns between different parsing responsibilities:
This architectural division leverages CESR's self-framing property, where each primitive contains sufficient information to determine its own boundaries. The strip-parameter acts as the routing mechanism that dispatches different portions of the stream to the appropriate specialized parser based on the content type and structure.
The strip-parameter enables a modular parsing architecture where:
Implementations should:
Strip-parameter behavior depends on the active version code:
The sniffer component works with strip-parameters to:
The strip-parameter enables chunk-delimited processing rather than full stream iteration. When Parside encounters a count code at the beginning of a stream section, the strip-parameter determines:
This mechanism is essential for handling heterogeneous streaming data where a single CESR stream may contain mixed serialization formats (CESR binary, CESR text, JSON, CBOR, MessagePack) that require different parsing strategies.
The strip-parameter's behavior is influenced by the active version code, which determines which CESR code table is loaded. When Parside encounters a version count code, it switches parsing context and may redirect subsequent stream portions to different code paths based on the version-specific table definitions.