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

# Tokenomics

<figure><img src="/files/jmRSQ0OrlUwwAOBf8Fuz" alt=""><figcaption></figcaption></figure>

The $MDEV tokenomics have been designed to align incentives across the entire ecosystem, powering rewards, access, governance and growth as wellness data moves on-chain. Here are the key mechanisms enabled by the token:\
\
1\. Rewards & Participation Earn $MDEV by contributing value: from sharing data captured through sensors, completing wellness goals, or engaging in research and community activity. Every action that strengthens the ecosystem is rewarded.

2\. Access & Utility Spend tokens to unlock real utility: AI insights, professional consultations, encrypted communications and integrations with external apps and devices.

3\. Governance & Ownership Stake tokens to secure the network and participate in key protocol decisions: giving the community real influence over how the system evolves.

4\. Deflationary Design A portion of every transaction and service fee is burned, while staking locks supply: creating natural scarcity and reinforcing long-term value as adoption grows.


---

# 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://mdev-1.gitbook.io/litepaper/tokenomics.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.