> For the complete documentation index, see [llms.txt](https://docs.enzyme.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enzyme.finance/onyx-user-documentation/enzyme-vault/subscription/deposits/synchronous-deposits.md).

# Synchronous Deposits

## Synchronous Deposits

In addition to the standard asynchronous deposit queues, vaults can also use **synchronous deposits** as an alternative or complementary deposit mechanism.

### Overview

Synchronous deposits allow depositors to make **instant deposits** without going through a deposit queue and without requiring administrator approval.

This feature is best suited for vaults with slowly changing portfolio values and share prices typically vaults focused on yield generation. It is **not recommended** for vaults with volatile portfolio valuations, when the NAV is not updated regularly as outdated share prices could expose the vault to arbitrage risk.

{% hint style="warning" %}
Unlike the standard deposit queue, a synchronous deposit is processed immediately at the current share price, the moment the depositor submits it.
{% endhint %}

### Deposit Window

To prevent deposits from being processed against an outdated share price, vault administrators can configure a **deposit window**. This defines the period during which synchronous deposits are accepted, starting from the most recent valuation update.

{% hint style="info" %}

#### Without a threshold duration

Synchronous deposits are always open. There is no time restriction after a valuation update. Combined with our NAV automation mechanism, this enables a fully synchronous and automated framework.
{% endhint %}

{% hint style="info" %}

#### With a threshold duration

1. The administrator updates the vault's valuation.
2. A **deposit window** opens immediately for the duration of the threshold.
3. Depositors can make instant deposits during this window.
4. Once the window expires, synchronous deposits are **refused** until the next valuation update.

This mechanism ensures that if a valuation update is missed for any reason, deposits are automatically blocked rather than processed at a stale price.

**Example 1:** If the vault NAV is updated every 24 hours and the deposit window is set to 12 hours, synchronous deposits will be available up until NAV Update H+12, for the remaining time before the next NAV update, sync deposits won't be possible. 
{% endhint %}

### Configuration

Enzyme will set up the **Synchronous Deposits** and the **Deposit Window** at vault deployment but this can be configured and updated throughout the lifetime of the vault.

Synchronous deposits can be configured in two ways:

* **As an additional mechanism** used alongside the standard deposit queue, giving depositors both options.
* **As a full replacement :** the standard deposit queue is disabled entirely, and all deposits go through the synchronous path.

<figure><img src="/files/VDfNsSTGzS9KLwLGreHp" alt="" width="375"><figcaption></figcaption></figure>

### Deposit Assets

The deposit queue and synchronous deposits operate independently. Deposit assets can differ between both methods, allowing managers to define distinct subscription paths with asset sets tailored to each deposit route.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.enzyme.finance/onyx-user-documentation/enzyme-vault/subscription/deposits/synchronous-deposits.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.