# Multi-Plane Failure Scenarios

This section analyzes representative worst-case compound failure scenarios and their impact on solvency, accounting correctness, and user withdrawals.

#### Scenario A — One External Execution Environment Unavailable, Others Healthy

* Valuation from the affected environment is conservatively excluded from NAV.
* Strategies in healthy environments continue operating normally.
* The zkSync vault remains fully solvent.
* Withdrawals are serviced using available local liquidity and validated unwinds from healthy environments.

#### Scenario B — Low-Latency Execution Environment Halts Mid-Cycle

* Affected strategies are frozen at their last validated state.
* Partial or in-flight returns are excluded until fully validated.
* NAV excludes affected environment values during the outage.
* Withdrawal queues resume processing once validated liquidity returns.

#### Scenario C — All External Execution Environments Unavailable

* The system continues operating using only strategies native to the canonical settlement layer.
* External environments are conservatively valued at zero for accounting purposes.
* Users may continue withdrawing using available local liquidity.
* NAV integrity and solvency remain preserved.

#### Scenario D — Validation Layer Degradation

* No new external state updates are accepted.
* NAV remains frozen at the last validated state.
* Strategies may continue operating but cannot influence accounting.
* The system enters a conservative safety mode prioritizing correctness over liveness.

In all scenarios, failures degrade performance or availability but cannot cause insolvency, accounting drift, or user fund loss.


---

# 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/securing-multistake/multi-plane-failure-scenarios.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.