> 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/value-accrual-model.md).

# Value Accrual Model

For `TMNS` to matter beyond initial distribution, the network must have a clear logic for value accrual. In other words, it must be clear why network growth can create sustained relevance for the token over time.

## Payment Growth as the Core Driver

The first and most important driver of token value is growth in real payment activity. As Terminus expands its user base, partner network, merchant reach, and transaction density, the network itself becomes more valuable as an economic coordination system.

`TMNS` is positioned to benefit from that growth not because it is required for each payment, but because it is embedded in the mechanisms that help the network expand.

## Utility-Based Demand

Demand for `TMNS` can emerge through multiple utility channels:

* ecosystem participation,
* partner incentive alignment,
* staking and credibility requirements,
* fee discounts or access rights,
* governance participation,
* and eligibility for network programs.

This is important because strong token demand in infrastructure networks often comes from layered utility rather than a single forced use case.

## Staking as Economic Commitment

Where appropriate, staking can create a stronger relationship between token holders and network health. Participants that want deeper access, preferred status, or stronger governance involvement may commit `TMNS` as a signal of economic alignment.

This creates a path from speculative holding toward functional participation.

## Token Demand From Expansion

As new markets, partners, and programs are added, demand for `TMNS` can grow with the number of actors seeking to benefit from network participation. This is especially relevant if access to certain incentive programs, fee structures, or governance privileges becomes tied to token-based alignment.

## Avoiding Pure Speculation

The whitepaper should be explicit about one point: `TMNS` is not meant to derive value only from market attention. Its long-term relevance depends on utility that remains connected to network behavior.

This is why Terminus is prioritizing:

* real payment usage,
* partner growth,
* staking-based commitment,
* treasury-backed ecosystem deployment,
* and community participation tied to actual adoption.

## Value Accrual as a Network Function

Ultimately, the value accrual model of `TMNS` is strongest when the following loop becomes true:

network growth increases utility, utility increases participation, participation increases demand, and demand reinforces the network's ability to expand.

That is the kind of reflexive yet grounded system Terminus should aim to build.


---

# 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/value-accrual-model.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.