← Truebitreviewed 2026-11-02 · 12 claims checked
Fact-check findings
What an automated fact-checker found when it re-read Truebit against the sources the page cites. Only the most recent review is shown.
Read this first
These findings are produced by an automated reviewer, and its results vary between runs: the same page, checked three times on the same day, came back with 15%, 20% and 34% of its claims disputed, mostly because each run extracted a different number of claims. Treat what follows as leads, not rulings.
“Disputed” means the reviewer could not reconcile the claim with the evidence it cited. It does not mean the claim is false. “Unverifiable” means no reachable source settled it either way.
Nothing here changes the page on its own. A proposed correction is applied only after a human moderator approves it; until then the page reads as it did when reviewed.
disputed
5 claimsThe reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.
- #3[disputed][awaiting moderator]in section: Security History
“deployed an attack contract at 0x764C64b2A09b09Acb100B80d8c505Aa6a0302EF2”
reviewerThe attack contract is at 0x764C...2EF2The page labels the victim contract as the attacker's attack contract. Two independent write-ups agree on the correct address.Proposed correction (not yet applied)deployed an attack contract at 0x1De399967B206e446B4E9AeEb3Cb0A0991bF11b8 - #4[disputed][awaiting moderator]in section: Security History
“The contract was compiled with Solidity 0.6.10”
reviewerThe vulnerable contract was compiled with Solidity 0.6.10 (Security History)Two independent analyses give 0.5.3, not 0.6.10. The cited SlowMist article could not be fetched, so the correction rests on those two. The point that no default overflow checks existed still holds.Proposed correction (not yet applied)The contract was compiled with Solidity 0.5.3 - #5[disputed][awaiting moderator]in section: Protocol Mechanics
“compiled with Solidity 0.6.10, a version”
reviewerTruebit's contracts were compiled with Solidity 0.6.10 (Protocol Mechanics)Same Solidity version error as in Security History.Proposed correction (not yet applied)compiled with Solidity 0.5.3, a version - #6[disputed][awaiting moderator]in the timeline
“(compiled with Solidity 0.6.10)”
reviewerPurchase contract compiled with Solidity 0.6.10 (timeline 2021)Same Solidity version error. The 2021 deployment year is consistent with 'about five years ago'.Proposed correction (not yet applied)(compiled with Solidity 0.5.3) - #7[disputed][awaiting moderator]in the timeline
“2025-09”
reviewerTruebit Verify general availability was announced in September 2025The primary announcement is dated 2025-11-18. The 2025-09 date is not supported.Proposed correction (not yet applied)2025-11
unverifiable
2 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #8[unverifiable][awaiting moderator]in section: Security History
“The attacker also employed MEV (Maximal Extractable Value) techniques, paying priority bribes to ensure their transactions were processed ahead of any potential interference.”
reviewerAttacker paid MEV priority bribesNeither reachable analysis mentions attacker MEV bribes. The SlowMist source was blocked, so it may come from there. - #11[unverifiable][awaiting moderator]in section: Background
“It was co-founded by Jason Teutsch, a mathematician who holds a PhD from Indiana University, and Christian Reitwiessner, the creator of Solidity”
reviewerFounders and background: Teutsch and Reitwiessner co-founded Truebit; whitepaper 2017; ACM CCS Test-of-Time awardI did not fetch the background sources in this pass. These claims are widely known and plausible, but I did not verify them here, so I make no verdict.
partially supported
3 claimsThe cited evidence supports part of the claim but not all of it.
- #9[partially supported][awaiting moderator]in section: Security History
“Security analysts at PeckShield linked the attacker's wallet to the earlier Sparkle Protocol hack, in which a similar exploit — minting tokens at artificially reduced cost via contract flaw — was used, suggesting an experienced threat actor.”
reviewerPeckShield linked attacker to Sparkle Protocol hack involving a similar token-minting exploitThe link is supported. The Sparkle loss was only about 5 ETH, and no source I read says the method was similar minting. 'Experienced threat actor' is inference. - #10[partially supported][awaiting moderator]in section: Security History
“Truebit stated it contacted law enforcement and halted interactions with the affected contract”
reviewerTruebit contacted law enforcement and has not released a full post-mortemLaw enforcement contact is confirmed. 'Halted interactions' slightly overstates a user advisory not to interact. - #12[partially supported][awaiting moderator]in section: Risk Assessment
“No compensation mechanism for affected users has been publicly announced.”
reviewerPage states no compensation plan, no recovery and no post-mortem as of May 2026Latest explicit statement I found is from January 15, 2026. I found nothing later, so the claim is unconfirmed beyond that date, and the page's May 2026 framing is now six months old.
confirmed
2 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in the summary
“On January 8, 2026, an integer overflow vulnerability in a five-year-old, closed-source legacy Purchase contract was exploited, draining 8,535 ETH (approximately $26.44 million) and causing the TRU token to collapse by over 99.9%”
reviewerExploit on Jan 8, 2026 drained 8,535 ETH (~$26.44M) and TRU fell 99.9%Core facts hold. Dollar value differs slightly across outlets, which is normal price-timing variance. - #2[confirmed][no action needed]in the summary
“the attacker subsequently laundered all stolen funds through Tornado Cash”
reviewerAttacker laundered all stolen funds through Tornado CashConsistent across Rekt and search coverage.
How this fits together. The reviewer reads the published page and its cited sources and records one finding per claim. A human moderator decides whether each proposed correction is applied; those decisions, and the score changes they cause, appear in the audit log. Earlier review runs are not shown here; only the latest reflects the page as it stands.