Liquidation dependencies: price input to debt recovery
A liquidation mechanism depends on more than a fresh oracle value. Research the entire chain from price input to eligibility, transaction execution and debt recovery. This is a study of a spot lending protocol’s dependencies, not instructions for opening a leveraged position or carrying out liquidations.
Aave’s health-factor documentation relates collateral value, weighted liquidation thresholds and borrow value. That relationship illustrates how price inputs can affect eligibility. Actual reserve settings, market versions and execution rules still need deployment-specific evidence.
Map the dependency chain
Start with the asset pair and the price adapter actually consumed by the protocol. A feed visible in a dashboard is not necessarily the value used by the relevant contract. Record unit scale, quote currency, adapter transformations and update conditions before connecting that input to a threshold calculation.
Next identify the eligibility rule and applicable account configuration. Distinguish maximum borrowing conditions from liquidation thresholds; their labels and roles should not be merged. Then ask what transaction can realize recovery, which assets it exchanges, and what operational constraints can prevent or delay it.
Separate eligibility from economic completion. A position can satisfy a liquidation condition while execution is delayed, unavailable or insufficient to recover the debt. Conversely, a transaction that reduces debt does not by itself establish that all remaining obligations are covered. Keep a recovery ledger rather than stopping at a threshold crossing.
Hypothetical price-adapter discrepancy
Assume a fictional protocol has collateral marked at 150 units, a stipulated liquidation threshold of 80%, and debt valued at 110. A simplified health ratio is 150 × 0.8 / 110, about 1.09. If the consumed collateral value becomes 130, that ratio becomes about 0.95.
Now suppose an external dashboard continues showing 150 while the protocol adapter uses 130. A memo based on the dashboard would describe the wrong eligibility state. The research correction is to identify the consumed input and timestamp, not to select whichever price looks more reasonable. All values and thresholds are hypothetical.
Even with eligibility established, recovery still requires an accepted execution and the relevant asset flows. If only 100 units of compatible value are actually recovered against 110 of debt, the remaining ten needs separate investigation. The arithmetic intentionally distinguishes a threshold signal from a recovery result.
Dependency worksheet
| Link | Evidence question |
|---|---|
| Raw price input | Which pair, source and observation time? |
| Adapter | Which transformations and fallback conditions? |
| Eligibility | Which threshold and account configuration? |
| Execution | Which contract state and operational prerequisites? |
| Recovery | What debt reduction and asset receipt actually occurred? |
| Remainder | What exposure remains after execution? |
For each link, state whether the evidence is a general specification, observed deployment state or executed transaction. These levels support different conclusions. A published formula explains a mechanism; it does not establish a current account balance or guarantee that an execution will occur.
Test distinct failure modes
Consider stale input, wrong unit scale, adapter mismatch, unavailable execution and poor recovery as separate scenarios. Do not add their hypothetical losses as independent probabilities. Some share the same cause, and several may describe different stages of one event.
The final memo should identify which dependency matters to the asset thesis and what observation would trigger review. For example, a change in the consumed adapter calls for a different check from a reduction in available recovery liquidity. Avoid presenting one healthy metric as assurance for the whole chain or inferring a price forecast from a modeled threshold.
FAQ
Does a current oracle timestamp guarantee successful recovery?
No. Eligibility, execution conditions and realized asset recovery remain separate dependencies.
Is a dashboard price sufficient to reproduce a health calculation?
Only if evidence establishes that the protocol consumed that value with compatible units and account settings at the relevant time.