> For the complete documentation index, see [llms.txt](https://terminus-1.gitbook.io/terminus-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://terminus-1.gitbook.io/terminus-docs/token-and-value-accrual/tmns-utility.md).

# TMNS Utility

`TMNS` is not intended to replace the assets users spend through Terminus. It is intended to reward and coordinate the actors who help the network grow.

This utility model is deliberately aligned with payment reality. Users should remain free to pay in widely recognized digital assets, while `TMNS` creates an incentive and governance layer around the network itself.

## Ecosystem Growth Incentives

The primary utility of `TMNS` is to incentivize the behaviors that expand network density. This includes user growth, partner activation, merchant-side acceptance expansion, and ecosystem contributions that increase transaction relevance over time.

In practice, this means the token can be used to reward:

* real payment usage,
* useful referrals and channel growth,
* new market expansion,
* and ecosystem participation that improves transaction throughput or retention.

## Partner Onboarding and Participation

As Terminus grows across Southeast Asia, the network will need multiple types of external collaborators. `TMNS` can align these participants by giving them a reason to contribute to network growth rather than interact as purely extractive service providers.

This may include:

* onboarding incentives,
* growth-based partner rewards,
* or ecosystem-based participation programs tied to measurable outcomes.

## Staking and Reputation

`TMNS` can also support staking-based participation. In this model, ecosystem actors commit stake as a signal of alignment, reliability, or network seriousness. Over time, this can contribute to a layered reputation system in which aligned participants gain stronger standing inside the network.

This is particularly useful for a system that may involve:

* regional partners,
* channel operators,
* ecosystem contributors,
* or future governance participants.

## Fee Discounts and Access Rights

The token can also create differentiated access or economic benefits for aligned participants. For example, certain categories of partner or power users may receive fee discounts, preferred access, or ecosystem privileges when participating through `TMNS`.

These benefits help create ongoing token demand without forcing the token into the user payment path itself.

## Community Participation

At the community level, `TMNS` creates a mechanism for rewarding early believers, active participants, and network contributors. This matters in Web3 because community support is not only symbolic. It is often one of the strongest drivers of product distribution, ecosystem attention, and early brand resilience.

## Usage Mining With Guardrails

Terminus also intends to support `usage mining`, but not in a naive form. The objective is to reward real economic activity, not low-quality transaction farming.

A robust usage mining system should therefore:

* prioritize successful payments,
* favor repeat users and meaningful merchant interactions,
* use anti-sybil and anti-wash controls,
* and reward network quality rather than just raw transaction count.

When designed correctly, `TMNS` utility becomes a multiplier for real network formation rather than a distraction from product integrity.


---

# 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://terminus-1.gitbook.io/terminus-docs/token-and-value-accrual/tmns-utility.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.