# Asynchronous Withdrawals Withdrawals that involve external execution environments require asynchronous state transitions. The zkSync vault explicitly tracks: * Pending unwind commitments. * Arrival and reconciliation of returned liquidity. * Validation status of returned balances. * Completion conditions for queued withdrawal requests. Even in the presence of asynchronous execution and settlement delays: * ERC-4626 conversion functions remain deterministic. * Rounding and accounting semantics remain intact. * NAV remains accurate at every finalized block. * Users cannot exploit unsettled or in-flight liquidity. This design ensures that withdrawal correctness and solvency guarantees are preserved independently of execution timing variability or cross-environment settlement latency. --- # 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/asynchronous-withdrawals.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.