> For the complete documentation index, see [llms.txt](https://thealtitudeproject.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://thealtitudeproject.gitbook.io/docs/everest-vault/how-rewards-work.md).

# How Rewards Work

Rewards in the Everest Vault are funded by ecosystem activity, project fees, and external revenue. USDC is deposited into the vault reserve and then distributed to stakers over time.

The planned reward model pays out 3% of the available USDC reserve daily in real time to vault participants.

A user's share of rewards is based on their share of the staked Altitude in the vault. This is similar to how many staking pools distribute rewards: the more of the pool a user represents, the larger their share of the distributed rewards.

## Example

If a user owns 10% of all Altitude staked in the vault, that user would receive 10% of the USDC rewards emitted by the vault during that period.

## Claiming

Rewards can be claimed at any time.

There are no claim deadlines. This means smaller holders can allow rewards to build up before claiming, rather than being forced to claim frequently.

## Withdrawals

There is no token vesting. Users can withdraw their staked Altitude at any time, subject to the vault's withdrawal fee.

{% hint style="warning" %}
The Everest Vault is in development. Final contract rules, fees, and reward mechanics should always be checked before interacting with the vault.
{% endhint %}


---

# 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://thealtitudeproject.gitbook.io/docs/everest-vault/how-rewards-work.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.