Morpho is back on the Radar because a new governance post changes the risk surface underneath eligible markets, not because it adds another generic parameter tweak.
This is an oracle-architecture story. When a protocol replaces a single hardcoded feed path with layered fallback logic, liquidation quality and market safety move onto the same research page.
What Happened
A Morpho governance post published on April 27, 2026 says Steakhouse is upgrading the oracle architecture of Prime BTC and ETH related markets on Ethereum mainnet. The post says some cbBTC markets previously relied on a single hardcoded Chainlink BTC feed on collateral price with no fallback.
The same post says the upgraded design uses MetaOracles with SVR primary feeds and standard Chainlink backups, including a 2% deviation threshold, a two-hour challenge timelock and an eight-hour healing timelock for the backup-switch logic on affected markets.
Why It Matters
For Radar, the signal is that oracle design is being treated as live protocol plumbing rather than static configuration. That matters because fallback behavior determines how gracefully markets behave when the preferred price route is stressed or diverges from the underlying collateral.
The introduction of SVR routing also changes the liquidation conversation. The proposal frames it as a way to make the path more deterministic and to reduce the need for chaotic public-mempool liquidation races.
This is useful discovery because it is not just “new oracle address” maintenance. It is a redesign of how prime markets surface price truth and failure handling on Ethereum mainnet.
What To Watch Next
Watch whether delegates focus more on fallback assumptions than on the headline oracle upgrade itself, especially around cbBTC-specific depeg edge cases.
The next useful checkpoint is whether the upgraded markets behave more legibly under stress without introducing new operational opacity for observers.
This stays on Radar because oracle fallback design often matters most before the failure path is needed, not after.
Continue this cluster
Protocol risk surfaces get easier to judge when oracle design, fallback mechanics and liquidation routing are reviewed as one connected operating layer.
