# Architecture

<figure><img src="/files/mbBbjaUK8nYUMNqHaAYj" alt=""><figcaption></figcaption></figure>

To enable flexible strategy deployment, Enzyme.Onyx uses an Enzyme Vault as the tokenization layer, with strategies deployable through any wallet type, including EOAs (MetaMask, Phantom...), MPCs (Fireblocks...), Smart Accounts (Safe...), and Cold Wallets (Ledger...).

### Enzyme Vaults - Subscription and Accounting

The Enzyme Vault acts as the tokenization layer, providing a natively tokenized structure that supports deposits and redemptions, issues Vault Shares (ERC20), and consolidates fees.

At the Vault level, the value of the underlying strategy is consolidated, ensuring accurate NAV computation and per-share valuation.

{% hint style="info" %}
Learn more about Enzyme Vaults [HERE](https://enzyme-finance.gitbook.io/onyx/enzyme-vault/overview).
{% endhint %}

### Wallets - Custody and Management

While the Enzyme Vault collects funds and provides the tokenized structure, custody and execution of the underlying strategy are handled by Wallets (***Management Wallet***).

Vault owners can leverage their preferred custody stack to deploy any strategy of their choice, without any kind of boundaries.

{% hint style="info" %}
Lean more about Wallets [HERE](https://enzyme-finance.gitbook.io/onyx/getting-started/publish-your-docs).
{% endhint %}

***

## What Onyx isn't?

Onyx is not a micro-management tool. It provides the tokenization layer that can be deployed on top of any wallet, enabling the tokenization of any type of strategy.

Onyx does not monitor, track, or restrict how the tokenized value or assets are managed.


---

# 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.enzyme.finance/onyx-user-documentation/getting-started/quickstart/architecture.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.