Liquidation risk affects borrowers who post collateral for a loan. If collateral value drops too far, the position is liquidated and a penalty is taken. Impermanent loss affects liquidity providers who deposit assets into an AMM pool. They may earn fees, but price divergence can leave them worse off than holding the assets outright.
Why These Two Losses Behave Differently
Liquidation risk and impermanent loss both come from price movement, but they hit different participants and fail in different ways. Liquidation risk is a borrowing problem: the position must stay above a collateral threshold. Impermanent loss is a liquidity-provision problem: the pool rebalances your assets relative to the market, so the value you end up with can trail simple holding even if you earn trading fees.
The practical distinction is that liquidation is an acute event, while impermanent loss is often a path-dependent outcome. With liquidation, the protocol can forcibly close the position once the health factor or collateral ratio falls too far. With impermanent loss, there may be no single failure moment, only a widening gap between pool value and hold value as prices diverge.
When borrowers manage collateral, the key question is whether the position can survive volatility without crossing the liquidation line. When liquidity providers manage LP exposure, the key question is whether fees and incentives are likely to offset rebalancing drag, especially in pairs that can move sharply apart.
How Collateral Risk Differs From Pool Repricing
Liquidation risk depends on the loan structure. The borrower posts collateral, borrows against it, and must maintain enough margin for the lending protocol to consider the position safe. If the collateral falls in value or the borrowed asset rises enough, the protocol can liquidate part or all of the collateral and usually charges a penalty on top of the loss.
Impermanent loss depends on the AMM design. In a constant product pool, price changes cause the pool to sell the asset that rises and buy the asset that falls, keeping the pool balanced but changing your asset mix. That is why the loss is described as “impermanent” only until withdrawal, because the position’s relative underperformance becomes real when you exit the pool.
These mechanics also imply different monitoring habits. Borrowers watch collateral ratios, oracle movement, and liquidation thresholds. Liquidity providers watch volatility, correlation between the paired assets, fee generation, and the time horizon over which the position is likely to remain open.
For a deeper identity and access angle around the systems that support these positions, NHI Mgmt Group’s Ultimate Guide to NHIs is useful background on governance and lifecycle control, and the touchpoints between AI and non-human identities page shows how automated actors can intensify operational risk. For protocol controls, the NIST Cybersecurity Framework 2.0 is a sensible high-level reference for governance, protect, detect, respond, and recover thinking.
What Practitioners Should Watch Before Treating Either as “Just Yield”
In practice, the common mistake is comparing headline APY against headline risk. A high lending rate does not help if the collateral is near its liquidation threshold. A high farming reward does not help if impermanent loss is large enough to erase the fees earned.
Decision rule: If the position can be forcibly closed, treat liquidation risk as the primary control problem and size the leverage conservatively. If the position cannot be liquidated but can be rebalanced by an AMM, treat impermanent loss as the primary return problem and test whether the fee curve realistically compensates for expected divergence.
What to verify: Check the liquidation threshold, oracle reliability, incentive emissions, pool composition, and expected correlation of the paired assets. The best signal that a yield strategy is sound is not the stated APY, but whether the position still makes sense after stress-testing a realistic price move.
Practitioner takeaway: Liquidation risk is about losing the collateralized position itself, while impermanent loss is about underperforming a simple hold. The first is a balance-sheet survival issue, the second is a relative-return issue, and they should be underwritten with different assumptions.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10 address the attack and risk surface, while NIST CSF 2.0 and CIS Controls v8 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | GV.RM-01 — Risk Management Strategy | Risk framing helps compare liquidation exposure and LP return risk. |
| Recommendation — Assess liquidation thresholds and pool divergence as separate risk scenarios. | ||
| CIS Controls v8 | 14.1 — Security Awareness and Skills Training | Practitioners need decision discipline on leverage and yield assumptions. |
| Recommendation — Train users to distinguish forced-close risk from market-value underperformance. | ||
| OWASP Non-Human Identity Top 10 | NHI-04 — Secrets Rotation and Lifecycle | Automated yield systems often depend on long-lived credentials and operational governance. |
| Recommendation — Review credential lifecycle and revoke access paths that support automated farming. | ||
Related resources from NHI Mgmt Group
- What is the difference between data loss prevention and insider risk management?
- What is the difference between prompt injection risk and identity abuse in agents?
- What is the difference between secrets exposure and credential reuse risk?
- What is the difference between vendor risk management and identity governance?
