# ASCII Diagram — Deposit/Withdraw Flow

```vb
Deposits:
User → zkSync Vault → Mint Shares → Allocation to Planes (async)

Withdrawals (fast):
User → zkSync Vault → Burn Shares → Transfer Assets

Withdrawals (async):
User → Withdrawal Queue → Strategy Unwind → Bridge Back → Validate → Burn → Transfer

L1 Exit:
Vault → zkSync Exit → L1 Proof → User Claim

```

### 8.7 Summary

Multistake preserves ERC-4626 semantics in a multi-chain execution environment by strictly centralising accounting on zkSync. Deposits and withdrawals remain predictable and deterministic, even when strategies operate asynchronously on remote planes. The protocol enforces delayed minting, delayed burning, oracle validation, and queue-based solvency preservation to ensure correctness under all conditions.

***


---

# 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/deposit-semantics/ascii-diagram-deposit-withdraw-flow.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.