Skip to main content

Documentation Index

Fetch the complete documentation index at: https://whitepaper.flowstate.exchange/llms.txt

Use this file to discover all available pages before exploring further.

For token-issuing projects, FlowState is the supply orchestration layer for your token. Every channel that puts your tokens into the market (team unlocks, VC vesting, treasury sales, designated market makers) can route through C1 Pools instead of dumping into the AMM. The chart stays clean. The seller gets oracle price minus 1%. The buyer pays no slippage.

The problem most projects face

Every token project hits the same wall around year two:
  • Team and VC unlocks begin. Holders want to realise gains. The AMM pool cannot absorb the volume without dropping the price 30-50%.
  • Treasury holdings need diversification. The project holds native tokens that cannot be sold to fund operations without signalling weakness.
  • Liquidity mining costs rise. Keeping AMM pools deep enough to look healthy on chart sites costs ongoing token rewards, draining treasury.
  • Designated market makers refuse to quote. For tokens below $50M market cap, professional MMs decline inventory risk that cannot be hedged.
  • Short-term holders dump on every catalyst. Even small sells move the price meaningfully, hurting long-term confidence.
The structural cause is the same in every case: AMM pools cannot absorb large sells without the curve punishing the seller, the chart and every other holder.

Your token’s supply channels, mapped to C1

C1 Pools accept supply from four distinct sources. For a token-issuing project, each of these maps to a part of your cap table or treasury operations:

Holders

Your team, advisors, seed investors, KOL allocations, retail holders and any other long-term position. Anyone who holds the token can deposit into the C1 Pool when they want to exit, in any size, without coordinating with the project.

Vesting platforms

Token vesting contracts (Series X, Sablier, Hedgey, Liquifi and similar) can route unlocked tokens directly into C1 Pools at each vesting cliff or stream tick. Recipients exit at oracle price without ever touching the AMM. Integration with Series X is native.

Market makers

Designated MMs that historically refused to quote thin-liquidity tokens can deploy inventory into C1 with a defined exit price (oracle). This converts MM engagements from speculative inventory risk into structured execution.

OTC desks

Project treasury operations and large block trades can route through C1 instead of bilateral OTC. The treasury gets oracle pricing, the buyer gets aggregator-routed execution, the chart is unaffected.
The project itself does not need to be the depositor in every case. What matters is that each of these supply channels has the option to route through C1 instead of through the AMM, and that the project actively guides them to do so.

How a project activates each channel

1

Holders

Once a C1 Pool exists for your token and aggregator routing is live, holders can deposit independently. The project’s role is communication: tell holders the pool exists, tell them how to use it, and tell them why it matters for the chart.
2

Vesting platforms

Coordinate with your vesting provider to enable a “route to C1 Pool” option at unlock. Series X is built around this flow. For other providers, the recipient deposits manually post-unlock. The project can pre-stage this with each VC and team member ahead of their cliff.
3

Market makers

If you have a designated MM relationship, give them the C1 Pool address as a structured inventory deployment venue. The MM deposits available inventory into C1 and exits at oracle minus 1% as buyers route through aggregators. See Market Makers for the full MM economics. Your MM contract terms can include C1 routing as a baseline expectation.
4

OTC desks

Treasury diversification and large grants can use the C1 Pool as the settlement venue instead of arranging bilateral OTC. The pool absorbs the block at oracle price. The buyer receives tokens through the aggregator route as if it were a normal trade.

What this looks like for chart health

A typical thin-liquidity token with a $5M AMM pool and a $500K position holder has three exit paths:
Exit methodSlippage to sellerAMM price impactChart visibility
Single AMM dump20%+-20%Visible red candle
TWAP over weeks5-10%-5-10%Sustained downtrend
C1 Pool1% fee, 0% slippageNoneInvisible to chart
The third option is what FlowState makes possible. Sellers get clean exits, the chart stays healthy and long-term holders are not punished for the seller’s liquidity event.

Where this matters most

The economic case strengthens with position size and token thinness:

VC and team unlock cliffs

The single highest-impact use case. A $1M-$10M cliff routed through C1 instead of the AMM is the difference between a sustained downtrend and an invisible exit.

Treasury operations

Project treasuries can convert measured tranches at oracle price without creating visible sell pressure. Useful for funding operations, runway extension or DAO grants.

Post-launch holder retention

When large holders have a clean exit path, short-term holders panic less on catalysts. The chart stops being a coordination signal for selling.

Lower LP rewards spend

Healthy chart action depends less on artificially deep AMM pools when large sellers route through C1 instead. Liquidity mining budgets can be reduced or redirected.

When to start

The right time to set up a C1 Pool is before the first major unlock. Once the pool exists and aggregator routing is live, holders have a clean exit option. Without it, the only exit is the AMM, with the predictable consequences. For projects approaching team or VC unlock cliffs, lead time to set up a pool and coordinate the holder communication is two to four weeks.

Get started

For project liquidity partnerships, including pool deployment coordination, vesting platform integration and large-treasury operations, contact partnerships@flowstate.exchange.

See also: For Foundations

Ecosystem-level liquidity infrastructure for chains and grant programmes.