FRAC presale: check the current server quote, availability and allocation terms — Buy Now
MIDAS / RESCUE

Protection with clear boundaries.

Review permissions, conditions and availability before taking action.

  1. 01Permissions
  2. 02Conditions
  3. 03Action

MIDAS Rescue Protocol

Save your Aave V3 position on Base before liquidation · fee … wFRAC (read live from the contract)

Intelligence
Validating on-chain…
Simulating the rescue call against the deployed vault… Sending stays locked until the deployed vault confirms the call format.
Aave liquidation penalty (WETH)
…
liquidation bonus paid to liquidators, from Aave ProtocolDataProvider · varies by asset
MIDAS Rescue Fee
… wFRAC
reading rescueFeeWfrac()…
Aave flash-loan premium
…
FLASHLOAN_PREMIUM_TOTAL, plus Uniswap V3 swap fee (0.05–1%) when collateral ≠ debt asset

Check Your Position

Guardian — automatic rescue

Store a rescue policy on-chain once. If your Aave health factor on Base drops below your trigger, a FractalAI keeper runs the same atomic flash-loan rescue for you — it pays the gas, you pay the … wFRAC fee per rescue.

Inactive
Connect a wallet to see your status
Checking the deployed V2 vault…
Set it up once, let the keeper watch
  • 1. Choose debt to repay, collateral to use, your HF trigger (1.00–3.00) and a per-rescue cap.
  • 2. Approve a bounded amount of aTokens and the fee × the number of rescues you want covered.
  • 3. Sign enableGuardian. Disable any time; the policy expires on the date you set (max 365 days).

What the guardian is — and is not

The trigger is on-chain

The keeper can only act while Pool.getUserAccountData says healthFactor < your trigger. It never decides which asset, how much slippage or which fee: those come from your policy.

A smaller window, not zero

The node rescans Base every ~20 s and the keeper loop runs every ~10 min. A sharp crash can still liquidate you before the keeper reacts. This reduces the liquidation window; it does not remove it.

Who pays what

You pay the wFRAC fee per rescue (frozen at the value shown when you activate). The keeper pays gas. A rescue must leave your HF strictly higher and at least …, or it reverts entirely.

Approvals are the leash

Without a live aToken and wFRAC allowance the rescue reverts. Approvals are bounded (never unlimited): revoke them in your wallet and the keeper is powerless, even with the policy on.

This is best-effort automation bounded by feed latency, gas, pool liquidity and competing liquidators — not guaranteed protection. Vault V2: 0x6541…D37C · keeper 0x0f5a…CceE · bytecode on Base, not audited by a third party.

How Rescue Works

  1. 1

    You approve the vault to pull the aTokens of your collateral (bounded to your balance, never unlimited) and approve the … wFRAC fee in wFRAC. Both allowances are required by the contract — without the wFRAC allowance the rescue reverts.

  2. 2

    The vault takes an Aave V3 flash loan to repay your debt. The whole thing is one atomic transaction: if any step fails, everything reverts and your position is untouched.

  3. 3

    The vault withdraws just enough of your collateral, swaps it on Uniswap V3 (when it is not the debt asset, slippage capped by the maximum you choose) and repays the flash loan plus premium. Leftover collateral and aTokens are returned to you.

  4. 4

    Fee: read live from the contract (50% burned, 50% treasury).

Fee split: 50% burned → deflationary pressure on wFRAC. 50% to treasury → funds MIDAS infrastructure.Contract: 0x54b1…6403 (bytecode deployed on Base; not audited by a third party).

Aave positions tracked by the MIDAS scanner(near liquidation = HF < 1.2; addresses are not published)

Reading scanner telemetry…