> For the complete documentation index, see [llms.txt](https://astrofarms.gitbook.io/astrofarms/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://astrofarms.gitbook.io/astrofarms/astrovaults/astro-vaults.md).

# AstroVaults

![](/files/-Mdzu4j7GHfyzZYLR-j-)

### We have been moving fast.  Months ahead of schedule, we have even launched our Vaults, right on our first Layer Cancer.  

Stay Tuned for new Vaults at any moment! 

**What are AstroVaults?**

One of our many reward systems.  One of the main reasons we use our vaults is to give back to our AstroFam.  We reward you for holding our tokens.  We decided to take a portion of our deposit fee and simply, purchase stables that you want to earn.  

**We offer 0% transaction fees on our Vaults.** 

### **Deposit our natives and earn a variety of different tokens.** 

Trust us… it’s written in the stars. 

Only Possible in AstroFarms™, as we are committed to being THE constellation for Polygon DeFi.

### View Vaults on Live Missions.  View Vault Contracts under the [Contracts](/astrofarms/contracts-security/contracts.md) tab.


---

# 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://astrofarms.gitbook.io/astrofarms/astrovaults/astro-vaults.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.