← ETHTrustFundreviewed 2026-11-02 · 14 claims checked
Fact-check findings
What an automated fact-checker found when it re-read ETHTrustFund 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.
- #3[disputed][awaiting moderator]in the timeline
“Developer executed rug pull in two transactions: first transferring ~3.2 million BRETT tokens (~$453,000), then ~477 ETH (~$1.65 million) approximately 9.5 hours later.”
reviewerTimeline: the rug pull on 2024-07-20 included the 477 ETH transfer 9.5 hours after the firstEntry is dated 2024-07-20 and implies both transfers that day; Rekt says the second was on July 21. Other outlets say only that the rug pull began July 20. Low-severity.Proposed correction (not yet applied)Developer executed rug pull in two transactions: first transferring ~3.2 million BRETT tokens (~$453,000) on July 20, then ~477 ETH (~$1.65 million) approximately 9.5 hours later, on July 21.
unverifiable
2 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #10[unverifiable][awaiting moderator]in the summary
“ZachXBT has flagged this entity as a fraudulent project.”
reviewerZachXBT has flagged ETHTrustFund as fraudulentNo source found for a ZachXBT flag. The page's own section admits it is unverified, yet the summary states it flatly. - #13[unverifiable][awaiting moderator]in section: Project Overview
“The $ETF token went live on Uniswap V3 on March 14, 2024.”
reviewerToken launched on Uniswap V3 on March 14, 2024March 2024 launch is supported; the exact date and DEX were not verified. BaseScan and CMC were not fetched.
partially supported
7 claimsThe cited evidence supports part of the claim but not all of it.
- #1[partially supported][awaiting moderator]in the summary
“On July 20, 2024, the pseudonymous lead developer known only as 'Peng' drained approximately 607 ETH (worth ~$2.1–2.2 million) from the project treasury”
reviewerTotal theft was 607 ETH worth about $2.1-2.2 million, drained by Peng on July 20, 2024Total and start date are supported, but Rekt says the thefts spanned July 20 and 21, so a single-day framing is imprecise. - #2[partially supported][awaiting moderator]in section: Rug Pull — July 2024
“On July 20, 2024, the ETHTrustFund lead developer”
reviewerBoth thefts (BRETT and 477 ETH) occurred on July 20, 9.5 hours apartRekt places the 477 ETH transfer on July 21. The BRETT amount (3.2M, ~$453k), 477 ETH (~$1.65M) and the 9.5-hour gap are confirmed. Only the date of the second transfer conflicts. - #5[partially supported][awaiting moderator]in section: Rug Pull — July 2024
“The incident was first publicly disclosed by crypto community researcher Octoshi on July 21, 2024, and further reported by Ogle of glue.net, who filed a report with ChainAbuse.”
reviewerOctoshi first disclosed on July 21, 2024; Ogle of glue.net filed a ChainAbuse reportRoles are confirmed. The July 21 date and the 'first' priority for Octoshi are not stated in the sources I read. - #6[partially supported][awaiting moderator]in section: Fund Laundering via Tornado Cash and Railgun
“200 ETH was sent to Railgun at approximately 13:27 UTC; two separate transfers of 200 ETH each were routed through Tornado Cash; and an additional 56.9 ETH was transferred back to Railgun.”
reviewerLaundering split: 200 ETH to Railgun, 2x200 ETH to Tornado Cash, 56.9 ETH back to Railgun, per PeckShieldFlows match, but sources read give 456.9 ETH total versus 607 ETH, and the sources describe 200 ETH to Tornado Cash in two transactions (reading ambiguous). The page does not note the unreconciled gap. - #7[partially supported][awaiting moderator]in section: Fund Laundering via Tornado Cash and Railgun
“PeckShield confirmed the laundering activity via an alert posted on July 22, 2024.”
reviewerPeckShield posted an alert on July 22, 2024 confirming the launderingPeckShield involvement confirmed; the exact alert date is inferred from the article date. - #8[partially supported][awaiting moderator]in section: Pre-Exit Warning Signs
“lead developer 'Peng' had become unresponsive on Telegram as early as April 2024 — roughly three months before the rug pull.”
reviewerPeng unresponsive on Telegram as early as April 2024Three months of silence is sourced; 'April' is an inference. 'Telegram' specifically is not confirmed. - #12[partially supported][awaiting moderator]in the summary
“The project's website, Twitter, and Telegram accounts were permanently deleted following the exit.”
reviewerWebsite, Twitter and Telegram were deletedDeletion confirmed. 'Permanently' is an overstatement, and documentation was reported still accessible.
confirmed
4 claimsThe cited evidence supports the claim as written.
- #4[confirmed][no action needed]in section: Rug Pull — July 2024
“The deployer wallet identified on-chain is 0xF259F01C40C211D63Ab75A6d2B108B364EFaB780, the treasury address is 0xbfDB66a6783a6Dc757f539139c68BED75EB491c8, and the attacker's destination wallet is 0x374f4BD39aD211e67e0f8Cb8Ebf1b4F6Ac3059aD.”
reviewerDeployer, treasury and attacker addressesMatches Rekt exactly. - #9[confirmed][no action needed]in section: Pre-Exit Warning Signs
“The $ETF token had previously experienced a sharp price decline of approximately 90% within one week of its March 2024 launch”
reviewerToken fell ~90% within one week of launchMatches Rekt. - #11[confirmed][no action needed]in section: ZachXBT Flag
“The underlying rug pull incident itself has been confirmed by multiple Tier 1 and Tier 2 sources independent of any ZachXBT flag.”
reviewerSection asserts the underlying rug pull is confirmed by multiple Tier 1 and Tier 2 sourcesIncident corroborated by Rekt, crypto.news, Web3 Is Going Great, Cointelegraph and Forklog. - #14[confirmed][no action needed]in section: Developer Anonymity and Accountability
“No law enforcement action, regulatory filing, or legal proceeding has been publicly reported against any individual in connection with this theft as of the time of this investigation.”
reviewerNo law enforcement action reportedNo action found in my searches.
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.