Start by separating protocol growth into market-level components rather than treating TVL as a single resilience signal. Review collateral type, oracle dependence, and liquidation settings for each market, then check whether borrowing activity is scaling or whether only deposits are inflating headline numbers.
Break the headline growth into separate market signals
The first move is to stop using total value locked as a single health score. In lending, rapid growth can come from real borrowing demand, but it can also come from deposit concentration, incentive chasing, or a market that is accumulating idle collateral without true credit activity. Teams need to isolate each market before they decide whether growth is healthy or just noisy.
That means looking at the asset mix, the quality of collateral, and whether the protocol’s growth is broad-based or concentrated in one market. A protocol can look strong overall while one collateral market becomes the main source of exposure, especially if pricing, volatility, or user behavior is not uniform across the book.
Teams should also distinguish scaling demand from balance-sheet inflation. If borrowing, utilization, and repayment flow are not rising alongside deposits, the protocol may be gathering liquidity faster than it is putting that liquidity to work. That is a different operating condition from a lending book that is expanding because more users are actively borrowing against sound collateral.
Check the control points that make fast growth risky
The next review should focus on the mechanics that turn growth into fragility: oracle dependence, liquidation thresholds, and how much buffer exists if prices move quickly. These are the controls that determine whether the protocol can absorb stress, or whether growth has simply increased the size and speed of a future unwind.
Collateral type matters because not all assets behave the same under stress. More volatile assets can create sharper liquidation cascades, while concentrated exposure to a single collateral class can make the protocol sensitive to the same market move across many positions. Oracle design matters because a stale or manipulated price feed can distort both borrowing capacity and liquidation execution at the exact moment the protocol needs reliable signals.
Liquidation settings are the final check. If liquidation thresholds, close factors, or incentives are too permissive, rapid growth can leave the system with too little room to clear risky positions cleanly. If they are too strict, the protocol may trigger unnecessary liquidations and deepen market stress during normal volatility. The right answer is market-specific, not one-size-fits-all.
Separate demand quality from balance-sheet size before you expand
Once the market-level view is clear, teams should ask whether the growth is producing durable lending activity or only a larger headline number. Durable growth shows up in active borrowing, stable repayment behavior, and a collateral base that still looks sound after you remove the most promotional or incentive-driven deposits.
This is where protocol operators often overread success. A fast-growing market can look liquid and safe because deposits are abundant, but if the borrowed side is shallow, the protocol may not actually be earning diversified usage. In that case, the first management question is not how to add more capital, but whether the existing capital is being intermediated safely and consistently.
If a protocol is growing faster than the broader market, the operational response should be to slow the assumption that “growth equals resilience.” Expansion only becomes useful when the team can show that the new volume is diversified, priced correctly, and able to survive stress without relying on perfect market conditions.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST CSF 2.0 and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | ID.AM-01 — Physical devices and systems inventory | Market-level decomposition depends on knowing which markets and assets make up the protocol's exposure. |
| GV.RM-01 — Risk management strategy | The answer is about separating growth from resilience signals to make a better risk decision. | |
| Recommendation — Inventory each market and asset class separately before judging protocol growth. Define how growth, utilization, collateral quality, and liquidation stress are weighed in risk reviews. | ||
| NIST SP 800-53 Rev 5 | RA-3 — Risk Assessment | The question calls for assessing collateral, oracle, and liquidation risk before acting on headline growth. |
| AU-6 — Audit Record Review, Analysis, and Reporting | Teams need to examine activity patterns, not just aggregate balances, to see whether growth is real usage. | |
| SC-8 — Transmission Confidentiality and Integrity | Oracle dependence is a control-point issue because price integrity affects lending and liquidation decisions. | |
| Recommendation — Assess each lending market's specific risk drivers before treating TVL as a health indicator. Review utilization and borrowing activity trends, not just total deposits. Validate price-feed integrity where oracle inputs drive collateral valuation and liquidation. | ||
Practitioner Guidance
What to prioritise: Review each market separately before you make any portfolio-level judgment. The most useful first pass is a market-by-market readout of collateral mix, oracle reliance, liquidation parameters, and whether borrow-side activity is keeping pace with deposits.
What to verify: Confirm that growth is supported by genuine utilization, not just liquidity inflow. A protocol that is absorbing deposits faster than it is originating loans needs closer scrutiny than one with broadly distributed, actively used markets.
Decision rule: If the fastest-growing market also has the weakest collateral quality or the highest oracle sensitivity, treat it as the first place to tighten monitoring and risk limits, even if the aggregate protocol still looks healthy.
Practitioner takeaway: The right first step is to decompose growth into market-level risk signals, because total size tells you very little unless you know what kind of activity created it.
Related resources from NHI Mgmt Group
- Should identity teams prioritise faster connector delivery or broader policy design first?
- How should security teams prioritise NHI remediation in cloud environments?
- How should security teams govern non-human identities at scale?
- How should security teams govern non-human identities for compliance?