When a Price Feed Is Fresh but Still Wrong
One oracle risk that deserves more attention is the difference between a quoted exchange rate and a price people can actually trade at.
This becomes especially important when an asset is used as DeFi collateral.
DIA’s work with Twin Finance and DAMM Capital is a useful example.
Twin Finance issues local-currency stablecoins such as ARGt, BRAt and BOLt. DAMM Capital curates lending markets for these assets on Morpho.
The challenge? In some emerging markets, official exchange rates can differ significantly from executable market rates. Thin onchain liquidity can make displayed prices even less reliable.
DIA addresses this by building feeds from relevant trading venues, including Belo, and checking them against independent references such as Binance and Coinbase.
One detail stands out: If the sources diverge beyond the agreed threshold, the feed holds its last good value instead of publishing an uncorroborated price.
That is a targeted safeguard, not a guarantee against every bad-data event or liquidation loss.
For me, the bigger lesson is simple:
A lending protocol needs more than a price that updates regularly. It needs a pricing method suited to the asset, its liquidity and the market where it actually trades.
That’s when oracle infrastructure becomes part of risk management—not just a data endpoint. $DIA