> For the complete documentation index, see [llms.txt](https://otoco.gitbook.io/otoco/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://otoco.gitbook.io/otoco/part-ii.-the-otoco-token-a-loyalty-scheme-usage-token-and-voting-card-all-in-one/untitled.md).

# 2. “Proof of sale” rewards

A second key departure from the token models we studied is in how we plan to use the OTOCO token to reward outside developers in function of how well their products sell in the online, competitive marketplace otoco.io is building.

In addition to the ETH-based revenue sellers generate as a result of selling their dApps via the store, extra rewards in OTOCO tokens will kick in based on volume sold.

Such sales-based token rewards would add an extra dynamic to the OTOCO token price and link its value directly to user demand for add-on components.

At the same time, all OTOCO holders and the OtoCo Foundation itself would share in the new mint linked to revenue generated by third-party developers, which in turn may feed into the value of otoco.io and its token.


---

# 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:

```
GET https://otoco.gitbook.io/otoco/part-ii.-the-otoco-token-a-loyalty-scheme-usage-token-and-voting-card-all-in-one/untitled.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.