Dice9 would have not received any alerts prior to the incident, precision from the perspective of the Dice9 team is 100%. While the protocol doesn't have a pause functionality, it does have a 'setMaxProfit' function, could have been used as a proxy function for incident response

With the launch of Attack Detector 2.0 and @OpenZeppelin Defender 2.0, incident response is ready, reliable, and prepped for deployment 🛡️ More on incident response soon 👀

This is where things get interesting 🤔 Forta’s Attack Detector fired at 07:57:02 GMT just after the first successful exploit but the BEFORE subsequent exploits that resulted in the loss of $25K. Inside the Forta alert, Dice’s address was identified

So, if Dice9 was subscribed to the Attack Detector and automatically paused the protocol upon receiving the alert, the protocol would have only lost 0.1 BNB (around $22) instead of the 25K in BNB they did loose AND mitigated any other potential losses

The $25K hack of

t.co

could have been a lot worse, but thanks to SEAL911, the protocol saved $200k after engaging in active incident response measures 🛡️ But if Forta monitoring was integrated, ALL funds would be safe 👇