> For the complete documentation index, see [llms.txt](https://docs.aspidanet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aspidanet.com/aspida/how-it-works/rewards-and-fees.md).

# Rewards and Fees

Aspida currently is running a campaign, hence the protocol fees are currently set at 5% until May 31, 2024, of which, 3% will be allocated to node operators and 2% to Aspida’s DAO’s treasury. The protocol fee will be deducted from the total staking rewards upon each weekly distribution.

The protocol fee will be resumed to 10% (5% to node operators and 5% to Aspida DAO treasury) after the campaign. This allocation and distribution proportion can be adjusted through DAO governance in the future.  

The following table details the current distribution of  liquid staking rewards and fees:

| Entity        | Rewards |
| ------------- | ------- |
| Stakers       | 95%     |
| Node Operator | 3%      |
| Aspid DAO     | 2%      |

Updated 09.03.2024


---

# 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.aspidanet.com/aspida/how-it-works/rewards-and-fees.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.