> For the complete documentation index, see [llms.txt](https://wp.jannavi.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wp.jannavi.net/mahjong-big-data-depin-project/integration-of-jn-token-and-depin-ecosystem.md).

# Integration of JN Token and DePIN Ecosystem

This section explores the integration of the JN Token within the Mahjong Big Data Project, highlighting its essential role in enhancing data transactions and incentivizing participation within the Jan-Navi ecosystem.

* **Means of Rewards and Payments** The JN Token operates as the core currency within the JAN-Navi DePIN platform. Mahjong parlors that contribute data are compensated with JN Tokens, motivating them to share valuable gameplay data. These tokens are further utilized to manage operational expenses such as event organization and marketing, ensuring efficient financial operations across the platform.
* **Building a Token Economy** The JN Token is used extensively within the DePIN platform, acting as the primary medium of exchange for services and transactions. This setup develops a self-sustaining token economy, enhancing the platform's value while ensuring ongoing demand and liquidity for the token.
* **Investment Opportunities** Beyond its functional uses, the JN Token presents attractive investment opportunities through features like staking and lending. Token holders can benefit from the platform's growth and the potential appreciation of the token's value, fostering active and long-term participation in the ecosystem.

This integration not only facilitates operational efficiencies but also strengthens the economic foundations of the JAN-Navi platform, promoting growth and sustainability in the competitive online gaming market.


---

# 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://wp.jannavi.net/mahjong-big-data-depin-project/integration-of-jn-token-and-depin-ecosystem.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.
