.jpg)
The Tectonic exploit that drained an estimated $75 million from the Cronos lending protocol was not an oracle failure, according to RedStone co-founder Marcin Kazmierczak — the oracle did its job, and the real weakness was Tectonic's willingness to lend against a token whose reported price nobody had verified could actually be sold.
The distinction matters for how the industry assigns blame. Cronos validators halted block production on Aug. 30 after the attack, in which the attacker pushed TONIC's price roughly 100 times higher within about 20 minutes and then supplied the inflated tokens as collateral to borrow assets with real liquidity. An independent researcher estimated about $75 million was affected, with the attacker's position of roughly 364.6 trillion TONIC requiring a reported value around $375 million to support the borrowing.
An oracle can be right and useless at once
"The oracle wasn't wrong. It accurately reported the price of TONIC on the pool it was reading from at that moment," Kazmierczak told crypto.news. A thinly traded token can register an enormous spot price after very few trades, even when the market lacks enough buyers to absorb large sales at that level. The oracle's job is to observe the available market price; the lending protocol's job is to decide whether that price is safe to lend against. "Reporting a price and validating that a price is safe to lend against are two different jobs, and Tectonic's design conflated them."
Tectonic reportedly allowed TONIC as collateral with a 20% collateral factor — meaning users could borrow up to one-fifth of a collateral position's reported value. With the manipulated price inflating the position's apparent worth roughly a hundredfold, the factor became irrelevant. Cronos ultimately rolled back its chain state to before the exploit, erasing the attack from the ledger's history — an emergency measure that reopened the industry's immutability debate on its own.
The fix: borrow caps tied to executable liquidity
Among the safeguards lending protocols can deploy, Kazmierczak argued that borrow caps linked to executable liquidity provide the strongest protection — limiting total borrowing against an asset by how much collateral could realistically be sold without collapsing its price. "Even if TONIC's reported price moves 100x, a borrow cap sized to what could realistically be exited without collapsing the market limits the damage regardless of what the price feed says."
Dynamic collateral factors, price-impact limits and minimum market-depth requirements could also have reduced exposure. He pushed back on treating longer time-weighted average price windows as a cure-all: a TWAP smooths brief spikes, but windows must be set to each asset's liquidity profile. "A move like TONIC's, 100x in 20 minutes, isn't a volatility event a wider TWAP window would smooth over. It's a signal the asset shouldn't have been usable as collateral at any meaningful size in the first place."
A familiar pattern of thin collateral attacks
The Tectonic exploit follows a well-worn playbook. Mango Markets lost more than $100 million in October 2022 after Avraham Eisenberg inflated positions tied to the thinly traded MNGO token and borrowed against them — a case that also exposed how hard applying traditional fraud law to automated lending systems can be. A Manhattan jury convicted Eisenberg in 2024, but a federal judge vacated the convictions in May 2025 over venue problems and insufficient evidence on the wire fraud count. In August, an $8.7 million exploit on Moonwell used the same pattern: the attacker manipulated the illiquid MAMO token's collateral value on Base before borrowing cbBTC, after which Moonwell cut its borrow caps to 1 wei while investigating.
Kazmierczak placed primary responsibility on risk curators and service providers who set and maintain collateral parameters — noting that governance voters may approve a listing without the market-structure knowledge to judge liquidity risk. Protocols face a structural temptation: listing a native governance token as collateral boosts its usage and attracts deposits, and the cost of weak settings stays hidden until someone tests the market's response to a manipulated price. More detail on RedStone's own infrastructure is available at redstone.finance.
For lenders, the lesson of the Tectonic exploit is uncomfortable but simple: exploits rarely require broken infrastructure — they require parameters nobody stress-tested. Oracle providers can report the market accurately and still watch a protocol lend a hundred million dollars against a price that only ever existed for twenty minutes.
