> 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-token-thesis.md). # TMNS Token Thesis The `TMNS` token exists to accelerate network formation. This distinction is foundational. Terminus does not need to force users to pay with a native token in order to justify a token model. Doing so would likely weaken the product. The payment experience should remain centered on the assets users already hold and trust for spending. `TMNS` serves a different role: it aligns the incentives of the participants who help grow the network. ## The Core Idea `TMNS` is not designed to sit in front of product adoption. It is designed to compound product adoption after the payment loop is already working. That makes the token thesis stronger. Instead of manufacturing demand through forced utility, Terminus can tie `TMNS` to something more durable: real payment growth, ecosystem expansion, and governance evolution. ## Why a Payment Network Benefits From a Token Payment systems involve multiple stakeholders with different motivations: * users who want utility, * merchants who want continuity, * partners who bring distribution or execution capacity, * and infrastructure participants who help scale settlement and market coverage. A token can coordinate these groups more effectively than a purely closed corporate model when the goal is to grow a network rather than just sell a product. In crypto terms, this means the network can reward the behavior that makes it stronger rather than limiting all upside to a single cap table. ## TMNS as an Ecosystem Incentive Token `TMNS` is designed first as an ecosystem incentive token. Its primary purpose is to reward behavior that makes the network stronger: * real payment activity, * useful partner participation, * meaningful merchant expansion, * and ecosystem contributions that increase network density. This positioning is consistent with how Web3 networks create growth loops. Tokens are strongest when they amplify genuine adoption, not when they create artificial usage requirements. For Terminus, that distinction is critical. The project is not building a token in search of a use case. It is building a token around a payment network that already has a clear adoption loop: * more supported spending, * more useful merchant coverage, * more payment activity, * more ecosystem relevance, * and more reasons for partners and community participants to align around the network. ## Product First, Token Second A payment network becomes fragile when token logic dominates product logic. Terminus should take the opposite approach. The product must be valuable even before the token is fully active. Then the token can accelerate: * distribution, * retention, * partner participation, * community alignment, * and long-term governance. This sequence matters because it keeps the network grounded in real economic behavior. It also makes the story easier for the market to understand. Terminus is not asking the community to believe in a token before there is a payment thesis. It is asking the community to join a payment network that can become stronger with token coordination. ## Aligning Growth With Ownership One of the most compelling aspects of a tokenized network is that the participants helping expand it can also share in the upside of that expansion. If users, partners, contributors, and ecosystem builders help increase the relevance and throughput of Terminus, `TMNS` provides a mechanism for aligning those contributions with the long-term success of the network. That is especially important in a regional payment strategy. A network that grows across markets, partners, and merchant environments needs a way to turn contribution into alignment instead of relying only on one-way commercial contracts. ## Why Usage Mining Fits the Thesis Because Terminus is a payment network, the most natural primitive for token distribution is not passive ownership alone. It is useful activity. This is why `usage mining` belongs in the token thesis: * it rewards real payment behavior, * it encourages repeat usage instead of one-time speculation, * it can attract users into the network through measurable utility, * and it gives `TMNS` a direct role in bootstrapping transaction density. When paired with anti-abuse controls, usage mining helps connect token issuance to real economic behavior rather than synthetic attention. ## Why TMNS Matters In short, `TMNS` matters because it transforms Terminus from a payment product into a growth-coordinated ecosystem. It turns: * usage into incentives, * incentives into retention, * retention into network density, * and network density into stronger ecosystem gravity. That is the token thesis. `TMNS` is the asset that helps convert payment adoption into network expansion. --- # 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-token-thesis.md?ask=&goal= ``` `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.