# Tokenomics

The $ACN token functions as the economic layer of AITECH Cloud Network, enabling value exchange, access to services, and ecosystem participation across both the Compute Marketplace and Agent Forge. It is designed to support usage-driven demand, align incentives, and introduce predictable economic flows within the network.

***

#### **9.1 Token Utility Across Ecosystem**

$ACN is embedded across core platform interactions, serving as the primary mechanism for accessing services and participating in ecosystem activities.

* Access to compute resources within the Compute Marketplace
* Execution of workflows within Agent Forge
* Deployment and monetization of agent-based services
* Participation in governance and staking mechanisms

| Utility                 | Application                              |
| ----------------------- | ---------------------------------------- |
| Compute Access          | Payment for GPU and infrastructure usage |
| Workflow Execution      | Payment for agent operations             |
| Deployment              | Publishing workflows and agents          |
| Governance              | Voting on protocol-level decisions       |
| Ecosystem Participation | Staking and access-related mechanisms    |

***

#### **9.2 Payment Mechanism**

$ACN operates as the primary medium of exchange across the ecosystem, enabling consistent and programmable transactions.

* Used for usage-based payments across both products
* Supports subscription-based access models
* Integrated with on-chain settlement systems
* Compatible with automated payment enforcement mechanisms

| Payment Type          | Description                                     |
| --------------------- | ----------------------------------------------- |
| Usage-Based Payments  | Pay per compute usage or workflow execution     |
| Subscription Payments | Fixed access plans for platform services        |
| On-Chain Transactions | Transparent and verifiable payments             |
| Programmable Payments | Automated transactions via integrated protocols |

***

#### **9.3 Staking Design**

Staking mechanisms are implemented to support ecosystem participation, access models, and supply management.

* Access-based staking to unlock platform capabilities
* Deployment-based staking for APIs and workflows
* Long-term ecosystem support through supply locking

| Staking Function        | Purpose                                     |
| ----------------------- | ------------------------------------------- |
| Access Enablement       | Unlock platform features and usage tiers    |
| Deployment Rights       | Enable external API and workflow deployment |
| Supply Locking          | Reduce circulating token supply             |
| Ecosystem Participation | Align incentives with long-term usage       |

***

#### **9.4 Governance**

$ACN enables participation in decentralized governance, allowing token holders to contribute to the evolution of the ecosystem.

* Voting on ecosystem upgrades and changes
* Adjustments to system parameters and mechanisms
* Participation in ecosystem proposals and initiatives

| Governance Area           | Scope                                       |
| ------------------------- | ------------------------------------------- |
| Protocol Upgrades         | Changes to system architecture or features  |
| Parameter Adjustments     | Updates to economic or operational settings |
| Ecosystem Proposals       | New initiatives and integrations            |
| Stakeholder Participation | Token-holder voting and input               |

Governance is designed to balance stakeholder participation with operational efficiency, ensuring that decisions reflect real usage patterns while maintaining system stability.

***

#### **9.5 Deflationary Mechanism — Revenue-Backed Burn**

$ACN incorporates a deflationary supply model directly linked to platform activity and revenue generation.

* A percentage of platform revenue is allocated to token buybacks
* Tokens are repurchased from the open market
* Repurchased tokens are sent to a burn address and permanently removed from circulation

| Stage              | Process                                                     |
| ------------------ | ----------------------------------------------------------- |
| Revenue Generation | Compute usage and agent execution generate platform revenue |
| Buyback Allocation | Portion of revenue allocated for token repurchase           |
| Market Repurchase  | Tokens acquired from open market                            |
| Burn Mechanism     | Tokens sent to burn address, reducing supply                |

**Flow Overview**

```
Platform Usage → Revenue → Buyback → Burn Address → Reduced Circulating Supply
```

This mechanism ensures that supply reduction is directly tied to measurable economic activity. As usage of the Compute Marketplace and Agent Forge increases, the rate of token removal from circulation scales accordingly, aligning long-term supply dynamics with real infrastructure demand.

***

#### **9.6 Supply Dynamics**

The overall supply behavior of $ACN is driven by the interaction between usage, staking, and deflationary mechanisms.

| Factor              | Impact                                      |
| ------------------- | ------------------------------------------- |
| Platform Usage      | Increases token demand                      |
| Staking Mechanisms  | Reduces circulating supply                  |
| Revenue-Backed Burn | Permanently removes tokens from circulation |
| Ecosystem Growth    | Expands utility and demand base             |

***

#### **9.7 Summary**

The $ACN token is designed to:

* Act as the primary medium of exchange across the ecosystem
* Enable governance participation and protocol evolution
* Support staking mechanisms tied to access and deployment
* Introduce a revenue-linked deflationary model
* Align token demand and supply with real platform usage

This structure ensures that the economic layer of AITECH Cloud Network remains directly connected to infrastructure consumption and workflow execution, supporting long-term sustainability and ecosystem growth.


---

# Agent Instructions: 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:

```
GET https://whitepaper.aitech.io/acn/publish-your-docs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.