> For the complete documentation index, see [llms.txt](https://docs.more.markets/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.more.markets/more-vaults/core-concepts/registries.md).

# Registries

Registries are simple on‑chain catalogues.

## Types of Registries

There are three registries included in the protocol:

* Vaults are registered on the Vault Factory of each chain;
* Whitelisted protocols and their corresponding facets are registered on the Vault Registry;
* Oracles are registered on the Oracle Registry.

A registry never blocks a contract call. It only stores information that front‑ends, analytics, and governance can consult to verify the trustworthiness of the component.

## Permissioned Vaults

When an item has been audited and a DAO vote confirms the findings, the identical identifier (the address and list of selectors) is copied into the DAO‑approved registry. From this moment on nothing about the contract itself changes. However, if an item is upgraded, it must be re-approved to be updated in the registry. The DAO‑approved registry therefore acts as an overlay that labels items as verified.


---

# 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.more.markets/more-vaults/core-concepts/registries.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.