EVM network halts block production after supply exploit as TON connection remains dark
What happened
Validators on TAC — an EVM network linked to TON — hit the big red pause button on block production after the team announced a supply-related vulnerability on the Cosmos-based EVM side of the chain. The project said the issue was limited to the TAC token supply, and validators coordinated a temporary halt that took effect quickly.
Public chain data showed activity frozen at block 24,671,475 (timestamped 23:58:11 UTC on Aug. 22). That same block still appeared as the latest on the explorer about 8 a.m. UTC on Aug. 24, indicating the chain stayed stopped for more than a day while the team investigated.
Background: the earlier bridge incident
This isn’t the first time TAC has had to scramble. Back in May, a bridge-related breach stemmed from sequencer software that failed to verify a token wallet properly. That allowed counterfeit deposit messages to be accepted, unbacked tokens to be minted on TAC, and real assets on TON to be incorrectly released. TAC later estimated the May protocol loss at roughly $2.85 million and temporarily halted the sequencer linking TAC to TON, while the EVM layer itself kept running at the time.
What’s still unclear (and why that’s a headache)
The recent halt raises more questions than it answers. TAC’s initial notices didn’t spell out how many tokens were created, which transaction or block triggered the issue, which wallets — if any — lost funds, or when normal operation might resume. There was also no explanation for why the problem couldn’t be isolated below the full-chain level, which is the kind of detail people need to reconcile balances across native, wrapped, bridged, staked, exchange-held, or protocol-controlled TAC holdings.
Because the team hasn’t published technical specifics or a reconciled supply number, the reasonable takeaway for now is simple and a little boring: block production is paused; TAC says this concerns token supply; and the conditions for restarting the chain haven’t been revealed. Whether this supply incident is tied to the May bridge breach — or is a completely different gremlin in the codebase — remains unknown until a thorough post-mortem is released.
For anyone watching from the sidelines, the smart move is to wait for the technical report and verified supply reconciliation before assuming wallets or balances are safe or fully understood. In the meantime, validators appear to be treating the situation like a high-stakes game of tug-of-war with the canonical state — and nobody wants to be the person who lets go too early.
