Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Aave V3 and Compound III handle liquidation risk differently. Aave tracks a position with a Health Factor and documents a PriceOracleSentinel that can pause borrowing and liquidation during certain oracle or Layer 2 sequencer interruptions. Compound III separates borrowing capacity from liquidation eligibility with two collateral factors, then absorbs underwater accounts using protocol reserves. Neither design makes a market categorically safer: the configured feeds, parameters, liquidity, reserves, governance and execution conditions matter.
How do their oracle and liquidation designs compare?
| Question | Aave V3 | Compound III |
|---|---|---|
| How are prices configured? | Each reserve has an oracle, with the source selected through Aave Governance. Aave’s documentation names Chainlink Price Feeds and CAPO among production oracle types. Aave Oracle documentation | Governance can set the base-token price feed and update feeds for individual assets. The documentation does not establish one universal vendor or setup. Compound Governance documentation |
| What indicates liquidation eligibility? | A position’s Health Factor; below 1 makes it eligible for liquidation. Aave V3 Overview | Whether the account’s borrowing exceeds the limit set by liquidation collateral factors, which are separate from and higher than borrow collateral factors. Compound Liquidation documentation |
| What happens in liquidation? | A liquidator repays part of the debt and receives collateral with a reserve-defined liquidation bonus. Aave V3 Overview | A liquidator calls absorb; collateral transfers to the protocol and protocol cash reserves pay off the borrow. Eligible liquidators may then buy protocol-held collateral at a feed-based discount. Compound Liquidation documentation |
| Is there a documented outage gate? | PriceOracleSentinel controls can disallow borrowing and liquidation while the oracle is down or a recovery grace period is active, particularly for L2 sequencer interruptions. Aave Oracle contract reference | The reviewed documentation describes configurable feeds and pause controls, but not a directly equivalent oracle/sequencer recovery-grace sentinel. That does not establish that no other operational safeguards exist. Compound Governance documentation |
How does Aave V3 handle oracle and liquidation risk?
Oracle selection is reserve-specific
Aave’s oracle documentation says each reserve uses an oracle contract to report market prices, and Aave Governance selects the source. How and when a source updates can depend on its logic—for example, a time-based or deviation-based update rule. The documentation identifies Chainlink Price Feeds and the Correlated Assets Price Oracle (CAPO) as primary oracle types on production Aave markets. CAPO is intended for strongly correlated assets, such as wrapped tokens whose value follows an underlying asset. Aave’s oracle documentation
A position’s Health Factor determines eligibility
Aave’s borrowing overview describes an overcollateralized position whose Health Factor responds to oracle-priced collateral, debt and accrued interest. Each reserve has its own liquidation threshold. If the Health Factor falls below 1, external liquidators may repay part of the debt and receive collateral at a reserve-defined discount, expressed through its liquidation bonus. The threshold and bonus are reserve parameters, not universal values for every asset or market. Aave V3 Overview
The sentinel addresses a specific outage scenario
Aave’s PriceOracleSentinel can block borrowing and liquidation while the price oracle is down or while a grace period after recovery remains in effect. The documented purpose is especially relevant to Layer 2 sequencer downtime: after service returns, users get time to make positions healthy before liquidations resume. The contract reference also describes authorized admin roles for managing asset sources and the fallback oracle. This is an operational safeguard for specified conditions, not protection against every incorrect or manipulated price. Aave Oracle contract reference
#1 Best Overall
Other controls do not remove oracle or market risk
Aave’s governance materials describe controls including isolation mode, supply and borrow caps, risk-admin roles and the oracle sentinel. Aave also warns that third-party oracle failure or compromise can cause incorrect valuations, while volatile or illiquid collateral can become undercollateralized or create bad debt. It identifies LTV ratios and liquidation thresholds, monitored by risk service providers and adjustable through governance, as mitigations—not guarantees. Aave V3 governance introduction · Aave Risks
How does Compound III handle oracle and liquidation risk?
Borrow capacity and liquidation eligibility use different factors
Compound III lets users supply crypto assets as collateral to borrow a market’s base asset. For each collateral asset, the borrow collateral factor determines how much of its USD value counts toward borrowing capacity. Passing or failing that borrowing check is not the same as being liquidatable. A separate, higher liquidation collateral factor sets the liquidation boundary and creates a price buffer between opening a position and becoming eligible for liquidation. Compound Collateral & Borrowing documentation · Compound Liquidation documentation
Rank #2
- Ideal for Gifting
- Ideal for a bookworm
- Compact for travelling
Absorption uses protocol reserves
When an account exceeds the allowed limit under its liquidation collateral factors, a liquidator can call absorb. The protocol takes ownership of the account’s collateral and pays off its debt using base-asset cash reserves. If reserves are below a governance-set target, liquidators may be able to buy protocol-held collateral at a discount based on the price feed; those sales add base assets back to reserves. This makes reserve availability part of the liquidation mechanism, rather than having the liquidator directly repay a portion of debt in exchange for seized collateral as in Aave’s documented path. Compound Liquidation documentation
Governance controls feeds and risk settings
Compound governance operates through proposals and execution, with the Timelock controlling protocol contracts. Documented admin functions include setting the base-token feed, updating an asset’s feed, changing borrow and liquidation collateral factors, and pausing selected functions. These controls establish that settings can be governed; they do not identify one price-feed provider or prove a particular configuration applies to every deployment. Compound Governance documentation
What do these differences mean for a borrower?
The clearest design distinction is how each protocol makes the boundary between a healthy and liquidatable position legible. Aave expresses the position’s status as a Health Factor and documents a special gate for certain oracle or sequencer recovery conditions. Compound makes the separation between borrowing capacity and liquidation eligibility explicit through distinct collateral factors, and routes liquidation through absorption and protocol reserves. This is a comparison of documented mechanisms, not a measurement of safety or liquidation performance.
Oracle problems are not all the same. A feed can report an incorrect value, provide stale data, become unavailable, or be affected by a chain or sequencer outage. A sentinel designed for a particular outage case does not show that all price errors are prevented. Likewise, an orderly liquidation design cannot eliminate risks from thin market liquidity, execution delays, inadequate reserves, governance decisions or smart-contract failures. Aave explicitly discusses oracle and collateral risks; Compound documents reserve-funded absorption and governance-controlled settings. Aave Risks · Compound Liquidation documentation · Compound Governance documentation
Rank #4
What to check before comparing live markets
The protocol-level design does not tell you the live settings for a particular pair of markets. Aave’s documentation describes reserve-level oracle selection; Compound’s overview identifies Ethereum with USDC as its initial deployment, not as a description of every current market. Neither fact establishes matching, current feed addresses or risk parameters across deployments. Aave Oracle documentation · Compound overview
For a market-specific comparison, identify and record:
Best Value
- It can be a gift option
- Comes with secure packaging
- Helpful in various ways
- The exact network, market and collateral and borrow assets.
- The configured feed contracts and relevant oracle or sequencer safeguards.
- The current collateral factors and liquidation thresholds or bonuses.
- For Compound III, the base-asset reserve condition relevant to absorption and discounted collateral sales.
- Relevant governance or pause configuration, plus when the values were checked.
These settings can vary by deployment and change through governance. The official documentation reviewed on October 4, 2026 does not establish current feed addresses or numerical parameters for a matched Aave V3 and Compound III market pair. Treat any live comparison as incomplete unless those deployment-level values have been checked.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
