𝗪𝗵𝗲𝗻 𝘁𝗵𝗲 𝗽𝗿𝗶𝗰𝗲 𝗹𝗼𝗼𝗸𝘀 𝘄𝗿𝗼𝗻𝗴, 𝘆𝗼𝘂𝗿 𝗰𝗼𝗻𝘁𝗿𝗮𝗰𝘁 𝘀𝗵𝗼𝘂𝗹𝗱 𝗴𝗲𝘁 𝗺𝗼𝗿𝗲 𝗰𝗮𝘂𝘁𝗶𝗼𝘂𝘀, 𝗻𝗼𝘁 𝗺𝗼𝗿𝗲 𝗰𝗿𝗲𝗮𝘁𝗶𝘃𝗲. @WinkLink_Oracle gives you one circuit breaker out of the box. Every aggregator has a minAnswer and a maxAnswer, and the docs say a report whose median falls outside them is rejected. That stops absurd values reaching the chain. What happens inside your own protocol after that is your design. I've seen two philosophies. The creative one tries to keep everything running by falling back to an older price, a hard-coded value or some internal estimate. The cautious one switches into a 𝘀𝗮𝗳𝗲 𝗺𝗼𝗱𝗲. Here is what I mean by safe mode, as my own pattern rather than anything WINkLink prescribes: ➜ 𝗣𝗮𝘂𝘀𝗲 𝗿𝗶𝘀𝗸-𝗶𝗻𝗰𝗿𝗲𝗮𝘀𝗶𝗻𝗴 𝗮𝗰𝘁𝗶𝗼𝗻𝘀, like new borrows or opening leveraged positions ➜ 𝗞𝗲𝗲𝗽 𝗿𝗶𝘀𝗸-𝗿𝗲𝗱𝘂𝗰𝗶𝗻𝗴 𝗮𝗰𝘁𝗶𝗼𝗻𝘀 𝗼𝗽𝗲𝗻, like repaying, adding collateral or closing positions ➜ 𝗧𝗿𝗶𝗴𝗴𝗲𝗿 𝗼𝗻 𝗰𝗹𝗲𝗮𝗿 𝗰𝗼𝗻𝗱𝗶𝘁𝗶𝗼𝗻𝘀, such as a price older than your max age ➜ 𝗥𝗲𝘀𝘂𝗺𝗲 𝗮𝘂𝘁𝗼𝗺𝗮𝘁𝗶𝗰𝗮𝗹𝗹𝘆 once a fresh, valid round arrives Users can always make themselves safer. Nobody gets liquidated or over-lent against a number that was never verified. The Developer Notes ask you to design for extreme market scenarios, and this is one concrete way to do it: https://t.co/BVkWssd0mw 𝗗𝗼𝘂𝗯𝘁 𝘀𝗵𝗼𝘂𝗹𝗱 𝘀𝗹𝗼𝘄 𝘆𝗼𝘂 𝗱𝗼𝘄𝗻. Never speed you up. @justinsuntron @WinkLink_Oracle #TronEcoStar