Understanding the economics of an oracle is a key part of risk analysis for lenders and borrowers.
At @credditxyz, we tried to come up with a standardized way to explain oracle configurations across every lending protocol.
For borrowers, the focus is on liquidation drivers: what can actually change your health factor?
btw shoutout to @EthanDeFi_ who's been relentlessly pushing lending protocols to surface more oracle transparency in their own UI.
Fluid does provide the relevant economic implications already in their UI.
Morpho also showed some initiative and introduced a methodology that classifies each feed using the oracle provider's own published categories or, for contracts such as vaults, how the contract calculates its price.
A feed can therefore be labelled NAV even when market prices enter the calculation underneath it.
Take the @protocol_fx fxSAVE market for example.
Morpho classifies it as NAV type because the oracle uses fxSAVE’s net asset value, so 'NAV' describes the calculation.
But that value depends on the fxUSD and USDC held in the underlying stability pool.
And fxUSD is valued using a moving average of its market price.
An fxUSD depeg can therefore lower your health factor and trigger liquidation, even though the oracle is labelled NAV.
The label is technically valid.
But "NAV"/"exchange price"/"redemption value" are often understood as being the valuation marked by the issuer, not any market price.
Hence this can be misleading in terms of economic implications for the borrower.
At creddit, the focus is on translating an oracle into economic meaning for the borrower and this consistently across every lending protocol.
We use various labels but the two main types are 'Market price" and "NAV".
For example we use "Market price" when the oracle reads the collateral’s own market price or a synthetic dollar's market price beneath it.
fxSAVE falls into the second category because fxUSD market price feeds the oracle.
We use "NAV" when the collateral is valued at its issuer’s redemption value, and the underlying stablecoin is fixed at par or is one of the major fiat backed stablecoins.
Taking fiat backed stablecoins at par for this classification is a choice, in theory stables like USDC / USDT / USDG can also show some market price fluctuations.
Where collateral and debt use the same price feed, that exposure can cancel.
For example, syrupUSDT/USDT on @aave uses the same USDT/USD feed on both sides.
Where it doesn't cancel, that residual risk is explained separately in the collateral/debt detailed section.
@pendle PTs have more specific labels to distinguish market pricing, fixed discounts and pricing limits.
Any feedback is welcome. @credditxyz is in beta, DM for access code
At @credditxyz, we tried to come up with a standardized way to explain oracle configurations across every lending protocol.
For borrowers, the focus is on liquidation drivers: what can actually change your health factor?
btw shoutout to @EthanDeFi_ who's been relentlessly pushing lending protocols to surface more oracle transparency in their own UI.
Fluid does provide the relevant economic implications already in their UI.
Morpho also showed some initiative and introduced a methodology that classifies each feed using the oracle provider's own published categories or, for contracts such as vaults, how the contract calculates its price.
A feed can therefore be labelled NAV even when market prices enter the calculation underneath it.
Take the @protocol_fx fxSAVE market for example.
Morpho classifies it as NAV type because the oracle uses fxSAVE’s net asset value, so 'NAV' describes the calculation.
But that value depends on the fxUSD and USDC held in the underlying stability pool.
And fxUSD is valued using a moving average of its market price.
An fxUSD depeg can therefore lower your health factor and trigger liquidation, even though the oracle is labelled NAV.
The label is technically valid.
But "NAV"/"exchange price"/"redemption value" are often understood as being the valuation marked by the issuer, not any market price.
Hence this can be misleading in terms of economic implications for the borrower.
At creddit, the focus is on translating an oracle into economic meaning for the borrower and this consistently across every lending protocol.
We use various labels but the two main types are 'Market price" and "NAV".
For example we use "Market price" when the oracle reads the collateral’s own market price or a synthetic dollar's market price beneath it.
fxSAVE falls into the second category because fxUSD market price feeds the oracle.
We use "NAV" when the collateral is valued at its issuer’s redemption value, and the underlying stablecoin is fixed at par or is one of the major fiat backed stablecoins.
Taking fiat backed stablecoins at par for this classification is a choice, in theory stables like USDC / USDT / USDG can also show some market price fluctuations.
Where collateral and debt use the same price feed, that exposure can cancel.
For example, syrupUSDT/USDT on @aave uses the same USDT/USD feed on both sides.
Where it doesn't cancel, that residual risk is explained separately in the collateral/debt detailed section.
@pendle PTs have more specific labels to distinguish market pricing, fixed discounts and pricing limits.
Any feedback is welcome. @credditxyz is in beta, DM for access code
0:41
been in many 15min twap PT markets so i think the criticism against @SteakhouseFi using a fundamentally unsafe oracle is unwarranted + loopers can avoid liquidation entirely by lowering health factors to unliquidatable levels based on pendle yield rangesView quoted post on X
it also does not help that the market went from linear discount to twap from the last PT market to the current which probably caught a bunch of loopers offguard
i do think all lending platforms need to have MUCH richer oracle descriptions. seems trivial to add with a few prompts @aave @Morpho @eulerfinance @0xfluid