> For the complete documentation index, see [llms.txt](https://docs.dittonetwork.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dittonetwork.io/ditto-earn/ditto-musd-savings-vault/withdrawals.md).

# Withdrawals

Request dMUSD redemption, wait for batch funding, then claim MUSD on Mezo.

The V2 flow is **request → settle → claim**. All user transactions are on Mezo and use BTC for gas. Use the [vault that holds your shares](https://docs.dittonetwork.io/ditto-earn/ditto-musd-savings-vault/deployments); pilot and V2 requests are separate.

## 1. Request

On the **Withdraw** tab, enter dMUSD and confirm **Request withdrawal**. The shares are locked into the current batch. The MUSD amount shown is an estimate; the final entitlement uses the share price fixed at batch close.

## 2. Wait for settlement

Current operator policy makes a non-empty batch due when either trigger is reached:

| Trigger | Value                                            |
| ------- | ------------------------------------------------ |
| Size    | 100 MUSD of queued shares at the published price |
| Age     | 24 hours since the batch opened                  |

An empty batch stays open. If it is already 24 hours old, the next request makes it due immediately. **Due is not the same as closed:** operators must execute the close, then fund it.

V2 also publishes NAV after 48 hours without a successful price publication, subject to safety checks and network availability. That standalone update does not close or fund a withdrawal batch and is not a settlement deadline. The batch triggers above are unchanged.

The vault pays from its Mezo buffer where possible. Otherwise, funds return from Spark through the bridge and a swap back to MUSD. A buffer payment is generally faster; RPC, operator, venue or bridge delays can extend either path. Do not treat the displayed estimate as a deadline.

## 3. Claim

When **Your withdrawals** shows an amount ready to claim, press **Claim**. MUSD is paid to your wallet. This is a separate transaction; funds do not arrive automatically just because the batch settled.

Partial emergency funding may permit a partial claim, with the remainder payable after more funding. Already funded claims remain callable while the vault is Paused or Deprecated. V2 also preserves requests and cancellation after deprecation; pause can delay normal settlement.

## Cancellation

Cancel only while the batch is **Open**. Your dMUSD returns to your wallet. If the batch is already due by size or age, it may close before a cancellation transaction is included. Once closed, cancellation is no longer possible.

## Statuses

| Status           | Meaning                                                         |
| ---------------- | --------------------------------------------------------------- |
| Open             | Requests accepted; cancellation possible                        |
| Processing       | Closed; waiting for funding                                     |
| Partially funded | Claim only the amount currently available; retain the remainder |
| Settled          | Funding complete; any unclaimed entitlement can be claimed      |

For wallet/frontend implementation, use [Mezo UI integration](https://docs.dittonetwork.io/ditto-earn/ditto-musd-savings-vault/integration). The on-chain claimable amount—not a timer or estimated bridge arrival—determines whether Claim is enabled.