Cookie Chat — Tokenomics

$CHAT — the access token for the AI terminal on Cookie Chain

v1.0 · August 2026 · Living document · Companion to the whitepaper

1. Summary

$CHAT is the access token for Cookie Chat, the AI terminal for Cookie Chain. It exists for one purpose: to open the tiers above the free product — a product that is already live at https://cookiechat.net, already listed in the official ecosystem apps registry, and already answering questions every day.

The essentials:

• Total supply: 1,000,000,000 $CHAT, fixed. Mint and freeze authority were revoked at creation — both read null on-chain today — so the supply can never increase and no balance can ever be frozen. Check it yourself against the mint address in §9.
• Native to Cookie Chain, minted directly on the chain rather than issued through a launchpad.
• No sale. No presale, no private round, no venture allocation, no insider price. The market opens on a CHAT/COOK pool and everyone meets it at once.
• Liquidity is permanent — the pool's LP is locked, as is every position added to it later. Nothing that goes in comes back out.
• Team, treasury and future liquidity vest on-chain in Cookie Vault, an ecosystem escrow app, on schedules that end twelve months after launch.
• Half the supply belongs to the people using it — 25% community, 25% ecosystem.
• Utility is access. Holding $CHAT opens Cookie Pro and Cookie Max. Holding — not spending it, not staking it, not handing it to anyone.

Cookie Chat did not build a token and then go looking for a product. The terminal shipped first, in public, with a published whitepaper and a published roadmap. The token extends it.

2. Why a token, and why this shape

The terminal is free and stays free. Anyone can ask anything, read live cards, inspect a wallet and check the sources behind an answer without holding a single token, without an account, without a card and without connecting anything. That is not a promotion; it is the architecture. Most questions are answered without a language model ever running, which is where the cost of an assistant usually concentrates.

What is not free is the layer underneath: data providers, hosting, and the depth the roadmap promises. Those costs grow with use. A paid tier is the ordinary answer, and $CHAT is how it is paid — by holding, not by billing. The difference matters to this product specifically: Cookie Chat asks for no payment details, no sign-up and no personal data today, and a card subscription would have introduced all three.

Why not a launchpad. A bonding-curve launchpad exists in the ecosystem — MomoSwap — and on paper it was the easy route: no code, a curve, an audience built in. It was rejected for one reason. A bonding curve puts the entire supply on the curve, and a curve cannot express a community programme, an ecosystem budget, or a treasury that is escrowed and answerable. We preferred pools that can be named, published, escrowed on-chain and pointed at afterwards.

What that costs us, stated plainly. There is no raise. Nobody buys in early, which also means nothing is funded up front. The product's running costs — data providers, hosting, the infrastructure the free tier sits on — are paid from the ecosystem pool, with the treasury held as the reserve behind it, and both are converted on the open market as they are spent. That is disclosed here rather than discovered later.

Why the allocations are conventional. Six pools with published sizes: the three the project holds for itself escrowed on-chain on a published schedule, the two meant to be handed out left liquid so that they can be, the sixth locked into the market as liquidity, and the address behind all of them disclosed. That is a claim anyone can check on the day and every day after. A structure that is verifiable is worth more than a structure that merely sounds pure.

3. Supply & allocation

Two numbers are worth reading together. Community and ecosystem are half the supply — the largest claim on $CHAT by a wide margin belongs to the people who use the terminal and to the apps around it. Team and treasury together are 20%, both escrowed, and neither can move faster than the schedule published in §4.

Initial liquidity (10%). Seeded in full at launch into the CHAT/COOK pool on CookieBox, the ecosystem's liquidity hub — pool AyAwJKceLGgGNNm1BA21tzUJfGfWxb4J1Td4hnQiCpaB — paired against COOK provided by the project. Deepening it later is what the future liquidity pool is for. $CHAT trades on CookieSwap, the chain's native DEX, and is indexed by the same official market data as every other traded token — including by this terminal, which reports $CHAT from exactly the sources it reports everything else from, with no special case. Every LP position — this one, and any added later — is locked permanently: liquidity cannot be withdrawn, by us or by anyone.

Future liquidity (20%). Escrowed for market depth — deepening the CHAT/COOK pool as volume justifies it, and seeding liquidity on venues Cookie Chat reaches later. It releases from day one, without a cliff, because that is when the job starts: a pool is thinnest on the day it opens, and a reserve that cannot be deployed until month three is not a liquidity reserve for the months that matter most. It is not a trading reserve, and the schedule in §4 is what makes that checkable rather than assertable.

Team (10%). One allocation, escrowed behind a three-month cliff — the only cliff of the three, since the other two exist to be spent from day one. It covers the people building the product, and it is the pool every reader should check first.

Treasury (10%). The reserve, and deliberately not earmarked for a programme: it is held against what a young product cannot foresee — a provider repricing, an opportunity that will not wait, a bad quarter. It exists so that the pools with a job to do are not raided when something goes wrong.

Community (25%) and ecosystem (25%). Described in §5. Both stay liquid at launch, because escrowing them would freeze the very programmes they exist to fund.

4. Locks & vesting

Three pools — team, treasury and future liquidity — are held in Cookie Vault (lock.cookoven.xyz, listed in the Cookie Chain ecosystem registry under its earlier name, Cookie Lock), the chain's token-lock and vesting app. They are the three the project holds for its own use, which is exactly why they are the three that should not rest on our word. Tokens sit in on-chain escrow; the recipient can claim only the amount that has actually vested; and a lock cannot be cancelled once it is created. Nothing about the schedule depends on our good behaviour.

Each escrow is a Cookie Vault lock you can open and read: the amount held, what has vested, what has been claimed, and the schedule it runs on. Ask the terminal for the $CHAT allocation and it reports the same figures, read live from the chain rather than from this table.

Why twelve months and not four years. Cookie Chain is a young chain with a small market. A large pool cannot be realised into that market at any speed without destroying the price it is being realised into — so a multi-year lock would be protecting against something that is not physically available, while blocking the things that are: seeding a pool, paying a partner, funding an integration. We would rather publish a short schedule we will actually keep than a long one that quietly gets renegotiated.

Why only the team has a cliff. The other two pools have work to do immediately. The treasury stands behind costs that start on day one, not in month three; and market depth is scarcest the day the pool opens, so future liquidity that could not be deployed until month three would be a liquidity reserve missing precisely the months where liquidity is thinnest. Both release linearly instead, which keeps them usable without letting either arrive all at once — roughly 16,700,000 $CHAT a month from future liquidity, and half that from the treasury. The team is the one allocation with nothing urgent to fund, so it is the one that waits.

What is not escrowed, and why. Community and ecosystem are liquid on purpose. Both exist to be distributed, on programmes described in §5; putting them behind a claim schedule would mean announcing an airdrop we could not pay. Their sizes are published, the address holding them is published, and every movement out of it is visible on-chain. Initial liquidity is neither escrowed nor liquid — it is in the pool, behind a permanent LP lock, which is a firmer commitment than any vesting schedule: it never unlocks at all.

What the locks cost. Cookie Vault charges a native fee of 16,000 COOK per lock and a 0.6% token fee on the amount deposited — across the three, that is 48,000 COOK and 2,414,487 $CHAT.

The token fee comes out of the deposit, so each escrow was funded with more than its stated size in order to hold exactly that size: the three escrows contain 100,000,000, 200,000,000 and 100,000,000, as §3 states. What pays for it is the ecosystem pool, which is the working pool and the one that carries the project's costs — leaving it at 247,585,512 in practice against the 250,000,000 in the table above, a shortfall of just under one per cent of that pool. The table keeps the round figure because that is the allocation; this paragraph is where the difference is accounted for, and a supply table that quietly ignored its own fees would be a supply table that does not add up.

Addresses. Everything the project still holds sits at one address — E5BGueDZ33Xn8SfdcQmkcGKxj14yFpSzX2KS4ndhqjmz — and each of the three schedules has its own Cookie Vault escrow, visible separately. It is worth being precise about what that does and does not show. The pool and the escrows are exact: what is in them is in them. The split between community and ecosystem at the project address is an accounting one until tokens actually leave it — those two pools are one balance on-chain, and only their spending tells them apart. Every movement out is visible either way, and the terminal returns these addresses when asked.

5. Where the tokens go

Community — 250,000,000 (25%)

First wave, August 2026: 100 seats of 100,000 $CHAT. Ten million tokens — 1% of supply — to the wallets posted in the replies to the airdrop announcement on @askCookieChat. Qualifying closed with that post: 203 wallets, more than there are seats, so claiming is first come, first served, one seat per wallet and one per X account.

It is claimed at cookiechat.net/airdrop and nowhere else. A claim is a signature proving the wallet is yours — never a transaction, never an approval, never a seed phrase — and the tokens are transferred the moment it is made. 100,000 $CHAT is exactly the Cookie Pro threshold (§6), so a seat opens Pro for as long as it is held.

After that: further waves and seasons. The remainder is airdropped and paid out as rewards for continued use of the terminal. The reason for holding some back is simple: a single airdrop rewards being early and nothing else, and Cookie Chat's whole argument is about the questions you ask next month too.

Recipients, qualifying criteria and timing for each wave are announced separately through the official channels in §9, and are deliberately not fixed here — a rule published in advance is a rule to be farmed. Nothing in this section is a promise of an amount to any individual.

Ecosystem — 250,000,000 (25%)

This is the working pool: it keeps the terminal running, and it pays for the relationship with the ecosystem around it going both ways.

• Running the terminal — data providers, hosting and the infrastructure the free tier depends on. These are the costs that grow with use, and this is where they are paid from.
• Grants and integrations with Cookie Chain apps — the explorer, the swap, the launchpad, the name service, the staking app and whatever comes next.
• The platform work the roadmap commits to: a public API and an embeddable widget, so other ecosystem apps can answer questions with Cookie Chat's engine instead of building their own.
• Marketing and growth — reaching the people who have not heard of either the terminal or the chain.

6. Utility — access

$CHAT's utility is access. Holding it opens tiers inside Cookie Chat. It is not spent, not staked, and never leaves your wallet.

The tiers themselves are published at https://cookiechat.net/plans, and each capability above stands as an item on the roadmap.

How verification works. Cookie Chat already connects to wallets, and reading a balance takes no signature. Tier status is an on-chain reading of your balance when you connect — no staking contract, no lock-up, no transfer of custody, no transaction to sign. Your tokens never move. The reading is taken again on each request that spends from a tier, so a balance that changes is reflected without reconnecting.

On thresholds. Tiers are denominated in tokens rather than in dollars, so access does not flicker with the price. Thresholds may be adjusted over time to keep them proportionate; any change will be announced before it takes effect.

The free tier is not a trial. Every topic, every live card and every computed figure stays available without holding anything, and no feature is removed once the tiers exist. What the daily allowance rations is narrower than that: how many answers a day are written by a model. Past twenty, Oven 2 keeps answering from the same facts and renders the same cards, composing the prose itself instead; Oven 1 has no limit at all. That is a consequence of an architecture where the figures never came from a model in the first place — not a concession.

7. Value mechanics

Three forces are intended to connect $CHAT to the product's growth.

1. Access demand. Premium capability requires holding. As the layer above the free terminal deepens — alerts, actions through Cookie MCP, the API, the widget — the reason to hold deepens with it.

2. Fixed supply. One billion, mint authority revoked, no emission schedule and no inflation. Every token that will ever exist exists at launch, and the schedule by which the escrowed pools become available is published in §4 rather than discovered.

3. Buyback and burn. As product revenue arrives, it may fund open-market buybacks of $CHAT with the purchased tokens burned. Cookie Chain has a precedent for the buying half: the Cookie Jar uses a share of creator-fee revenue to buy $COOK on the open market — though it holds what it buys in the community treasury rather than burning it. This is a stated intention, not a schedule: no amount, no timing and no minimum is promised, and it depends on revenue that does not exist yet.

8. Rollout

Utility ships in phases, in line with the product roadmap. Like the roadmap, these describe sequence and intent — not dates.

Governance is deliberately not specified here. It stands as a roadmap item, and how a vote is weighted and what it can decide will be described when there is a holder base to ask — not promised in advance to a page.

9. Verifying the real token

Every launch attracts impersonators. There is exactly one legitimate $CHAT contract, and two authoritative places to find it:

1. Inside Cookie Chat itself — ask the terminal for the contract address and it returns the verified one.
2. On cookiechat.net — published on this page and on the site.

Contract address: 2wPK38gv8dWU89K5zDAAULAihnU1sRocbpzwPP6twY7Q

That mint is an SPL token with 6 decimals, a total supply of exactly 1,000,000,000, and both its mint and freeze authority set to null. Its metadata — the name, the symbol and the image — is immutable, so not even we can change what this token calls itself. Every one of those facts is readable from the chain without trusting this document.

Announcements come only from Cookie Chat's official channels: the site cookiechat.net and @askCookieChat on X. Never trust a contract address from a direct message, a reply or a comment. If an address does not match what Cookie Chat itself reports, it is not $CHAT.

10. Risks

Anyone considering $CHAT should weigh the following honestly.

• Price volatility. Token prices move sharply and unpredictably. $CHAT may lose value, including all of it.
• Thin market. Cookie Chain is a young chain and market depth is limited. Large orders may face significant slippage, and the price may move on comparatively small volume.
• Sale pressure from the project's own pools. The product's running costs are funded by converting $CHAT on the open market. The treasury behind them does so on the published twelve-month schedule; the ecosystem pool is liquid and has no schedule. This is disclosed by design and is real.
• Single-chain risk. $CHAT lives on Cookie Chain. Anything that affects the chain — its validators, its bridges, its liquidity — affects the token.
• Execution risk. Tiers, actions, the API and governance are planned. They may change, be delayed, or not ship as described.
• Regulatory risk. Digital-asset regulation is evolving and varies by jurisdiction. Future changes could affect the token, its utility or its availability.
• Technical risk. Smart contracts, escrow programs, DEX infrastructure and blockchains carry inherent risk, including bugs and exploits. That includes the escrow holding the vested pools.
• Dependency risk. Cookie Chat reads external data providers. Their pricing, availability and terms can change.
• Impersonation risk. Fraudulent tokens and phishing are common. Verify the contract address as described in §9.

11. Legal

This document is for informational purposes only.

$CHAT is a utility token providing access to features within the Cookie Chat application. It is not a security, an investment product, a share, or a claim on revenue, profits or assets. Holding it confers no ownership interest in Cookie Chat and no entitlement to dividends or distributions.

Nothing in this document is financial, investment, legal or tax advice, and nothing here is a recommendation to buy, sell or hold any asset. No promise or guarantee of future value, price, return or profit is made or implied.

This document contains forward-looking statements. Planned features — including token-gated tiers, actions, the API, governance, and buyback and burn — describe intent and direction, not commitments. Scope, timing and design may change, and some features may not ship at all.

This document is not an offer or solicitation to sell any token or security, and is not directed at any person in any jurisdiction where such an offer, solicitation or distribution would be unlawful. Determining whether participation is lawful in your jurisdiction is your responsibility. Consult qualified legal and financial professionals before acting.

Cookie Chat is an official Cookie Chain ecosystem app. It does not speak for Cookie Chain, and nothing here is issued by, endorsed by or binding on the chain or its team.

Digital assets carry significant risk. Never commit more than you can afford to lose entirely.