Lending Protocols - FlowState

For lending protocols, C1 Pools provide a liquidation venue that does not suffer slippage tax on large positions. Liquidations execute at oracle price, atomically composable with existing liquidation flows. Pool depth is sourced from four supply channels (holders, vesting platforms, market makers, OTC desks), giving liquidation reliability that scales with the broader market, not just dedicated LP incentives.

The liquidation problem

Lending protocols (Aave, Morpho, Compound, Spark) rely on liquidators to close underwater positions. The mechanism only works if the collateral can be sold at or near the oracle-implied price. For thin liquidity collateral, this breaks down:

Collateral cannot be sold at quoted value. A $500K liquidation on a $2M AMM pool yields significantly less than the oracle says it should.
Bad debt accumulates. The shortfall between oracle price and AMM execution becomes protocol bad debt.
Risk parameters tighten artificially. To prevent bad debt, lending protocols set conservative LTVs, collateral caps and liquidation thresholds. This reduces capital efficiency for borrowers.
Long-tail collateral is excluded entirely. Many otherwise viable assets cannot be listed because no liquidation venue can absorb realistic position sizes.

How C1 Pools fit liquidation infrastructure

C1 Pools settle at oracle price with zero slippage. This is exactly the property a liquidation engine needs: deterministic execution at the price the lending protocol’s oracle already references.

Predictable execution at oracle price

Liquidation logic that assumes oracle-priced exit is now correct. The shortfall between oracle and execution price collapses to the 1% fee.

Reduced bad debt risk

Large liquidations on thin-liquidity collateral can clear without forcing the AMM curve. Bad debt scenarios that depend on slippage cascades become structurally less likely.

Atomic composability

C1 Pool settlement happens in the same transaction as the liquidation call. Liquidators can bundle borrowing, collateral seizure, C1 sale and debt repayment into a single atomic flow.

More viable collateral types

Long-tail assets that cannot currently be listed as collateral (because no liquidation venue exists) can be supported when C1 Pool depth covers expected liquidation sizes.

Where C1 Pool depth comes from

For a lending protocol relying on C1 as a liquidation venue, the question that matters most is “will there be depth at the moment of liquidation”. Unlike AMM pools, which depend on a single class of LP, C1 Pools draw supply from four distinct sources. This diversifies depth and makes it less correlated with any single LP behaviour:

Holders

Long-tail collateral holders deposit into C1 Pools when they want clean exits. This is structural baseline depth that grows with token holder count.

Vesting platforms

Vested allocations of collateral tokens (team, VC, ecosystem grants) feed C1 at each unlock cliff. Predictable additions to depth on a published schedule.

Market makers

MMs can deploy inventory in C1 as a structured exit venue, particularly for tokens where they want exposure but cannot hedge two-sided.

OTC desks

Block-sized depositors (treasuries, large holders, OTC counterparties) can stage inventory in C1 ahead of expected demand.

For collateral types with predictable liquidation pressure, the project itself often has interest in maintaining depth. Treasury operations, vesting recipients and designated MMs all benefit from a deep liquidation venue because a reliable venue is a precondition for the asset being listed as collateral in the first place.

Where this matters most

The economic case strengthens with collateral thinness. For ETH and BTC collateral, AMM liquidation works fine. The marginal benefit of C1 routing is small. For mid-cap and long-tail collateral, the picture is different:

Collateral type	AMM liquidation slippage at scale	C1 Pool execution
Stablecoins and majors	0-2%	Equivalent or better
Mid-cap (under $50M MC)	5-15%	1% fee, no slippage
Long-tail (under $20M MC)	15-50%+	1% fee, no slippage
RWA tokens	Often unsupported	Possible if oracle exists

The lending protocol’s loss from AMM slippage is often the primary reason long-tail collateral cannot be listed at competitive LTVs. C1 Pools change the underlying math.

How a lending protocol integrates C1 routing

There are two integration paths, depending on the protocol’s liquidation architecture:

Direct liquidator integration

Liquidator bots route their collateral disposal through DEX aggregators that already include C1 Pools (KyberSwap is live). The aggregator’s existing routing logic selects C1 when execution is better. No protocol-level change required.

Protocol-level liquidation hook

For protocols with custom liquidation engines (or those wanting to make C1 the primary route for specific collateral), the liquidation contract calls the C1 Pool directly using the standard pool interface. Settlement is atomic. See Integration Overview for interface capabilities and SDK status.

Most lending protocols can benefit from C1 availability through the aggregator path without any code changes. Direct integration is for protocols that want to bake oracle-price liquidation into the core risk model.

Risk considerations specific to lending

A few items lending protocols should evaluate before relying on C1 routing for high-stakes liquidations: Oracle alignment. The oracle FlowState uses for the C1 Pool should match (or be highly correlated with) the oracle the lending protocol uses for collateral pricing. Both sides currently use Pyth or Chainlink. Misalignment between the two oracles can create gap risk. Pool depth at liquidation moment. A C1 Pool only helps if depositors are present at the moment of liquidation. The four-source supply model reduces single-LP risk, but for black swan events, AMM fallback is still required. Lending protocols should monitor C1 depth as part of collateral risk parameters and adjust LTVs accordingly. Circuit breakers and rate limits. C1 Pools include circuit breakers that pause execution during rapid oracle moves. In a market crash, this is the correct behaviour for the pool but may delay liquidation availability. AMM fallback handles the gap. Collateral-specific supply coordination. For new collateral listings, lending protocols can coordinate with the token project to pre-stage depth via vesting platforms and treasury OTC deposits before activating the listing. These are not blockers. They are the expected risk model for any oracle-priced liquidation venue, well-understood from how perpetual DEX protocols (GMX, Hyperliquid, Drift) use oracle pricing.

Get started

For lending protocol partnerships, including risk model collaboration, dedicated liquidation pools and supply-side coordination on new collateral listings, contact partnerships@flowstate.exchange.

Documentation Index

​The liquidation problem

​How C1 Pools fit liquidation infrastructure