Use DeFi Saver for Liquidation Protection: Step-by-Step
Imagine you've deposited ETH as collateral on MakerDAO or Aave to borrow DAI or USDC. The market turns against you; ETH drops 20% in hours. Without active monitoring, your position could be liquidated, losing a chunk of your collateral to the liquidation penalty (typically 5–13% of the debt). Most lending protocols offer no built-in safety net—you either watch 24/7 or risk it.
DeFi Saver fills that gap. It’s an automation dashboard that lets you create stop-loss and rebalancing rules for your lending positions across MakerDAO, Compound, Aave, and more. Instead of manually scrambling to add collateral or repay debt, you predefine conditions—like a health factor threshold—and the platform executes the transaction automatically. This guide will walk you through exactly how to set up liquidation protection using DeFi Saver, from connecting your wallet to configuring advanced multi-step strategies.
By the end, you’ll understand the mechanics of health factors, how DeFi Saver’s automation engine works, and the concrete steps to protect your capital from forced liquidations. No fluff, just actionable steps for an intermediate DeFi user.
- DeFi Saver automates liquidation protection by executing stop‑loss or rebalancing actions when your health factor reaches a preset threshold.
- Configure a stop‑loss to repay a percentage of debt (or swap collateral to repay) when HF drops to, say, 1.15, giving you a buffer before protocol liquidation at 1.0.
- Rebalancing automation keeps your health factor within a target range by dynamically adjusting debt levels as collateral prices change.
- Combine both stop‑loss and rebalance for layered protection: rebalance handles normal volatility, stop‑loss acts as a safety net for extreme moves.
- Test your automation with small amounts first, monitor gas costs, and be aware that flash crashes or network congestion can still cause missed executions.
- DeFi Saver does not replace the need for understanding health factors; always set thresholds with your risk tolerance in mind.
What Is DeFi Saver and Why Use It for Liquidation Protection?
DeFi Saver is a non-custodial automation platform that sits on top of major lending protocols. It allows you to create “automations” that trigger specific actions—such as repaying debt or withdrawing collateral—when your position’s health factor reaches a certain level. Unlike manual adjustments, these actions happen instantly via smart contracts, often within the same block as the price drop.
The primary use case for liquidation protection is to prevent the protocol from seizing your collateral. When your health factor drops to 1 (or the protocol’s threshold), liquidation begins. DeFi Saver can intervene at a higher health factor you set (e.g., 1.2) by either repaying part of the debt or withdrawing collateral, thereby raising the health factor back above the danger zone.
Why not just use the protocol’s own UI? Because none of the major lending protocols (MakerDAO, Aave, Compound) offer built-in stop-losses. DeFi Saver fills that void with a simple, configurable interface. It also supports advanced features like rebalancing (automatically swapping between assets to maintain a target ratio) and multi-step automation chains.
Understanding Health Factor and Liquidation Thresholds
To configure effective protection, you must grasp the two key metrics: Health Factor (HF) and Liquidation Threshold (LT).
- Health Factor = (Total Collateral Value × Weighted Average Liquidation Threshold) / Total Borrowed Value. Simply, it’s the buffer. An HF of 2 means your collateral is worth twice your debt. When HF drops below 1, liquidation begins.
- Liquidation Threshold is the maximum loan-to-value (LTV) ratio allowed by the protocol before liquidation triggers. For example, if a protocol’s max LTV for ETH is 80%, then at an 81% LTV your position gets liquidated.
DeFi Saver lets you set actions based on HF (or LTV, depending on the automation type). A typical stop-loss might trigger when HF = 1.15, repaying 10% of the debt to push HF back to 1.3. The exact numbers depend on your risk tolerance and the volatility of your collateral.
Illustrative example: If you’ve borrowed 10,000 DAI against 20 ETH (price $1,500/ETH), your HF at that point might be 2.0. If ETH drops to $900, HF falls to 1.2. Setting a stop-loss at 1.2 with a 5% debt repay could restore HF to ~1.25, avoiding a likely liquidation if ETH drops further.
Step 1: Connecting Your Wallet and Selecting the Protocol
Begin by visiting app.defisaver.com and connecting your wallet (MetaMask, WalletConnect, Ledger, or any Web3 wallet). Ensure you are on the correct network: Ethereum mainnet (or supported L2s like Arbitrum/Optimism). DeFi Saver supports protocols on multiple networks, but for liquidation protection, the most common are MakerDAO (Ethereum), Aave, and Compound.
Once connected, the dashboard will display your existing positions if you have any open loans on those protocols. If you don’t have a position yet, you’ll need to open one via the protocol’s native UI or directly through DeFi Saver’s “Create Position” flow. The platform reads your on‑chain debt and collateral data automatically.
Click on the position you want to protect. You’ll see its current health factor, collateral amount, debt amount, and the protocols involved. From here, you can create automations.
Step 2: Creating a Stop‑Loss (Automated Repay or Collateral Withdrawal)
Select Automations from the position’s menu. Choose Stop‑Loss / Repay as the automation type. You’ll be asked to define:
- Trigger Condition: Health Factor ≤ X (e.g., 1.15) or LTV ≥ Y (e.g., 75%).
- Action: Repay a percentage of your debt (e.g., 10% of the outstanding loan) or withdraw a percentage of collateral (less common because it could worsen the ratio unless you simultaneously sell). The recommended action is repaying debt.
- Fund Source: You can use existing tokens in your wallet or allow the automation to swap collateral to the debt asset via a built-in DEX (e.g., 1inch). This is crucial: if you only hold collateral and no stablecoins, you can enable “Swap collateral to repay debt”—the automation will sell a small portion of your collateral for the debt asset and then repay.
Review the estimated gas cost and transaction. Approve the automation via your wallet. Once confirmed, the stop‑loss is active. DeFi Saver will monitor the blockchain for your trigger condition and execute the repay when met.
Step 3: Setting Up Rebalancing Rules for Ongoing Protection
Unlike a one‑time stop‑loss, rebalancing is a continuous automation that keeps your health factor within a target range. For example, you want your HF to stay between 1.5 and 2.0. When HF rises above 2.0 (due to collateral price increase), the automation can borrow more stablecoins to reinvest. When HF falls toward 1.5, it can repay debt to bring it back up.
In DeFi Saver, create a Rebalance automation with these parameters:
- Lower Health Factor Target e.g., 1.5 — once HF hits this, the automation will either repay debt or add collateral (if available) to push HF higher.
- Upper Health Factor Target e.g., 2.0 — if HF exceeds this, it will borrow more to increase leverage.
- Adjustment Amount — how much debt to repay or borrow (typically 5–15% of the current debt).
Rebalancing effectively creates an automated loop that maintains your desired risk profile. Note that rebalancing actions incur gas fees and may involve swaps. Set your targets wide enough to avoid excessive tiny adjustments.
Step 4: Testing and Monitoring Your Automation
After creating an automation, you can see its status in the Automations tab. DeFi Saver will display the current trigger value, last execution, and if it’s active. You can also simulate the automation using the “What‑If” tool on the platform: adjust the price of your collateral to see when the stop‑loss would fire and what the resulting health factor would be.
It’s smart to test with a small position first. For instance, if you have a $1000 position, set a stop‑loss at HF=1.3 with a 10% repay. Then manually simulate a price drop (using the dashboard’s price slider) to confirm the automation would trigger as expected.
Monitoring: DeFi Saver does not send notifications by default, but you can connect a Telegram bot or email via the platform’s settings. This is important because if you run out of gas or the automation fails due to slippage, you need to know.
Advanced: Combining Stop‑Loss with Rebalancing for Dual Protection
For maximum safety, you can stack a stop‑loss and a rebalance on the same position. The rebalance actively keeps the health factor in a safe range during normal market moves. The stop‑loss acts as a circuit breaker if the market gaps down faster than the rebalance can respond.
How to set it up: First create a rebalance automation with a lower target of, say, HF=1.4 and upper of HF=1.8. Then create a stop‑loss at HF=1.1 with a larger repayment (e.g., 20% of debt). The rebalance will fire more often to keep HF from drifting too low, while the stop‑loss is a last resort.
Important: The stop‑loss override condition should be more aggressive than the rebalance lower target. Otherwise they might conflict (e.g., rebalance tries to repay 5% while stop‑loss also wants to repay 20%). DeFi Saver handles this by executing automations sequentially based on priority, but careful configuration avoids redundant actions.
This dual setup is recommended for volatile assets like ETH, LINK, or small‑cap collaterals where price swings can be 15–20% in a few minutes.
Limitations and Risks to Consider
No automation is bulletproof. Here are the key risks with using DeFi Saver for liquidation protection:
- Gas and Slippage: The automation must pay gas to execute. If the network is congested, your transaction might be delayed or fail. In a flash crash, gas spikes can cause missed triggers. Set reasonable gas limits and consider using a strategy that includes a swap liquidity buffer.
- Flash Crashes: If the price drops by 40% in one block (e.g., a flash loan attack or black swan), even the fastest automation may not execute in time before the liquidation starts. The protection is only as fast as the block time (~12 seconds on Ethereum).
- Automation Cost: Each execution costs gas. If your position is small, gas fees might outweigh the benefit. Better suited for positions over $5,000–10,000.
- Smart Contract Risk: DeFi Saver’s contracts have been audited, but no contract is immune to bugs. Only use amounts you can afford to lose.
- Token Swap Risk: If your stop‑loss uses a swap to convert collateral to debt, the swap might suffer high slippage during volatile periods. Always set a slippage tolerance in the automation settings (e.g., 2–5%).
Despite these limitations, for most intermediate users, DeFi Saver’s automation is a massive upgrade over manual monitoring.
Frequently asked questions
Does DeFi Saver guarantee I won't be liquidated?
No. While the automation is designed to execute before liquidation, extreme black‑swan events, gas spikes, or smart‑contract failures can still result in liquidation. It drastically reduces the probability, but doesn't eliminate it.
What fees does DeFi Saver charge?
DeFi Saver does not charge a subscription fee for basic automations. However, you pay standard Ethereum gas fees for each automation trigger, plus any swap fees (e.g., 1inch) if you use the swap‑to‑repay feature. DeFi Saver may also charge a small service fee on automated actions.
Can I use DeFi Saver for multiple positions across different protocols?
Yes. After connecting your wallet, you can see all your positions from MakerDAO, Aave, Compound, etc., in one dashboard, and set up separate automations for each.
What if I run out of tokens in my wallet to repay debt?
DeFi Saver can automate a swap of your collateral to the debt asset before repaying. However, if the swap fails due to low liquidity or high slippage, the stop‑loss may not execute. Ensure you have enough allowance and liquidity.
Related reading
Track the entities behind the concepts
DeFi Intel maps 11,000+ protocols, tokens and companies to a typed knowledge graph — with live data, incidents and regulation.