> 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/compliance.md). # Compliance Enzyme Vaults can enforce onchain compliance through [Chainlink ACE](https://docs.chain.link/ace) (Automated Compliance Engine), an onchain policy engine. Compliance rules live in dedicated policy contracts, separate from the vault's core logic, so they can be added, changed, or removed without redeploying the vault. ### What can be gated Compliance checks can be applied to the following vault actions: * **Deposits** — both synchronous deposits and request-based deposits * **Redemption requests** * **Share minting and burning** * **Share transfers** — any transfer of vault shares between wallets Checks are configured per action, and a vault may use none, some, or all of them. ### How it behaves When a gated action is performed, the vault passes the details of the action (such as the depositor wallet and the amounts involved) to the policy engine, which evaluates them against the configured policies in order. {% hint style="warning" %} If any policy rejects the action, the entire transaction reverts. The deposit, redemption, mint, burn, or transfer does not take place, and no assets or shares move. {% endhint %} ### Example policies Policies can, for example: * require that a wallet holds a verified identity credential (such as KYC or AML status), using Chainlink ACE's cross-chain identity framework * screen wallets against allowlists and denylists (e.g. sanctioned addresses) * restrict an action to wallets holding a specific role, such as verified or accredited investors * enforce volume or rate limits * pause a given action entirely, or restrict it to certain time intervals The exact set of rules is defined per vault, so the checks a depositor encounters depend on how that vault is configured. ### Configuration Only the vault owner or its admins can enable, replace, or disable compliance checks on a vault. The policy rules themselves are managed on the Chainlink policy engine. Chainlink ACE is one of the validation mechanisms available to Enzyme Vaults — share transfers, for example, can alternatively be restricted using address lists. --- # 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/compliance.md?ask=&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.