DeFi Saver case study: The role of Automation during mass liquidation events

DeFi Saver users widely use Automated leverage management (a combination of Auto Repay and Auto Boost) to optimize their loan positions.

Under normal market conditions, these tools handle routine rebalancing, such as automatically adjusting debt levels to keep constant leverage or smoothly scaling a position's safety ratio from, for example, 180% to 200%.

However, during a major market selloff between January 25 and February 9, DeFi Saver's system executed a total of 382 automated repay actions on Aave V3 alone.

Out of these, 95.55% were critical interventions executed on heavily exposed positions running a Safety ratio of <150% - all of which would have faced certain liquidation during the event given the size of the market correction.

So today, in this study, we'll be looking at the 365 at-risk positions managed by DFS Automation between January 25 and February 9. To be more precise, these are Aave V3 positions managed via DeFi Saver, across Ethereum Mainnet, Base, Optimism, and Arbitrum.

During this period, automation performed with a 100% success rate, completely insulating users from an estimated $8.38 million in third-party liquidation penalties.

Now, let's go over the specifics.

Crisis Mode vs. Routine Leverage Management

Under varied market conditions, Automated Leverage Management had two different popular use cases:

• Routine Adjustments: Users continuously utilize Auto Repay and Auto Boost to maintain tight target ratios or buffer their positions safely above risk thresholds.
• Emergency Intervention: When sudden market drops pull safety ratios below a critical threshold (<150% Safety ratio), the automated Repay functions execute instantly to deleverage the position, defending it before external liquidators can step in.

Out of all the automated events that fired during this volatile timeframe, the system was almost exclusively operating in emergency defense mode:

Breakdown of Triggered Repay Events During the Event

• Protocol: Aave V3
• Total Automated Repay Events Triggered: 382
• Emergency Protection Triggers (<150% Safety ratio): 365 events (95.55% of triggers)
• Routine Adjustments Fired (>150 Safety ratio): 17 events (4.45% of triggers)

The economics of automated protection

Standard liquidations on lending protocols like Aave are inherently highly punitive and harmful for the user’s position. A third-party liquidator can seize a rigid, massive portion of the position to pay down the debt (the default close factor is 50%), charging a steep liquidation penalty (often around 5%) on that entire block.

Compounding the loss, forced external liquidations during crashes frequently swap a user's collateral at highly distressed, unfavorable market rates - effectively forcing the user to sell low at the worst possible time.

By contrast, DeFi Saver’s Automated Leverage Management operates with extreme capital efficiency. When a price drop occurs, the DFS Automation programmatically calculates the exact amount of collateral needed to be used for the position to reach the user’s configured target.

A modest 0.3% automation fee is applied only to the specific amount swapped, avoiding both the flat 50% position liquidation factor and the 5% liquidation penalty, while minimizing swap slippage thanks to multiple integrated DEX aggregators and preventing forced over-liquidations.

Case In Point: Capital Efficiency Under Stress

To see how these different mechanics impact a user's balance, consider this active position with $7,159,595.62 in debt that got caught in the ETH crash on January 29, 2026 (mainnet block 24,342,478) - a real, on-chain example, not a hypothetical (transaction):

• Standard third-party liquidation: An external liquidator is typically permitted to close 50% of the position's debt. They would forcibly close $3,579,797.81 of the debt and claim a 5% liquidation fee on that entire chunk, costing the user $178,989.89 in penalized collateral. The user would also lose significant capital from their collateral being panic-swapped at an unfavorable rate.
• DeFi Saver Automation: Instead of liquidating a rigid 50% chunk, the automated Repay trigger calculated the minimum amount required to reach the user's pre-set target ratio - restoring the position's Health Factor from roughly 1.30 back up to a safe ~1.5. It swapped just 697.49 WETH (about $1,965,378.61, or 27.5% of the debt) and used it to repay $1,905,742.69 of the loan. The 0.3% fee was applied only to that swap, costing the user just $5,896.14 - a saving of $173,093.75 (97% less) compared to what a standard liquidation would have cost.

Automation track record: Flawless execution under pressure

For the 365 instances where positions entered the danger zone, DeFi Saver's automation executed flawlessly.

By instantly unwinding a precise portion of collateral to pay down debt, the system restored health factors before external liquidators could extract fees. Across the four networks, DeFi Saver successfully defended over $446 million in at-risk collateral supporting $335 million in debt.

Note: "Unrealized Liquidation Fee" represents what users would have paid to external liquidators without DeFi Saver's liquidation protection.

Key Insights & Conclusion

• A Multi-Purpose Infrastructure: While users rely on Automated Leverage Management for day-to-day constant leverage and routine rebalancing, this data proves the system smoothly and flawlessly switches to a frontline emergency shield when extreme volatility hits.
• 100% Reliability When it Matters Most: For all 365 accounts that dipped below a 150% safety ratio during the event, the automation successfully preempted the market, resulting in zero liquidations for protected positions.
• Calculated vs. Predatory Execution: Automation prevents the drastic capital loss associated with rigid 50% protocol close factors and poor market execution rates. By executing fractional swaps rather than broad liquidations, users avoid being forced to sell low.
• Unmatched Capital Preservation on Mainnet: The vast majority of the defended capital was concentrated on Ethereum Mainnet, where automation successfully insulated $437.89M in collateral, saving users a staggering $8.24M in potential third-party penalties on that single network.

That would be all for today. For any questions you might have regarding this case study or have trouble setting up DFS automation, please be sure to contact our support guys via DFS Discord.

Until the next post, stay safe out there!

Stay connected:

🌍: DeFiSaver.com

💬: Official Discord

📢: Official Twitter/X