> 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/governance-and-execution/use-of-proceeds.md).

# Use of Proceeds

The purpose of the `TMNS` token raise is to accelerate network growth. Terminus is operating in a market window where execution speed matters. The use of proceeds strategy therefore emphasizes product expansion, ecosystem activation, and regional scaling rather than a defensive capital posture.

## Market Expansion

A significant share of capital should be directed toward entering and deepening Southeast Asian markets. This includes local business development, partnership formation, merchant network growth, and market-specific operational deployment.

Payment networks benefit from local density. Capital deployed into expansion is valuable when it creates concentration in the right markets rather than generic geographic sprawl.

## Product and Infrastructure Development

Terminus must continue investing in the systems that make the product reliable and scalable:

* payment orchestration,
* channel integrations,
* settlement workflows,
* risk monitoring,
* and user-facing product quality.

This is particularly important because the whitepaper positions Terminus as infrastructure, not just interface.

## Ecosystem Incentives

Part of the proceeds should support ecosystem growth programs, including:

* user acquisition campaigns,
* partner activation,
* merchant-side expansion incentives,
* and `TMNS`-linked usage mining programs.

This aligns directly with the token thesis that network growth should be actively incentivized.

## Liquidity Support

Healthy markets matter for token credibility and ecosystem participation. A dedicated portion of proceeds should therefore support liquidity formation, market-making readiness, and basic market quality conditions around `TMNS`.

This should be done responsibly, with long-term sustainability in mind rather than short-term appearance management.

## Business Development and Strategic Partnerships

A payment network expands through relationships. Proceeds should therefore also support strategic partner development, exchange relationships, integration efforts, and ecosystem growth initiatives that can accelerate user demand or merchant access.

## Community Growth

Because Terminus is pursuing a crypto-native narrative, community is not a cosmetic layer. It is part of distribution. Capital should be allocated to community activation, education, content, ecosystem engagement, and contributor pathways that increase organic reach and network resilience.

## Compliance and Operational Reserves

Even in a growth-oriented model, a disciplined reserve for compliance, legal support, and operational flexibility remains necessary. Payment networks operate across sensitive and regulated environments. Responsible execution requires resources for resilience as well as growth.

The use of proceeds framework should therefore reflect ambition without sacrificing durability.


---

# 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/governance-and-execution/use-of-proceeds.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.