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

# Revenue Share

A key feature of the $RBLK tokens is Rollblock's commitment to distributing a share of its weekly revenue to token holders transparently.

Up to 30% of Rollblock's weekly generated revenue will be shared with RBLK holders. This revenue sharing will occur through two primary methods.

Buyback and Burn - 60% of the revenue shared from Rollblock's profits will be used to buy back $RBLK from the open market and these will be sent directly to a burn wallet where the tokens will be taken out of circulation forever. Thus, reducing the circulating and total $RBLK supply.

Staked $RBLK - 40% of Rollblock's weekly generated revenue will be allocated to reward our stakers for holding and staking $RBLK tokens. This distribution will be conducted regularly and will be proportional to the amount of $RBLK each participant has staked.


---

# 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://whitepaper.rollblockpresale.io/whitepaper/revenue-share.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.