# Token-based Consumption

In traditional business models, consumers pay for products and services at a price that includes a markup over cost, while profits are typically distributed back to **shareholders** through dividends.

RoamFi redefines this mechanism — when users **hold and spend the governance token $RF**, they receive **direct value benefits** from their consumption. This approach extends the concept of value sharing beyond shareholders to **all token holders**.

### Mechanism Design

* When users exchange $RF for account balance ($RUSD) and use it for consumption, the system converts $RF to $RUSD **at a 1:1 market rate**, and provides an **additional 20% bonus** in $RUSD balance.
* This mechanism not only encourages users to choose $RF as a preferred payment method, but also reinforces the alignment between **token utility**, **governance rights**, and **value growth**.

### Advantages and Impact

* **User Incentives:**\
  Expands real-world use cases for the governance token and increases demand, strengthening token value and circulation.
* **Governance Integration:**\
  Aligns token ownership with real consumption activity — uniting governance rights and usage rights under one ecosystem.
* **Operational Efficiency:**\
  Payments made in $RF can be directly stored in the project’s on-chain treasury without complex conversion processes, improving efficiency and security of fund management.

This mechanism not only brings **immediate benefits to users**, but also enhances the **practical value and utility** of $RF — creating a **positive feedback loop** connecting **consumption, governance, and treasury growth**.


---

# Agent Instructions: 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://docs.roamfi.net/tokenomics/token-based-consumption.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.