> 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/assets.md).

# Assets

Both deposits and redemptions are unrestricted across crypto asset classes. 

## Deposits

Each Enzyme Vault is configured with one or several ***Deposit Assets***, chosen by the Vault Owner or Admin. This asset (any ERC-20 token) is the one required for deposits.\
\
There can be several ***Deposit Assets.***

{% hint style="info" %}
About ***Deposit Assets***

While the Enzyme Vault only accepts funds in the ***Deposit Asset(s)***, Vault Owners can develop an extra layer of onboarding on top of the Vault to swap, bridge, or on-ramp other asset classes. \
\
*Examples:* \
*- Collect funds via bank transfers and on-ramp them into the chosen **Deposit Asset**.*\
*- Collect funds on Solana, bridge them to the the Vault network and swap into the **Deposit Asset**.* 
{% endhint %}

## Redemptions

Vault Owners can configure one or several ***Redemption Assets*** that can vary from the ***Deposit Assets***.

Redemptions are executed on the Enzyme Vault network.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.