# Asynchronous Deposits

The default deposit mechanism is asynchronous and relies on a queue.

**Deposit Requests** can :

* Be arbitrarily processed by Vault Owners or Managers
* Be executed in batch
* Be cancelled by the depositor after a waiting period defined by the Vault Owner or Admins

**Deposit Requests cannot** be cancelled by Vault Owner and Admins (*Subscriptions are on-chain transactions and only the initiator can revoke them*). However, Vault Owners and Admins may choose to ignore pending requests.

{% stepper %}
{% step %}

### Investor deposit funds

The investor submits a deposit request, which enters a dedicated queue.
{% endstep %}

{% step %}

### Deposit Processing - NAV Calculation and Reporting

Before new Vault Shares can be issued, the Vault Owner or Admin must evaluate the portfolio's underlying assets and positions, and report the ***Portofolio Value*** in the Administration App. 
{% endstep %}

{% step %}

### Deposit Processing - Deposit Request Execution

The Vault Owner or Admin approves pending deposit requests. This action triggers the issuance of Vault Shares, proportionally to the stake held in the Vault, which are then transferred  to the depositor’s wallet.
{% endstep %}

{% step %}

### Funds consolidation in the Vault

Once approved, the deposited funds are transferred into and consolidated within the Vault smart contract.
{% endstep %}

{% step %}

### Transfer to Management Wallet

After processing, Vault Owners or Admins may withdraw funds from the Vault smart contract to the Management Wallet.
{% endstep %}

{% step %}

### Strategy execution

From the ***Management Wallet***, managers are free to deploy funds across any system, protocol, or asset in line with their strategy.
{% endstep %}
{% endstepper %}