Aave
Aave is the reference comparison for a generalized reserve-based money market. The useful contrast is not whether Lyrasing should imitate Aave. It is which assumptions a mature pooled collateral market can make at the reserve level, and which assumptions become incomplete when candidate collateral is an LRT with restaking and AVS exposure.
Primitive boundary
| Axis | Aave | Lyrasing methodology |
|---|---|---|
| Primitive owned | Liquidity pools with reserve-level supply and borrow markets. | A future restaking-aware money-market policy surface. |
| Collateral decision | Reserve configuration governs whether an asset can be used as collateral and how much can be borrowed against it. | Candidate LRT review would require price, liquidity, redemption, operator, vault, AVS, slashability, and insurance evidence before any collateral policy. |
| Position safety | Health factor combines collateral value, weighted average liquidation threshold, and borrow value. | The same family of safety language would need AVS timing and insurance-capacity inputs before recursive exposure is allowed. |
| Liquidation posture | Liquidation is triggered when health factor falls below the protocol threshold and depends on reserve parameters and liquidation mechanics. | Liquidation review would ask whether the LRT exit path and slash window can be absorbed before collateral value or redeemability changes. |
Reserve risk versus AVS-aware collateral review
Aave’s reserve documentation treats each token reserve as an instance inside a liquidity pool with parameters such as LTV, liquidation threshold, borrowing enabled state, and supply or borrow caps. Its user-facing health-factor docs explain that liquidation risk is evaluated through collateral value, weighted liquidation thresholds, and borrow value.
That model is precise for a generalized money market, but it does not by itself answer Lyrasing’s restaking-specific questions:
| Review question | Why Aave-style parameters are not enough |
|---|---|
| Which AVSs or networks can affect the backing asset? | A reserve parameter can gate borrowing power, but it does not identify operator set, vault, or service-specific slash exposure. |
| How long can the position remain slashable after an exit or deallocation starts? | Liquidation threshold posture needs timing evidence if the collateral can be impaired before liquidation can safely unwind. |
| Is there mapped insurance capacity for the same slash surface? | Insurance language should not support LTV unless capacity is tied to the exposure that can create a shortfall. |
| Can the liquidation route absorb recursive LRT exposure? | Looping reuses the same collateral thesis; reserve-level comfort does not prove unwind depth for repeated exposure. |
What Lyrasing would need to prove
Before any future market borrowed from Aave-like collateral assumptions, Lyrasing would need evidence that the candidate LRT has:
- observable price, redemption, liquidity, and oracle units;
- current primary-source AVS exposure and operator-set inputs;
- a slashability-timing model compatible with liquidation and withdrawal paths;
- insurance-capacity language mapped to the same exposure, or a policy that ignores insurance for parameter support;
- loop-policy constraints that compress recursive exposure before single-supply collateral use becomes unsafe.
That evidence would still be methodology until implemented. This page does not claim an Aave integration, Aave replacement, active market, active LTV, active reserve, supported collateral list, or working app.
Primary sources
- Aave V3 Reserve docs , for reserve-level LTV, liquidation threshold, borrow state, and caps.
- Aave Health Factor and Liquidations , for health factor and liquidation-process language.
- Aave collateral status guide , for LTV and liquidation-threshold framing through governance-set parameters.