> For the complete documentation index, see [llms.txt](https://docs.rairprotocol.org/rairprotocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rairprotocol.org/rairprotocol/whitepaper-draft/start/mechanics/demand-side-deflation.md).

# Demand Side (Deflation)

A portion of revenue from all official RAIRprotocol Dapps is used to buy back token supply. To become an official RAIRprotocol Dapp, members sign an agreement with the RAIRprotocol DAO for up to 20% revshare. Revshare is used to buy back tokens. 

**Launch Dapp Example (DevDapp)**

DevDapp is engaged to distribute 100k prize pool to incentivize developer network.

* 80% or 80k goes directly to Developers
* 20% or 20k captured as revenue by DevDapp
  * Buy Back:  20% of revenue or 4k used to buy back RAIR tokens 

**Alt Dapp Example**

An official Alt Dapp launches an unrelated service using RAIRprotocol open source. Enters into agreement with RAIRprotcol DAO for revshare. 

Audit revenue onchain and match required RAIR token payment to DAO treasury via smart contract. 


---

# 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.rairprotocol.org/rairprotocol/whitepaper-draft/start/mechanics/demand-side-deflation.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.