Under-Collateralization

Under-collateralization in DeFi lending describes the state where a borrower’s outstanding debt exceeds the current market value of the collateral backing it — the loan is worth more than the security pledged against it — which in an overcollateralized lending protocol signals insolvency, triggers automatic liquidation mechanisms, and if uncorrected, produces bad debt that the protocol must absorb. The term is the direct opposite of overcollateralization, which is the baseline assumption of all DeFi lending: that collateral is always worth more than the loan it secures. Under-collateralization means this fundamental safety margin has been breached, either gradually (as collateral prices fall) or suddenly (flash crash, oracle manipulation). In traditional finance, an under-collateralized borrower can be pursued legally; in DeFi, the code enforces the rules — and if liquidation fails, the loss is systemic.

The Overcollateralization Baseline

DeFi lending protocols never allow borrowing up to 100% of collateral value. They use a layered buffer system:

“`

Collateral Value (100%)

│

├── Max Borrow (Loan-to-Value ratio) ← e.g., 75% — never lend above this

│

├── Liquidation Threshold ← e.g., 80% — begin liquidation here

│

└── Collateral Value at Bad Debt ← below 100% — under-collateralized

“`

Example (Aave ETH parameters):

ETH LTV: 80% → can borrow $800 against $1,000 ETH
Liquidation threshold: 82.5% → liquidation triggers when debt > 82.5% of collateral
Under-collateralization: debt > 100% of collateral = bad debt

The 17.5% buffer between max LTV (80%) and 100% collateral coverage is the safety margin against under-collateralization. Liquidations are supposed to fire before this buffer is exhausted.

How Under-Collateralization Occurs

Gradual Price Decline (Normal Liquidation Path)

“`

Day 1: ETH = $3,000 | Borrow $2,000 USDC | LTV = 66.7% ✓ Safe

Day 3: ETH = $2,600 | Debt = $2,000 | LTV = 76.9% — approaching threshold

Day 4: ETH = $2,420 | Debt = $2,000 | LTV = 82.6% → Liquidation triggers

Liquidator closes position before under-collateralization

“`

In this scenario, under-collateralization never fully occurs because liquidation fires first.

Sudden Price Drop (Under-Collateralization Scenario)

“`

Day 1: ETH = $3,000 | Borrow $2,000 | LTV = 66.7% ✓ Safe

Day 4: ETH crashes from $2,500 → $1,200 in one block (Binance large sell, oracle update)

Old: LTV = 80% (safe)

New: LTV = $2,000/$1,200 = 166.7% → immediately under-collateralized

Liquidators can’t profitably close: seizing $1,200 collateral < $2,000 debt

→ Bad debt of $800 created

“`

Asset-Specific Scenarios That Create Under-Collateralization

Flash crash of illiquid collateral: A governance token with $5M liquidity is listed as collateral. A whale sells $2M worth → price drops 60% in minutes → all borrowers against that token become under-collateralized.

Oracle manipulation attack: Attacker inflates collateral price via manipulation, borrows the maximum, then crashes the price → position is instantly under-collateralized by the manipulated amount.

Liquidation cascade amplification: Mass liquidations of one asset push its price down, causing more liquidations, in a loop. The final positions in the cascade may be under-collateralized by the time liquidators reach them.

Interest accrual on locked positions: In extreme cases (very illiquid or abandoned positions), accruing interest can slowly push a position below collateralization even without price movement.

Distinguishing Under-Collateralization from Near-Liquidation

State	LTV	Description	Protocol Action
Safe	< LTV limit (e.g., 75%)	Healthy buffer; no risk	None
Warning zone	75–82.5%	Between LTV and liquidation threshold	User should add collateral or repay
Liquidatable	> Liquidation threshold (82.5%)	Liquidation can fire	Liquidators can repay up to 50%
Under-collateralized	> 100% (debt > collateral)	True insolvency	Liquidation fails; bad debt created