A recent 1inch report put a surprisingly large number on one of DeFi's quiet problems: roughly $1.6 billion in liquidity was sitting outside active trading ranges. The report said that idle capital may represent about $150 million a year in missed fees. The exact estimate belongs to 1inch, so it needs to be read as an analysis rather than a universal market measurement.
The news matters because liquidity is the raw material of on-chain markets. A pool can advertise a large total value and still offer poor execution if that value is parked where current trades cannot use it. This is the difference between capital being present and capital being available.
What the 1inch report is measuring
The report focuses on concentrated liquidity and the way positions are distributed around current prices. In a traditional constant-product pool, liquidity is available across a wide price curve. Concentrated-liquidity systems let providers place capital inside a narrower range. That can make trading more efficient, but it also creates a maintenance problem.
When the market moves beyond a provider's chosen range, the position may stop earning fees from ordinary swaps. The assets have not disappeared. They are still on-chain and may still have value. They simply no longer sit where the market is currently matching buyers and sellers.
The $1.6 billion figure therefore should not be interpreted as stolen money or a protocol loss. It describes capital that is less useful for active market making under the conditions measured by the report. The annual $150 million estimate is also a modelled opportunity cost, not a guaranteed bill charged to users.
Why idle liquidity is expensive
Liquidity providers accept several risks in exchange for fees. They can suffer impermanent loss, price exposure, smart-contract risk, and the operational cost of moving or rebalancing positions. Concentrated liquidity adds another cost: someone has to watch the range and decide when the position should change.
That work is easy to underestimate. A provider can be profitable at one price and inactive a few hours later. Automated managers can rebalance positions, but they charge fees and introduce more contract logic. Manual management is cheaper in code and more expensive in attention.
For traders, the effect appears as wider price impact or more fragmented routes. Aggregators may find a better path across several pools, but routing cannot create depth that is not there. If much of the nominal liquidity is inactive, a large trade still moves the market more than the headline total value suggests.
What changes for DeFi users
The immediate lesson is simple: compare usable depth, not only total value locked. A pool with less total capital can produce better execution if more of its liquidity sits near the current price. Traders should inspect price impact, route splits, fees, and the age of liquidity positions before assuming a large pool is efficient.
For liquidity providers, the report is a reminder to measure net returns after rebalancing and exposure. A high fee number on a dashboard does not automatically mean a good strategy. The position may have earned fees while losing more through price movement, gas, management costs, or missed time outside its range.
Protocols also have a design choice. They can keep asking users to manage ranges themselves, or they can build better automation and clearer risk disclosures. Vaults and managed positions may reduce the burden, but they do not remove the underlying risk. They move the decision from each user to a strategy operator.
The larger on-chain finance angle
This problem extends beyond decentralised exchanges. Tokenised funds, stablecoin markets, and on-chain settlement all need liquidity that is available at the moment a transaction arrives. Capital that looks impressive in a dashboard but cannot quote a trade is not the same as market infrastructure.
That is why the report is useful even if its estimate changes. It points toward a quality question for Web3: how much capital is productive under real trading conditions? The answer needs time-series data, not a single snapshot, and it should separate user deposits, active ranges, volume, fees, and losses.
The next generation of liquidity tools will probably compete on that measurement. Providers want better returns. Traders want tighter execution. Protocols want deeper markets without paying for permanently idle capital. Those goals overlap, but only when the numbers describe usable liquidity instead of decorative liquidity.
For builders, the useful response is better reporting. Protocol dashboards should show active liquidity near the current price, fee generation per unit of capital, position age, and the cost of rebalancing. Those numbers would make it easier to compare a passive pool with a managed strategy without pretending that either one is risk-free.
For users deciding where to supply capital, the practical checklist is short. Check the fee history, inspect how often the position leaves its range, understand who controls any automation, and read the withdrawal and emergency rules. A position that needs constant attention is closer to a trading strategy than a savings product.
