# 4. $KNTC Tokenomics

**The Role of $KNTC**\
$KNTC is the ERC-20 utility token enabling the "Computational Liquidity" of the network. It aligns the incentives of hardware providers, developers, and the DAO, serving as the medium of exchange and security collateral.

**Token Utility**\
**Primary Utilities:**

* **Compute Settlement:** Requestors (Enterprises/Devs) burn or transfer $KNTC to pay for processing power.
* **Node Staking:** High-tier nodes must stake $KNTC to process sensitive or high-value workloads, ensuring economic security.
* **Governance:** Holders vote on protocol parameters, treasury allocation, and roadmap prioritization.

**Secondary Utilities:**

* **Priority Access:** Stakers receive priority routing for high-yield tasks.
* **Ecosystem Discounts:** Developers holding $KNTC receive reduced fees on compute requests.

**Revenue Sharing Model**\
Kinetic creates a circular economy:

* **Node Rewards (70%):** The vast majority of fees paid by requestors go directly to the hardware providers.
* **Treasury (20%):** Reinvested into protocol development, marketing, and partnerships.
* **Staking Yield (10%):** Distributed to long-term $KNTC lockers for securing the network.

**Token Distribution**\
Total Supply: 1,000,000,000 $KNTC

* **Liquidity (80%):** Ensuring deep market depth on DEXs at launch.
* **Ecosystem & Mining Rewards (10%):** Reserved for node payouts over a multi-year emission schedule.
* **Team & Contributors (5%):** Vested over 24 months to ensure long-term alignment.
* **Investors & Strategic Partners (3%):** Capital for initial scaling and institutional onboarding.
* **Treasury Reserve (2%):** For grants, bug bounties, and emergency stabilization.


---

# 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://docs.kntctoken.xyz/4.-usdkntc-tokenomics.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.