RedStone disputes oracle failure in $75M Tectonic exploit

While independent researcher Weilin Li estimated the losses at $75 million, Kazmierczak argues the oracle performed as designed by reporting the actual market price from the pool it monitored. The vulnerability, he contends, lay in Tectonic’s decision to accept that spot price as collateral without verifying if the token possessed sufficient liquidity to support such a valuation. By failing to implement borrow caps linked to executable liquidity, the protocol allowed the attacker to borrow against inflated, thin-market assets.

Kazmierczak emphasized that reporting a price and validating its safety for lending are distinct functions that Tectonic conflated. He suggested that even with a time-weighted average price, the sheer scale of the 100-fold spike should have triggered an automatic disqualification of the token as collateral. The exploit mirrors historical attacks on protocols like Mango Markets, where governance tokens with low liquidity were weaponized to drain deep-pool assets. Following the incident, Cronos validators executed an emergency chain rollback to a pre-attack state to secure the network, though a formal technical postmortem from Tectonic remains pending.