> ## 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.
# Vesting Platforms
> Make C1 the default unlock destination for vesting recipients
For vesting platforms (Series X, Sablier, Hedgey, Liquifi, Tally), FlowState is the natural exit destination at every unlock event. Instead of recipients dumping into AMMs at each cliff, vested tokens route directly into C1 Pools. Recipients exit at oracle minus 1%. The chart is unaffected. The project keeps its long-term holders. The vesting platform stops being identified as the cause of every post-unlock dump.
## The unlock dump problem
Every vesting platform faces the same downstream problem: tokens unlock, recipients sell, AMM pools cannot absorb the volume, charts collapse. The chain of events is predictable:
* Cliff or stream tick triggers token release
* Recipient receives tokens with the only obvious exit being the AMM
* Recipient dumps, slippage costs them 10-30% of the position
* Chart shows a red candle the community attributes to the vesting platform
* Project blames the platform, recipient blames the platform, holders blame the platform
* The platform did its job correctly. The market structure caused the loss.
Vesting platforms have solved the on-chain enforcement problem. They have not solved the post-unlock liquidity problem. C1 Pools close that gap.
## How C1 Pools fit the unlock flow
A C1 Pool is the right exit destination for any vested token because the exit mechanics match what vesting recipients actually want:
Recipients get the live market price minus the 1% fee. No slippage. No price impact. The chart does not move because the trade does not happen on the AMM.
The recipient holds the token they just unlocked. They deposit it directly. No need to acquire ETH or USDC pair to provide liquidity.
The recipient can deposit independently. The project does not need to approve or stage anything per recipient. The pool exists, the recipient uses it.
Buyers route through KyberSwap and other aggregators. The recipient does not need to find a buyer. Buyers find the pool through their existing trading workflow.
## Integration models
There are three integration patterns, increasing in depth:
Recipients exit their unlocked tokens by depositing into the relevant C1 Pool manually. The platform does not need to do anything technical. The platform just adds C1 to its documented exit options and links recipients to the pool.
Works for: any vesting platform. Time to enable: zero.
The vesting platform adds a "Deposit to C1 Pool" action in its recipient dashboard. After unlock, the recipient sees a one-click button that approves and deposits in a single transaction. The C1 Pool address per token is resolved from the FlowState registry.
Works for: any vesting platform with a frontend. Time to enable: one to two weeks.
The vesting contract itself is configured to route unlocked tokens directly into the C1 Pool at the unlock event. The recipient receives settlement proceeds (USDC or ETH) instead of the underlying token. The token never touches a wallet that might dump into the AMM.
Platforms integrate via the on-chain deposit call or the equivalent API operation. See [Integration Overview](/integration/integration-overview) for both surfaces.
Works for: vesting platforms with extensible release hooks. Time to enable: three to six weeks depending on contract architecture.
Series X is the reference implementation for this pattern.
## Why this matters for the platform
Vesting platforms operate in a category that gets attention for the wrong reasons. Every visible cliff dump becomes a community accusation. Platforms that route to C1 by default change the narrative: unlocks become invisible to the chart, the project's long-term holders are protected, and the platform's brand stops being attached to post-unlock drawdowns.
The commercial alignment is real too. A vesting platform that routes recipient deposits into C1 acts as the introducer for that flow. The standard reseller share applies: 30% of the 1% protocol fee, or 0.30% of settled volume, on every recipient unlock flowing through the integration. Recipients do not lose anything (the fee structure is unchanged) and the platform earns a recurring revenue line that scales with its existing token-under-management base.
## What an integrated unlock looks like
A typical \$500K unlock cliff using the contract-level routing pattern:
| Step | Old flow (AMM) | New flow (C1 routing) |
| ---------------- | ------------------------------------ | ------------------------------------------ |
| Cliff triggers | Tokens released to recipient wallet | Tokens released to C1 Pool deposit address |
| Recipient action | Sell on Uniswap | Receive settlement proceeds automatically |
| Price impact | 15-30% on \$500K thin-liquidity sell | Zero |
| Fee | 0.3% AMM + 15-30% slippage | 1% C1 fee, no slippage |
| Chart impact | Visible red candle | Invisible |
| Recipient net | Significantly less than oracle | Oracle minus 1% |
## Get started
For vesting platform partnerships, including contract-level integration support and revenue share terms, contact [partnerships@flowstate.exchange](mailto:partnerships@flowstate.exchange).
How the project itself coordinates vesting unlocks alongside team, treasury and MM supply channels.