# Validation Pipeline Validation happens entirely on zkSync, ensuring a single trusted domain. #### **1. State Validation** Confirms that balances or LP tokens exist and match chain state. #### **2. Price Validation** Cross-checks values against multiple sources, ensuring: * deviation limits * consistent TWAP alignment * acceptable mark-to-market variance #### **3. Temporal Validation** Ensures reports are not stale, backdated, or out of expected cadence. #### **4. PnL Validation** Compares reported PnL with expected deltas given asset and strategy behaviour. #### **5. Cross-Plane Consistency** Ensures no contradiction with vault allocations, exposure limits, or historical patterns. If *any* check fails, the packet is rejected and the strategy’s value becomes discounted. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://multistake-1.gitbook.io/multistake-docs/documentation/oracle-architecture/validation-pipeline.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.