Most DeFi users pay attention to borrow APY, supply APY, collateral factors, and liquidation thresholds because those settings are visible in the interface and immediately affect what a position can do. Borrow caps and supply caps receive much less attention because they sit one layer deeper in the risk framework. Even so, they often determine how far a market can expand before it becomes difficult to unwind, difficult to liquidate, or too concentrated for the protocol to handle safely.
Caps are key reserve parameters: supply and borrow caps limit the total amount of a token that can be supplied to and borrowed from a reserve. Caps are used to maintain liquidity and prevent overexposure during volatile market conditions.
The important point is that the two caps solve different problems. A supply cap controls how much raw exposure the protocol is willing to accept on the deposit side. A borrow cap controls how much of that asset the protocol is willing to let users take out on the debt side. Treating them as interchangeable misses the risk design entirely.
A supply cap limits the total amount of a given asset that can be deposited into a lending market. Once that ceiling is reached, new supply of that asset is blocked until room opens up again.
From the user’s perspective, this can look strange because deposits are usually thought of as helpful. More supply sounds like more liquidity, more fees, and more market activity. The protocol’s perspective is different. Supply is not only liquidity. It is also exposure to the asset itself. If a protocol allows too much of a volatile or thinly traded asset to accumulate as collateral, it can create a large liquidation burden later. A very large collateral base in a fragile asset can become difficult to sell during stress, especially if liquidators cannot exit the seized collateral cleanly.
That is why supply caps exist. They prevent the protocol from quietly becoming overexposed to an asset simply because deposit demand was strong. In practice, this is especially relevant for long-tail assets, bridged assets, or tokens whose onchain and offchain liquidity can deteriorate quickly when markets turn.
A borrow cap limits the total amount of a given asset that can be borrowed from the reserve. Once that limit is reached, additional borrowing of that asset stops even if there is still idle supply available.
This can feel counterintuitive at first because users often assume borrowed amount should be naturally constrained by available deposits and by interest rates. Borrow caps exist because those natural constraints are not always enough. A protocol may not want borrowers to build an outsized short position against one asset, or to drain so much of the reserve that liquidations and withdrawals become fragile during a volatile move.
Borrow caps are the first-line risk control for exactly this reason. Caps were introduced to control market size relative to liquidity and risk, particularly in volatile environments and for assets with more fragile exit conditions. A borrow cap therefore acts less like a convenience setting and more like a brake on how large the protocol is willing to let one debt market become.
A supply cap is mainly about collateral-side concentration and liquidation burden. A borrow cap is mainly about debt-side concentration and reserve depletion.
If the supply cap is too loose, the protocol can end up with an enormous quantity of a risky asset sitting inside the system as collateral. That creates trouble later if prices collapse and the market has to liquidate more of that asset than real liquidity can absorb. If the borrow cap is too loose, the protocol can allow too much demand for a particular asset to build on the debt side, which can make that reserve scarce, make withdrawals more fragile, or create one-sided market structure around the borrowed token.
This is why both caps can be active on the same reserve without being redundant. One is controlling how much of the asset the system is willing to hold. The other is controlling how much of it the system is willing to lend out.
Users often notice supply caps only when they try to deposit and find the market full. They notice borrow caps only when they try to borrow and discover that the reserve is open for deposits but closed for new debt. By that point the cap looks like a friction. In reality it is a sign that the risk framework has already decided the market is large enough.
This is why caps often feel arbitrary to users while looking essential to risk teams. The individual trader sees a blocked action. The protocol sees a limit that prevented more exposure from accumulating in a market whose downside would be difficult to manage.
For instance, Aave’s recent governance traffic shows how active these controls remain in practice. Cap changes are still being proposed and adjusted in 2026 based on usage, liquidity, and position health, as seen in current risk steward cap-change proposals. That alone is a good reminder that these are live controls, not static launch settings.
One common misunderstanding is that a supply cap automatically protects suppliers from withdrawal stress. It does not. A supply cap only limits total deposits. It does not guarantee that the borrowed portion of that reserve is small enough, nor does it guarantee that market conditions will remain liquid under stress.
A reserve can sit below its supply cap and still feel tight if utilization is high, if borrowers have consumed most of the available liquidity, or if liquidators would struggle to recycle seized collateral. This is why supply caps have to be read together with utilization, borrow caps, collateral quality, and the broader market liquidity around the asset.
Borrow caps can also be misread. A low borrow cap does not necessarily mean the protocol thinks the asset is bad. It often means the protocol thinks the asset’s debt market should remain small relative to available liquidity, liquidation capacity, or its role inside the system.
For stablecoins, borrow caps may matter because reserve scarcity can quickly affect withdrawals and peg-sensitive strategies. For more volatile assets, caps may matter because leveraged short or carry trades can grow too quickly and create disorderly unwind risk later. In both cases, the point is not that borrowing is unsafe in principle. The point is that scaling the borrow market too far can create fragility the protocol would rather avoid.
Modern lending protocols rarely rely on a single parameter. Caps usually sit alongside collateral settings, reserve factors, liquidation thresholds, and sometimes isolated-market or isolated-pool frameworks. Venus, for example, separates some risk into isolated pools and backs those pools with dedicated shortfall handling and risk-fund structures in its risk fund and shortfall documentation. That broader architecture exists because caps can reduce exposure growth, but they cannot by themselves eliminate insolvency or liquidation stress.
This is the most useful way to think about them. Caps are preventive controls, not complete insurance.
A supply cap tells the user how much of an asset the protocol is willing to warehouse. A borrow cap tells the user how much debt exposure the protocol is willing to tolerate in that asset. When either cap is close to full, that is not merely an operational inconvenience. It is a piece of information about how tight the protocol already thinks the market has become.
The closer a reserve is to its cap, the more likely it is that new demand will run into protocol-imposed friction rather than simple market pricing. That matters for lenders because capped markets can become sticky. It matters for borrowers because future strategy changes may be blocked. It matters for liquidators because the size and composition of the market are already being actively constrained.
Borrow caps and supply caps are easy to ignore because they do not feel as immediate as rate or liquidation settings, but they often determine how large a market can become before the protocol starts saying no. Supply caps limit how much raw exposure the system is willing to accept on the deposit side, particularly for collateral that could become difficult to liquidate in size. Borrow caps limit how much debt exposure the system is willing to let build on the borrowing side, particularly where reserve scarcity or concentrated positioning could create stress later. Users usually notice these settings only when they block a transaction. By then, the important fact is not that the cap exists. The important fact is that the protocol already believes the market is large enough to justify the barrier.
The post Borrow Caps vs Supply Caps: The Lending Controls Most Users Ignore appeared first on Crypto Adventure.
