Skip to main content
AVOID.NET
← BTC24Hreviewed 2026-10-27 · 7 claims checked

Fact-check findings

What an automated fact-checker found when it re-read BTC24H 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.

unverifiable 3partially supported 2confirmed 20 corrections pending · 0 applied

unverifiable

3 claims

No source the reviewer could reach confirms or contradicts the claim.

  1. #2[unverifiable][awaiting moderator]in the timeline
    “Quadriga Initiative publishes case study formally documenting the BTC24H claim system contract missing eligibility check, classifying the loss at approximately $86,000.”
    reviewerQuadriga Initiative published the case study on 2025-01-27The fetched case study does not state a publication date. Jan 27 is the date of the linked source items, so the page's date may be inferred. Timeline entries also carry empty source fields.
  2. #6[unverifiable][awaiting moderator]in section: ZachXBT Flag and Community Signals
    “BTC24H has been flagged by on-chain investigator ZachXBT, whose Investigations Telegram channel (t.me/investigations) serves as a primary early-warning resource for the crypto community.”
    reviewerZachXBT has flagged BTC24HThe page itself admits it found no post linking ZachXBT to BTC24H, yet it opens with a flat assertion that BTC24H 'has been flagged'. This is unsupported, and it names a real individual. The section heading and the same assertion should be hedged or removed. I did not find a source either way.
  3. #7[unverifiable][awaiting moderator]in section: Project Overview
    “with reported fully diluted valuation of approximately $2.12M at creation but only $129 in actual pool liquidity”
    reviewerToken is a 21M supply ERC-20 with 99%/1% allocation; Uniswap pool FDV $2.12M versus $129 liquidityI did not fetch GeckoTerminal, CoinMarketCap DEX or PolygonScan, which are dynamic pages. The archive records show the GeckoTerminal archive failed. Not scored.

partially supported

2 claims

The cited evidence supports part of the claim but not all of it.

  1. #3[partially supported][awaiting moderator]in the timeline
    “BTC24H Lock contract on Polygon exploited via missing eligibility check in the 'claim' function; estimated loss of $85,700.”
    reviewerExploit occurred December 16 (timeline) and was reported by TenArmor, 0xCommitAudits, IncentiveFiMechanism, loss, tx hash and reporters match. The exact day (Dec 16-17) is not stated in the case study and I could not read PolygonScan to check it. The SlowMist 'Weekly Security Report' on Dec 17 was not independently checked.
  2. #5[partially supported][awaiting moderator]in section: High-Yield Investment Program Characteristics
    “The Quadriga Initiative case study notes the platform has 'no apparent social media presence or active project communication.'”
    reviewerProject has no social media or public communicationThe substance is right, but the text is placed in quotation marks and is not the source's wording. The paraphrase should not be presented as a quote.

confirmed

2 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in section: Smart Contract Exploit — December 2024
    “The estimated loss from this vulnerability was approximately $85,700 USD.”
    reviewerEstimated loss from the Lock contract exploit was approximately $85,700Quadriga case study gives approximately $85,700 (headline rounded to $86,000).
  2. #4[confirmed][no action needed]in section: Domain and Operator Risk Assessment
    “The domain bitcoin24h.net received a trust score of 0 out of 100 from Scamadviser, flagged for recent registration (November 2024), identity concealment via a privacy proxy service, server hosting in Vietnam, co-hosting with other flagged sites, and a Gridinsoft malware warning.”
    reviewerDomain bitcoin24h.net scored 0/100 on Scamadviser, registered Nov 2024, privacy proxy, Vietnam hosting, Gridinsoft warningAll elements match. The Scamadviser score is a year old. The page's other claims on the other domains (bitcoin24h.org, scamvoid, scam-detector) were not checked.
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.