Where FlowState can fit
Common inventory events include:- Treasury operations: planned diversification, runway funding or other measured treasury sales
- Investor and contributor unlocks: an optional liquidity path after tokens become transferable
- Founder, team and advisor inventory: concentrated allocations that may be large relative to market depth
- Market-maker inventory: programmatic deployment or unwind of token positions
- Strategic holder liquidity: large positions that do not need to cross the entire market immediately
Build the liquidity layer before the inventory event
The strongest implementation is usually proactive.1
Establish the per-token C1 Pool
Coordinate oracle support, the C1 Pool and the approved ERC-20 quote assets relevant to the target chain.
2
Connect distribution
Ensure the token’s C1 inventory can be reached by the relevant aggregators, routers, intent systems, RFQ paths or other execution partners.
3
Connect inventory sources
Make the C1 path available to the treasury, vesting recipients, funds, large holders, market makers and other eligible sources of sell-side inventory.
4
Let external demand consume inventory
Individual fills settle atomically while larger positions can complete progressively as buyer demand arrives.
The project does not need to be the seller
A project can coordinate the liquidity infrastructure without owning every position that uses it.Treasury
The project or foundation can make its own inventory available in planned amounts.
Vesting & distribution
Unlock recipients can be offered C1 as an optional post-unlock liquidity path.
Funds & holders
Professional holders can choose independently whether to make inventory available.
Market makers
Professional trading firms can integrate C1 into inventory and execution workflows.

