> For the complete documentation index, see [llms.txt](https://templefi.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://templefi.gitbook.io/whitepaper/products/earn/staking.md).

# Staking

Staking serves a crucial purpose to keep the price floor stable and reward loyal community members with high yield which includes revenue share from every swap transaction on the DEX.   

Holders of $Temple can stake their tokens which will earn them real-yield rewards which comes from the trading fees and additional $Temple. Real yield is paid out daily automatically.   

### Real-yield daily rewards 

Real-yield for $Temple stakers will look as follows:  

* staked supply: 20%
* 24h volume: 10,000,000$
* fees collected: 5,000$
* **1000 $Temple staked daily rewards: 250$ and additional $Temple**   

### **$Temple Staking info:**

* APR: depends on the number of tokens staked and trading volume 
* Deposit and withdraw fee: 0% 
* Rewards: $Temple and ETH


---

# 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://templefi.gitbook.io/whitepaper/products/earn/staking.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.