David is a finance journalist and a contributor to Cryptonews.com with a keen interest in breaking comprehensive, accurate, and reliable blockchain news.
Cyvers Alerts flagged a suspected Truebit incident on January 8, after its monitoring detected a suspicious transaction with an estimated loss of $26 million. TRU’s on-chain pricing printed a -99.95% one-day move on at least one token tracker, a level that typically indicates DEX liquidity collapse or a broken price feed rather than orderly selling pressure.
Onchain Details
The label “Truebit Protocol: Purchase” maps to 0x764C64b2A09b09Acb100B80d8c505Aa6a0302EF2 on Ethereum, which Etherscan tags as a Truebit contract address. Cyvers’ estimate centers on 8,535 ETH (about $26M at ~$3.1k/ETH), and the open question for desks is whether that ETH represents treasury funds, a mispriced “purchase” path, or a compromised hot wallet connected to Truebit’s TRU sales flow referenced in project docs (“All sales transact in ETH”).
CoinGecko data showed TRU trading at $0.1611 (+4.1% in 24h) before crashing to $0.00007923.
Truebit lists the TRU token contract at 0xf65B5C5104c4faFD4b709d9D60a185eAE063276c, which matters because confusion between “Truebit (TRU)” and “TrueFi (TRU)” has repeatedly polluted execution and risk systems on desks that rely on symbol-only mappings.
Trading Desk Read
For a desk, the tradable signal is not “TRU down 99.95%”. The signal is that a labeled purchase contract (a flow that can touch treasury ETH, fee rails, or sale mechanics) sits at the center of a suspected 8,535 ETH loss, which increases counterparty risk for any venue still quoting TRU and raises operational risk for any strategy that keys off ticker symbols alone (TRU has a long history of symbol collision with TrueFi).
Expect market makers to widen or pull quotes until the actual drain path (treasury vs. user flow vs. labeling error) gets pinned to a specific transaction trail and a Truebit-controlled signer set.
