Skip to main content
FlowState’s primary market is the sell side. Aggregators, routers and intent platforms are the distribution network that makes that sell-side inventory useful. C1 gives execution partners access to token inventory that has already been made available by projects, funds, market makers and other holders. Buyers continue to trade through their existing venue; the integration simply adds C1 as another possible source of output inventory.

Why integrate C1

New inventory source

Shared per-token C1 inventory can sit alongside AMMs, RFQ sources and proprietary liquidity in the execution graph.

No C1 bonding-curve impact

The C1 execution rate is oracle-derived rather than determined by the pool’s reserve balance.

Non-reverting quote view

quoteBuyFromPool(pool, asset, amount) reports unavailability instead of requiring an unavailable C1 route to fail the full quoting pass.

Permissionless simulation

Integrators can simulate the on-chain quote path with eth_call without privileges or state changes.

Routing integrations

C1 can sit in the routing graph alongside AMMs, RFQ venues, order books and other liquidity sources. The router should choose C1 only when the available inventory, current oracle-derived rate, gas and route constraints produce the appropriate executable outcome for the requested trade. FlowState does not require C1 to win every route. The important structural difference is that a large C1 fill does not move along a C1 reserve curve.

Intent-based execution

For intent systems, C1 can supply the token the swapper is buying. A solver, filler or resolver can source that output inventory from the C1 Pool during settlement rather than needing to warehouse the same inventory in advance. C1 does not replace the intent layer. The intent system continues to own its user experience, auction or solver logic. FlowState supplies another inventory source underneath it.

Settlement Patterns

See how C1 fits into router, intent and direct settlement flows.

Quote behaviour and fallback

A C1 quote does not reserve inventory or guarantee later execution. Available inventory, oracle state and anchor-band conditions can change between quote and settlement. Integrators should simulate as close to execution as their architecture allows and treat an unavailable or failed C1 route as a normal routing outcome. Where execution certainty matters, retain an appropriate fallback.

Multiple quote assets, one inventory pool

One C1 Pool exists per inventory token and can support multiple approved quote assets. The quote asset is selected per trade. This means FlowState does not require separate seller inventory to be maintained for every quote pair. Multiple routes can reach the same underlying token inventory.

Current integrations

“Integrated” describes integration status rather than current public liquidity. Deployment remains pre-launch and staging pools contain test-scale inventory. See Deployments.

Commercial participation

FlowState allocates part of the seller-side protocol fee to distribution and commercial participation. Partner economics can reflect routing, execution, integration, inventory origination or other agreed contributions. Commercial terms are agreed per integration rather than fixed publicly for every partner.

Get started

See Integration Overview for the technical entry points or contact partnerships@flowstate.exchange for integration support.