TAC's chain halt points at shared Cosmos EVM code, which is the part that matters

A chain halt is the crudest mitigation available, and TAC got it off quickly: per the team, the freeze landed within minutes of the exploit being spotted, and only the native token moved before block production stopped at 24,671,475 ^[3][1]. That speed is the good news and also the shape of the problem. The answer to a bug in the precompile layer was not a patch, it was a validator set agreeing to stop ^[2]. Operators who cannot reach that agreement inside a few minutes do not have that answer available to them.

The consequential act here was the attribution. By stating publicly that the defect sits in a shared Cosmos EVM module and that several other chains run the same code ^[4], TAC told an unknown number of teams they are running a live bug, and told everyone else the same thing at the same moment. As reported, the disclosure carries no maintainer confirmation, no named module version, no list of affected chains and no patch date, only the observation that a fix or disclosure timeline would reach other Cosmos EVM projects too ^[5][6]. It is a single-sourced diagnosis from the party with the strongest incentive to place the fault outside its own repository. That does not make it wrong. It does mean nobody downstream can check it yet.

The token arithmetic is worth doing because it puts the rebound in proportion. Roughly $8.3m of market cap on about 4.8bn circulating tokens works out to some $0.0017 each ^[15]. At the August 22 low of $0.001129, that same supply was worth around $5.4m ^[16], so the 53% recovery amounts to about $2.9m of notional ^[17]. Apply the June 30 peak of $0.06688 to today's supply and the implied cap was near $321m ^[18], which is what a 97.4% drawdown looks like in dollars ^[9]. Meanwhile $2.46m of volume against that cap is close to 30% turnover in a day ^[19], and the quoted range of $0.001626 to $0.001894 spans 16.5% ^[20]. That is a thin book being worked over rather than a re-rating.

The pattern matters more than the print. May's theft took about $2.8m from the TON side of the bridge and hit USDT, BLUM and tsTON balances, meaning user assets rather than the native supply ^[11]. It was settled by recovering roughly 90% of the funds, letting the exploiter keep 10% as a bounty, reclassifying the episode as white-hat and reopening transfers on June 10 ^[12]. An 82% drop followed on July 7 with no explanation offered ^[13]. This is the third serious incident in four months ^[14], and the first one TAC has located outside its own perimeter.

Which is why the interesting exposure is not an $8m token that has already been repriced twice. It is the count of chains running the same precompile, and whether their operators learn about it from a module maintainer or from a victim's X account ^[2].