Tectonic’s $75M exploit was not an oracle failure, RedStone co-founder says

RedStone has said Tectonic’s estimated $75 million exploit resulted from weak collateral controls rather than an inaccurate oracle after TONIC’s reported price rose about 100-fold in 20 minutes. Summary An onchain researcher estimated that the Tectonic exploit affected about $75 million. TONIC’s reported price increased roughly 100 times before the token was supplied as collateral. RedStone said borrow caps tied to executable liquidity could have limited the losses. Cronos has restarted after restoring its chain state to a point before the attack. RedStone co-founder Marcin Kazmierczak told crypto.news that the oracle accurately reported TONIC’s price in the pool it monitored, but Tectonic allegedly accepted the reading without checking whether the token could be sold at that valuation in meaningful size. Cronos validators halted block production on Aug. 30 after Tectonic disclosed an incident involving the decentralized lending protocol. Independent researcher Weilin Li estimated that approximately $75 million was affected, although neither Tectonic nor Cronos has confirmed the final loss. According to Li’s initial analysis, the attacker pushed TONIC’s price about 100 times higher within roughly 20 minutes. The inflated tokens were then supplied to Tectonic as collateral, allowing the attacker to borrow assets with more established liquidity. TONIC reportedly had a collateral factor of 20%, meaning the protocol allowed users to borrow assets worth up to one-fifth of the collateral’s reported value. Li identified about 364.6 trillion TONIC in the position, which would have needed a reported value of around $375 million to support approximately $75 million in borrowing. You might also like: Cronos restarts network after emergency halt over Tectonic exploit Tectonic oracle reported a manipulated market price Kazmierczak rejected the idea that the oracle itself necessarily produced incorrect data, drawing a distinction between observing the available market price and deciding whether that price is safe for a lending protocol. “The oracle wasn’t wrong. It accurately reported the price of TONIC on the pool it was reading from at that moment,” he said. A thinly traded token can register a high spot price after a limited number of trades, even when the market lacks enough buyers to support large sales at the same level. According to Kazmierczak, Tectonic’s alleged failure was accepting the manipulated price as collateral without testing how much TONIC could actually be sold before its value collapsed. “Reporting a price and validating that a price is safe to lend against are two different jobs, and Tectonic’s design conflated them.” The initial Tectonic incident left most of the identified assets on Cronos when validators stopped the chain. Li estimated that about $6 million had reached Ethereum, while roughly $60 million remained at one Cronos address. A second address holding close to $8 million raised his combined estimate to about $75 million.