# Cross-Chain Safety Guarantees

The vault enforces strict consistency even when execution planes fail or desynchronize. Four key properties ensure safety:

#### **Isolation**

No plane can manipulate share supply or NAV.\
A compromised strategy executor cannot alter accounting.

#### **Conservatism**

Any stale or invalid plane automatically contributes zero or discounted value to NAV.

#### **Finality Dependence**

Deposits modify supply only after zkSync settlement.\
Withdrawals burn shares only after liquidity is present.

#### **Bridge Safety**

L1 deposits and L1 exits rely on BridgeHub’s canonical message ordering and zk proof validation.

The vault is engineered so that the worst-case behavior across any execution plane is *valuation exclusion*, not insolvency.


---

# 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/zksync-home-vault/the-core-of-multistake/cross-chain-safety-guarantees.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.