# V2.0 Flows

{% hint style="danger" %}
The contracts for V2.0 flows are yet to go through the audit.
{% endhint %}

1\. Depositor approves the amount.

2\. Depositor sends the amount to the fund contract (deposit request).

* Depositor can cancel the deposit request.

3\. Operator triggers NAV update (settle deposit and redemptions at new NAV price).

* If deposits = redemptions, both net out.
* If deposits > redemptions, both net out, but excess capital gets swept into the custody contract.
* If deposits < redemptions, both net out, but the operator/automation needs to provide enough liquidity in the fund contract before being able to execute.

4\. Depositor comes back and claims their assets.<br>

**Pros:**

* Depositors enter/exit vault at the time of a NAV update (everyone at the same time)
* Depositors are still required to come back to claim their assets after the flows are settled, but when they come back doesn’t impact the price of their assets or operator operations.<br>

**Cons:**

* There is no incentive to generate speculative volume  volume in/out of the vault (because no one can game the system within the vault itself).


---

# 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://docs.rethink.finance/rethink.finance/protocol/architecture/admin-contract/flows/v2.0-flows.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.
