Fact-check findings
What an automated fact-checker found when it re-read Odin.Fun against the sources the page cites. Only the most recent review is shown.
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.
unverifiable
1 claimNo source the reviewer could reach confirms or contradicts the claim.
- #8[unverifiable][awaiting moderator]in the cited sources
“https://web.archive.org/web/20260725134700/https://coincentral.com/okx-announces-historic-65-million-okb-token-burn-price-jumps-170/”
reviewerCoinCentral source for timeline entry on August 13.The stored archive_url points to an unrelated OKB token burn article, not the Odin.fun article. I did not locate a correct snapshot, so no correction is proposed.
partially supported
2 claimsThe cited evidence supports part of the claim but not all of it.
- #3[partially supported][awaiting moderator]in section: Platform overview
“Odin.Fun launched in January 2025 as Bitcoin's first meme coin launchpad modeled on Solana's Pump.fun.”
reviewerOdin.Fun launched in January 2025.January was the private beta; public launch was about February 2025. Page omits this nuance. - #6[partially supported][awaiting moderator]in the summary
“as of late August 2025 trading remained halted with no committed reopening date or compensation plan.”
reviewerAs of late August 2025 trading remained halted with no committed reopening date or compensation plan.Supported through August 19 only, and the page is stale: it is now October 2026 and the page has no later status. One search snippet mentions a partial compensation plan, which I could not verify.
confirmed
5 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in section: Exploit: August 2025 AMM liquidity manipulation (58.2 BTC, ~$7 million)
“Platform BTC reserves fell from 291 BTC to about 232.8 BTC in under two hours.”
reviewerThe August 2025 exploit drained 58.2 BTC (~$7M); reserves fell from 291 BTC to about 232.8 BTC in under two hours.CoinDesk confirms the amounts and reserve figures. It does not mention August 12; the date range rests on other sources (Rekt dates the breach to August 12). - #2[confirmed][no action needed]in section: Security practices and audit failures
“In an August 19, 2025 update it said it was working with undisclosed partners to achieve 1:1 backing of user deposits before reopening”
reviewerAs of August 19, 2025 the team said it was working with undisclosed partners for 1:1 backing, some funds were frozen at CEXs, and it could not commit to a timeline.Supported. Cryptopolitan presents the US law enforcement and Binance/OKX details as a later separate post, not the August 19 update, so the timeline[8] framing of dates is loose but acceptable. - #4[confirmed][no action needed]in section: Platform overview
“On March 14, 2025, Taproot Wizards, the Bitcoin Ordinals project co-founded by Udi Wertheimer, led a strategic investment round in Odin.Fun; the amount and terms were not disclosed.”
reviewerBy March 2025: $30M volume, ~20,000 users, nearly 4,000 tokens; Taproot Wizards led a round on March 14, 2025, terms undisclosed.Confirmed; article is reported March 14 rather than stating the investment date explicitly. - #5[confirmed][no action needed]in section: Earlier incident: March 2025 deposit synchronization anomaly
“On March 7, 2025, community members reported 74 BTC disappearing from Odin.Fun's apparent on-chain records.”
reviewerMarch 7, 2025: 74 BTC disappeared from records due to a deposit synchronization bug, not theft.Rekt says 'user balances' versus the page's 'on-chain records'; minor wording difference. - #7[confirmed][no action needed]in section: Security practices and audit failures
“Halborn saw 'no sign that the code was audited before release'”
reviewerThe AMM code was deployed without prior audit (Halborn: 'no sign that the code was audited before release').Consistent with search results quoting Halborn; I did not fetch the full page.