> For the complete documentation index, see [llms.txt](https://cryptic-documentation.gitbook.io/cryptic-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cryptic-documentation.gitbook.io/cryptic-documentation/tokenomics-and-business-model/4.-tokenomics-overview/4.3-tokenomics-model.md).

# 4.3 Tokenomics Model

#### **Fixed Supply**

* **Total Supply:** 100,000,000 CT
* **Starting Price:** $0.01197218
* **Starting Market Cap:** $1,197,218
* Fixed supply with no inflationary emissions currently planned
* Circulating supply may be reduced over time through treasury-managed buyback and burn operations, subject to governance, treasury policy, market conditions, and available platform revenue

#### **Streamflow dashboard**

{% embed url="<https://app.streamflow.finance/token-dashboard/solana/mainnet/A1y4iVpLaLutTYaG13UANr8VK5F8z8oTVtNuGMjSBjL4>" %}

#### **Distribution**

Designed for long-term sustainability across launch distribution, team alignment, ecosystem growth, staking, marketing, community incentives, and liquidity support.

| Allocation Category                               |     Tokens | % of Supply | Vesting / Unlock                               |
| ------------------------------------------------- | ---------: | ----------: | ---------------------------------------------- |
| **Airdrop**                                       | 16,108,618 |  16.108618% | 24-hour vest, unlocking every hour             |
| **Team**                                          | 10,000,000 |         10% | 18-month vest, unlocking monthly               |
| **Ecosystem**                                     | 25,000,000 |         25% | 24-month vest, unlocking every 2 weeks         |
| **Community Incentive Program / Airdrop Appeals** |  9,005,056 |   9.005056% | 1-month vest, unlocking weekly; held in Squads |
| **Staking**                                       | 10,000,000 |         10% | Reserved for staking incentives                |
| **Marketing**                                     | 20,000,000 |         20% | 24-month vest, unlocking every 2 weeks         |
| **Liquidity Addition**                            |  5,000,000 |          5% | 2-week unlock                                  |
| **Liquidity Pool Addition**                       |  4,886,326 |   4.886326% | Dedicated to liquidity pool support            |

#### **Airdrop Allocation**

The airdrop allocation is designed to support launch distribution and community participation.

* **Base Airdrop:** 15,358,618 *CRYPTIC*
* **Additional Airdrop Allocation:** 750,000 *CRYPTIC*
* **Total Airdrop Allocation:** 16,108,618 *CRYPTIC*
* **Unlock Structure:** 24-hour vest, unlocking every hour

#### Claim Tokens&#x20;

{% embed url="<https://app.streamflow.finance/claim>" %}

#### **Community Incentive Program / Airdrop Appeals**

The Community Incentive Program / Airdrop Appeals allocation is designed to support post-launch community alignment, appeal resolution, participation incentives, and approved ecosystem programs.

* **Allocation:** 9,005,056 *CRYPTIC*
* **Unlock Structure:** 1-month vest, unlocking weekly
* **Custody:** To be held in Squads

#### **Liquidity**

Cryptic’s token model includes dedicated liquidity support for launch and post-launch market operations.

* **Liquidity Addition:** 5,000,000 *CRYPTIC*
* **Liquidity Pool Addition:** 4,886,326 *CRYPTIC*
* **Total Liquidity Support:** 9,886,326 *CRYPTIC*

Liquidity allocations are intended to support market access, trading availability, and healthier launch conditions.

#### **Fee Structure**

Platform revenue may be generated through multiple product surfaces, including:

* transaction and payment-related fees
* swap-related fees through integrated routing and DeFi activity
* card-related revenue through supported crypto card flows
* fiat on-ramp revenue through integrated providers
* premium mobile and desktop features
* vault storage revenue through encrypted file storage and permanent storage workflows
* SDK access and usage tiers
* enterprise self-hosted deployments and seat-based licensing
* custom integrations and white-label infrastructure opportunities
* partner-driven ecosystem services and integrations

#### **Buyback & Burn Operations**

Where platform revenue, treasury policy, and market conditions allow, Cryptic may allocate a portion of ecosystem revenue toward buyback and burn operations.

These operations are intended to support long-term ecosystem alignment and responsible treasury management. Buyback and burn activity is subject to available revenue, governance or treasury approvals, operational requirements, and market conditions.

#### **Economic Backbone**

*CRYPTIC* is designed to connect:

* platform access
* product usage
* ecosystem incentives
* developer and partner participation
* staking incentives
* treasury resources
* liquidity support
* buyback and burn operations where applicable
* long-term product development
* community alignment

into one ecosystem model.

> *The Cryptic token model is designed to support product-led adoption across Mobile, Desktop, and SDK infrastructure, with treasury tools that can reinforce long-term ecosystem alignment where appropriate.*


---

# 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://cryptic-documentation.gitbook.io/cryptic-documentation/tokenomics-and-business-model/4.-tokenomics-overview/4.3-tokenomics-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.
