FlowState consists of three layers: the C1 Pool smart contracts, the oracle integration layer and the aggregator routing interface. Together these deliver oracle-priced, single-sided liquidity that settles on-chain and integrates natively into existing DEX aggregator infrastructure. The protocol and its predecessor liquidity infrastructure have been in active development for three years by an in-house engineering team. Smart contracts are deployed, audited by Hashlock and tested in adversarial simulations. EVM is live on KyberSwap.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.

What the C1 Pool contract does
Each C1 Pool is a self-contained smart contract instance bound to a specific token. The contract handles four functions:- Deposits. Accepts single-sided token deposits from holders, tracks balances per depositor.
- Oracle resolution. Reads the current oracle price at trade execution time, not at deposit time. Depositors always receive the live market rate.
- Settlement. Receives buyer payment in the base currency, transfers tokens at oracle price, distributes the fee.
- Withdrawals. Returns deposited tokens to the holder if untraded, or returns settlement proceeds if traded.
How the fee distribution works
A separate distribution contract splits the 1% seller fee at settlement. No batching, no claiming, no end-of-period accounting:Aggregator
0.30% of every C1 Pool trade
STATE token stakers
0.30% distributed at settlement
BD
0.30% to partners bringing volume to C1 Pools
Treasury
0.10% funding protocol development and integrations
Oracle integration
C1 Pools reference external oracle price feeds rather than deriving price from internal pool state. This is the architectural decision that eliminates price impact.Supported oracle providers
Pyth Network
High-frequency price feeds with sub-second updates. 400+ feeds across crypto, equities and FX. Used where latency is critical.
Chainlink
Industry-standard oracle infrastructure with 1,000+ feeds across EVM chains. Established track record across GMX, Synthetix and other major oracle-dependent protocols.
Token coverage is bounded by oracle availability. A C1 Pool can be deployed for any token where Pyth or Chainlink provides a price feed. For tokens outside oracle coverage, no C1 Pool can be deployed and AMM routing remains the only option.
How aggregators discover and route to C1 Pools
C1 Pools expose a standardised interface that DEX aggregator smart order routers can query and execute against:
Pool registers
C1 Pool contracts register with FlowState’s liquidity registry on each supported chain.
Aggregator queries
DEX aggregators and other buy-side liquidity partners query the registry when scanning available liquidity for a given token pair.
Quote returned
The aggregator requests an execution quote from the C1 Pool, including the current oracle price and available depth.
Router selects
If the C1 quote is better than all AMM alternatives (which it mathematically will be for thin liquidity tokens), the aggregator routes the trade to the C1 Pool.
EVM and Solana implementations
FlowState is an EVM-only brand. The current EVM implementation supports Ethereum mainnet, Arbitrum, Base and BNB Chain. Solidity smart contracts. Compatible with the full EVM aggregator ecosystem. The same C1 Pool architecture is being deployed on Solana under a separate brand, Oasis, using a purpose-built Rust program optimised for Solana’s account model. Pyth is the primary oracle on Solana given its native architecture. Oasis runs on its own roadmap and cap table and is documented separately.Security model
- Audit: Full smart contract audit completed by Hashlock. Audit report available on the Audits & Security.
- Pen testing: Adversarial simulation testing including oracle manipulation scenarios.
- Development history: Three years of continuous in-house development across C1 Pool architecture and predecessor liquidity infrastructure.
- Upgrade mechanism: Time-locked upgrade pattern with multi-sig control pre-TGE. Changes to core settlement logic require multi-sig approval and a time-lock delay. Governance transitions to FLOW token holders post-TGE.
- Access control: Administrative functions are role-separated. No single key controls fee rates and price feeds simultaneously.

