Oracle Aggregator (Trusted Oracle) Requirements

[vishalchangrani]

Requirements for the Oracle Aggregator

• The lending protocol (ALP / FCM) depends on a single trusted oracle interface that returns either a valid price or nil if the price should not be trusted.
• The lending protocol does not contain any logic for validating prices and simply consumes the output of the trusted oracle.
• The oracle aggregator combines multiple price sources such as on-chain DEX prices and off-chain price feeds.
• A price is considered usable only if the sources are reasonably aligned within a configurable tolerance and recent price changes are not anomalous.
• If sources diverge beyond tolerance or show suspicious short-term volatility, the aggregator returns nil and the protocol skips actions like liquidation or rebalancing.
• Governance is responsible for configuring which sources are used and what tolerances apply, not the lending protocol itself.
• This separation is intentional so the lending protocol remains reusable and does not encode assumptions about specific oracle implementations.

[vishalchangrani]

Related issue: #128

[holyfuchs]

How should recent price data be collected to ensure price changes are not anomalous?

A sudden spike in volatility will cause the price() function to revert, preventing data collection when the price() function is getting called.

Using scheduled transactions avoids this, but would likely require execution at a very short interval (e.g. < 1 minute).