← Compounder Financereviewed 2026-11-02 · 13 claims checked
Fact-check findings
What an automated fact-checker found when it re-read Compounder Finance 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
1 claimThe reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.
- #11[disputed][awaiting moderator]in the timeline
“Solidity Finance publicly acknowledges it should have been clearer about the implications of developer-controlled admin keys and commits to more robust future disclosures.”
reviewerTimeline: Solidity commits to more robust future disclosuresThe acknowledgement is supported; the commitment clause is not in the fetched source.Proposed correction (not yet applied)Solidity Finance publicly acknowledges it should have been clearer about the implications of developer-controlled admin keys.
unverifiable
3 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #7[unverifiable][awaiting moderator]in section: Funds Stolen
“Funds were reportedly routed through Tornado.cash to obscure the trail.”
reviewerFunds routed through Tornado.cashNot in CoinDesk; I did not check the Quadriga page. - #10[unverifiable][awaiting moderator]in section: Aftermath and Industry Impact
“Solidity Finance publicly committed to providing more robust disclosures about developer control risks in future audits.”
reviewerSolidity Finance publicly committed to more robust disclosures in future auditsDecrypt reports an admission, not a commitment to future disclosures. The same overreach appears in the timeline. - #13[unverifiable][awaiting moderator]in section: Aftermath and Industry Impact
“No funds have been publicly reported as recovered, no perpetrators have been identified, and no law enforcement action has been reported as of publicly available records through 2025.”
reviewerNo law enforcement action or recovery through 2025Negative claim; my search found nothing contradicting it.
partially supported
4 claimsThe cited evidence supports part of the claim but not all of it.
- #2[partially supported][awaiting moderator]in section: Overview
“The contract was deployed on November 8 or 9, 2020, according to Etherscan records”
reviewerContract deployed Nov 8 or 9, 2020 per EtherscanCoinDesk gives Nov 10; I did not fetch Etherscan to confirm the on-chain creation date. Sources conflict, so the page's hedged range may be inaccurate. - #3[partially supported][awaiting moderator]in the timeline
“2020-11-08”
reviewerContract deployed 2020-11-08 (timeline)Timeline commits to Nov 8 while the section hedges 8 or 9 and CoinDesk says Nov 10. Timeline entry has no source. - #5[partially supported][awaiting moderator]in section: Overview
“Compound Finance founder Robert Leshner publicly noted the impersonation.”
reviewerLeshner publicly noted the impersonationLeshner comment exists, but my extract did not show the impersonation statement or a confirmation of non-affiliation. - #6[partially supported][awaiting moderator]in section: The Rug Pull Mechanism
“the developer-controlled address called inCaseStrategyTokenGetStuck() on the StrategyController”
reviewerDev address called inCaseStrategyTokenGetStuck across seven malicious strategiesCoinDesk does not mention the function name or seven strategies; search results suggest another source (Rekt) does. The cited sources do not carry the detail.
confirmed
5 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in the summary
“stealing between $10.8 million and $12.5 million from investors”
reviewerStolen amount ranged from $10.8M to $12.5MBoth figures appear in the fetched sources. - #4[confirmed][no action needed]in section: Overview
“the rug pull was executed on or around December 1, 2020”
reviewerRug pull executed on or about Dec 1, 2020Matches CoinDesk. - #8[confirmed][no action needed]in section: Funds Stolen
“The exploit address associated with the drain is reported as 0x079667f4f7a0b440ad35ebd780efd216751f0758.”
reviewerExploit address and CP3R price dropAddress, itemization and the 98.8% / $0.24 drop match CoinDesk. - #9[confirmed][no action needed]in section: Audit and Pre-Incident Warning Signs
“However, the audit firm later acknowledged it 'should have been clearer about the implications' of that centralized control.”
reviewerAudit released Nov 19; auditor admitted it should have been clearer; no one monitored timelockDecrypt supports this. The year of the Nov 19 audit is not stated in the article, but it is consistent. - #12[confirmed][no action needed]in section: Audit and Pre-Incident Warning Signs
“Solidity Finance received death threats within 36 hours of the theft becoming public and declined to elaborate further.”
reviewerDeath threats within 36 hoursSupported.
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.