𝗬𝗼𝘂𝗿 𝗯𝗮𝗻𝗸 𝘄𝗶𝗹𝗹 𝗵𝗮𝗽𝗽𝗶𝗹𝘆 𝗱𝗲𝗰𝗹𝗶𝗻𝗲 𝗮 𝟵𝟬,𝟬𝟬𝟬 𝗱𝗼𝗹𝗹𝗮𝗿 𝗰𝗼𝗳𝗳𝗲𝗲, 𝗲𝘃𝗲𝗻 𝗶𝗳 𝘁𝗵𝗲 𝗰𝗮𝗿𝗱 𝗮𝗻𝗱 𝗣𝗜𝗡 𝗮𝗿𝗲 𝗽𝗲𝗿𝗳𝗲𝗰𝘁. That coffee is an illustration, but the logic is real. The transaction is technically valid. It is just obviously wrong. Good systems have limits that catch nonsense before it becomes damage. @WinkLink_Oracle price feeds have exactly that kind of sanity limit built into the aggregator. The developer docs list two variables on it: ➜ 𝗺𝗮𝘅𝗔𝗻𝘀𝘄𝗲𝗿 is the upper bound the aggregator is allowed to report ➜ 𝗺𝗶𝗻𝗔𝗻𝘀𝘄𝗲𝗿 is the lower bound ➜ 𝗢𝘂𝘁𝘀𝗶𝗱𝗲 𝘁𝗵𝗲 𝗿𝗮𝗻𝗴𝗲, a report whose median falls above the maximum or below the minimum is rejected ➜ 𝗜𝗻𝘀𝗶𝗱𝗲 𝘁𝗵𝗲 𝗿𝗮𝗻𝗴𝗲, the normal process of nodes and medians carries on Think of it as the fraud check on a card. Most days you never notice it. On the one day something absurd tries to get through, it is the only thing that matters. This is a different layer from the median itself. The median stops a dishonest minority from dragging the price. The bounds stop a report from landing somewhere no sane market could be. As a reader, you can check both values yourself on the aggregator contract. I would still add my own checks in my app, the way you still read your statement. The aggregator variables are documented here: https://t.co/BVkWssd0mw 𝗔 𝘃𝗮𝗹𝗶𝗱 𝗰𝗮𝗿𝗱 𝗶𝘀 𝗻𝗼𝘁 𝘁𝗵𝗲 𝘀𝗮𝗺𝗲 𝗮𝘀 𝗮 𝘀𝗲𝗻𝘀𝗶𝗯𝗹𝗲 𝗽𝘂𝗿𝗰𝗵𝗮𝘀𝗲. Bounds know the difference. @justinsuntron @WinkLink_Oracle #TronEcoStar