Skip to main content
C1 Pools are designed to be the lowest-risk venue an integration team can add. Adding C1 to a quoting pass cannot fail the pass. The quoter is a plain view that never reverts. An unavailable pool, a failed oracle read or a paused market all return an unavailable quote instead of an error, and anyone can simulate it with eth_call, with no privileges, no allowances and no state. Integration risk on the quote path is structurally zero. The integration is engineering days, not a project. One event to index for discovery, one entry point to execute against and deterministic pair resolution: one pool per token and quote asset pair. The execution argument is thin books at size. AMM price impact grows with trade size while the C1 price does not, so the advantage is largest exactly where AMM depth is weakest. No exclusivity and no relationship dependency. C1 sits in the routing graph and wins when it wins on price. Nothing about the integration depends on a commercial arrangement.

​
For smart order routers

A C1 pool is a venue that does not degrade with trade size. It sits in the routing graph alongside AMMs and RFQ sources, and the router’s own price comparison logic selects it when it delivers the best net execution, which on thin books is most of the time at size. There is nothing to operate. Inventory comes from token holders, pricing comes from the oracle, and the pool either quotes or reports itself unavailable.

​
For intent platforms: solvers, fillers and resolvers

The value is sourceable inventory at a deterministic price on tokens where none exists. That is exactly the segment a solver declines today, because it cannot hold or hedge the inventory. With a C1 pool the filler buys the output at the oracle rate during settlement and delivers it, with no inventory to warehouse and no hedge to find. The direction constraint, in plain language: C1 supplies the token the swapper is buying. It does not absorb a token the swapper is selling.

Settlement Patterns

Where the call sits in an intent fill, the funding callback and the constraints a filler must model.

​
Current integrations

“Integrated” describes the integration, not live depth. Deployment status and what to expect on-chain today are on Deployments.

​
Economics

Partner fee share is agreed per integration. Contact partnerships@flowstate.exchange.

​
Common questions

Every pool carries a reference rate and an anchor band tolerance. A fill whose oracle rate falls outside the band is rejected rather than executed, in the quote path and the execution path alike. See Audits & Security for the security model.
Depth scales with depositor coverage per token, and pools are effectively unstocked ahead of launch. Partners that integrate early get pool growth as part of their routing improvement curve.

​
Get started

Integration documentation is available on request. Contact the integration team at partnerships@flowstate.exchange.

Technical detail

Contract interface, settlement patterns, oracle mechanics and deployment status.