> For the complete documentation index, see [llms.txt](https://samurainodes.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://samurainodes.gitbook.io/docs/2.-understanding-the-nodes/2.7-i-dont-see-my-rewards-every-4-or-8-hours.-is-there-a-problem.md).

# 2.7 - I don’t see my rewards every 4 or 8 hours. Is there a problem ?

Sometimes the distribution of rewards may be delayed, and can take more than 4 to 8 hours to propagate. (Especially if you are waiting for your first cycle of rewards.)

The reason is that the function of distributing tokens to nodes requires **large amounts of gas**, and the transaction sometimes fails.  🛠 We've reduced the time between distributions to every 4 hours (instead of 8 hours).

**Important : The rewards and expected distribution time are an estimate. Its is not 100% guaranteed that noders will be always rewarded in accordance with the expected schedule. Rewards can lower or increase depending on the market fluctuations and the evolution of the SAMURAI protocol.**


---

# 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://samurainodes.gitbook.io/docs/2.-understanding-the-nodes/2.7-i-dont-see-my-rewards-every-4-or-8-hours.-is-there-a-problem.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.