Oracle risk is easier to discuss at protocol level than to measure at market level. I checked TermMax's current Ethereum oracle table and found a useful contrast.
WETH lists Chainlink as the primary feed, RedStone as backup, and an 86,400-second heartbeat. cbBTC lists a Chainlink feed, the same heartbeat, but no backup feed.
That does not make cbBTC unsafe. It does mean “dual oracle” should not be treated as a blanket property of every market. Before sizing any collateral position, I would map four things: primary source, backup source, heartbeat, and whether the price is built from multiple feeds.
Risk lives in the actual price path, not in the strongest example from the protocol.
@TermMax #TermMax
WETH lists Chainlink as the primary feed, RedStone as backup, and an 86,400-second heartbeat. cbBTC lists a Chainlink feed, the same heartbeat, but no backup feed.
That does not make cbBTC unsafe. It does mean “dual oracle” should not be treated as a blanket property of every market. Before sizing any collateral position, I would map four things: primary source, backup source, heartbeat, and whether the price is built from multiple feeds.
Risk lives in the actual price path, not in the strongest example from the protocol.
@TermMax #TermMax
