How Does DeFi Saver Work?

DeFi|Risk B|5 mechanisms|4 interactions

DeFi Saver is a non-custodial DeFi management tool that provides automated leverage management, liquidation protection, and one-click position adjustments across MakerDAO, Aave, Compound, Liquity, and Morpho. Operating since 2019 with no security incidents and multiple audits (ConsenSys, Dedaub), its B+ grade reflects mature automation patterns and a clean track record, with moderate risk from cross-protocol composability.

TVL

$303M

Sector

DeFi

Risk Grade

B

Value Grade

D

Core Mechanisms

6.1.1

CDP management interface for MakerDAO, Liquity, and CurveUSD overcollateralized positions

Standard overcollateralized lending management — DeFi Saver provides UX layer on top of existing CDP protocols

6.3.2

Automated liquidation protection via collateral ratio monitoring and keeper-triggered repay recipes

Standard automation pattern — keeper bots trigger predefined recipes when collateral ratio crosses threshold

2.1.2

Service fees on automated strategy executions and recipe transactions

Standard percentage-based fee on swap amounts within recipes

5.2.3

7-day timelock on core smart contracts, 1-day timelock on strategy contracts

Standard timelocked governance pattern for contract upgrades

6.2.1

Recipe system for composing multi-step DeFi actions into single atomic transactions

Recipes compose supply, borrow, swap, and repay actions across multiple protocols into single transactions using flash loans. Standard DeFi action composition pattern.

How the Pieces Interact

Automated leverage management↔Multi-protocol integration (Aave, Maker, Compound)High

Automated recipes execute across multiple protocols in single transactions. A state change or pause on any underlying protocol mid-recipe could cause partial execution, leaving positions in unexpected states.

Keeper bot automation↔Flash loan executionMedium

During extreme volatility, keeper bots may compete with other DeFi bots for block space. Combined with potential flash loan liquidity constraints, automated protections could fail to execute when most needed.

Cross-protocol recipes↔Oracle price feedsMedium

Multi-step recipes rely on consistent oracle pricing throughout execution. Oracle updates between recipe steps could change expected swap rates or collateral ratios, though single-transaction execution mitigates this for most scenarios.

Recipe system↔Protocol upgrade compatibilityLow

When integrated protocols upgrade (e.g., Aave V2 to V3, MakerDAO to Sky), recipe paths may break or behave unexpectedly if contract interfaces change, requiring rapid DeFi Saver updates.

What Could Go Wrong

  1. Smart contract composability risk — DeFi Saver interacts with multiple underlying protocols (MakerDAO, Aave, Compound, Morpho, Liquity) through automated recipes. A vulnerability in any integrated protocol could cascade through DeFi Saver positions.
  2. Automation bot dependency — automated strategies (stop-loss, take-profit, leverage management) rely on off-chain keeper bots to monitor and execute transactions. Bot downtime or network congestion during volatile periods could prevent timely execution.
  3. Flash loan execution risk — complex multi-step recipes use flash loans to execute leveraging/deleveraging in single transactions. During extreme market conditions, flash loan liquidity or DEX slippage could cause recipe failures at critical moments.

Automation Failure During Market Crash

Tail

Trigger: ETH price drops 40%+ within 2 hours while Ethereum gas prices exceed 500 gwei, causing DeFi Saver keeper bots to fail on automated liquidation protection recipes

  1. 1.Rapid ETH price decline triggers automated repay/liquidation protection for thousands of DeFi Saver positions simultaneously — Keeper bots submit transactions but compete with other liquidation bots and MEV searchers for block inclusion
  2. 2.Gas costs spike to levels where keeper transactions become uneconomical for smaller positions — Positions below a certain size threshold are not protected, falling through to underlying protocol liquidation
  3. 3.Flash loan liquidity dries up as Aave and other lending pools reach high utilization — Leverage-reduction recipes that depend on flash loans fail, leaving leveraged positions exposed to cascading liquidation on underlying protocols
  4. 4.Users with failed automation face liquidation penalties on MakerDAO (13%) or Aave — Users lose liquidation penalties they expected automation to prevent; trust in DeFi Saver automation decreases
See all 2 collapse scenarios in the full risk report →

Risk Profile at a Glance

Mechanism Novelty0/15
Interaction Severity5/20
Oracle Surface2/10
Documentation Gaps2/10
Track Record3/15
Scale Exposure5/10
Regulatory Risk4/10
Vitality Risk4/10
B

Overall: B (25/100)

Lower score = safer

More on DeFi Saver

Is DeFi Saver Safe?

Safety analysis

Is DeFi Saver a Good Investment?

Value analysis

Full Risk Report

All mechanisms & interactions

Related DeFi Explainers

How Does Truebit Work?DHow Does Flying Tulip Work?C-How Does Arkis Work?C-How Does Virtuals Protocol Work?CHow Does Makina Work?C