# Security Invariants The protocol enforces eight fundamental invariants.\ These invariants are **non-negotiable properties** guaranteeing solvency and correctness, independent of execution-plane behaviour. #### **Invariant 1 — NAV cannot increase from unvalidated data** No remote-plane report affects accounting before oracle validation. #### **Invariant 2 — Share supply immutable except through zkSync vault** No plane, no strategy, no bridge, no relay can mint/burn. #### **Invariant 3 — Capital in transit always valued at zero** All cross-chain movements are non-inflationary. #### **Invariant 4 — FIFO withdrawals** Fairness enforced regardless of async latency. #### **Invariant 5 — Strategies isolated** Failure in one strategy cannot influence another. #### **Invariant 6 — Planes isolated** Failure in one execution plane cannot affect another. #### **Invariant 7 — Discount stale or inconsistent data** Any validation failure triggers conservative fallback. #### **Invariant 8 — Only zkSync finality creates user balances** Deposits must reach zkSync; withdrawals must be present on zkSync. These invariants are the **mathematical core** of the security model. --- # 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/security-model/security-invariants.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.