# Safety Principles

Multistake enforces the following deposit/withdraw invariants:

1. **Never mint shares without zkSync-recognised assets.**
2. **Never burn shares unless validated liquidity is available.**
3. **No strategy plane may alter supply or NAV.**
4. **Discount stale or invalid planes automatically.**
5. **Withdrawal queue always respects FIFO ordering.**
6. **NAV cannot rely on unfinalised cross-chain state.**

These rules ensure safety even under network splits, bridge congestion, or execution-plane outage.


---

# 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/deposit-withdrawal-semantics/safety-principles.md?ask=<question>
```

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.