Skip to main content
AVOID.NET
← BitcoinDepotreviewed 2026-10-28 · 6 claims checked

Fact-check findings

What an automated fact-checker found when it re-read BitcoinDepot 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 1partially supported 2confirmed 30 corrections pending · 0 applied

unverifiable

1 claim

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

  1. #2[unverifiable][awaiting moderator]in section: Fraud Facilitation Allegations
    “alleged in a February 2026 lawsuit that more than 80% of the company's largest Massachusetts customers (those who spent $10,000 or more between August 2023 and January 2025) had been victims of scams, generating roughly $10.6 million in revenue”
    reviewerMassachusetts AG alleged more than 80% of largest customers were scam victims, generating roughly $10.6 million, nearly 60% of MA kiosk revenuePrimary source blocked. ICIJ is consistent in spirit but does not contain the specific 80%, $10.6M and 60% figures; not scored against the page.

partially supported

2 claims

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

  1. #3[partially supported][awaiting moderator]in section: State and Federal Regulatory Actions
    “Washington State's Department of Financial Institutions filed a Statement of Charges dated June 11, 2026 against Bitcoin Depot Operating, LLC”
    reviewerWashington DFI charges: Statement of Charges dated June 11, 2026, individual named, $1.5M fine, up to 42% markup, 30,000+ transactionsFigures confirmed. The release date is June 11; the charging document's own date and the named individual were not independently confirmed from the page text.
  2. #5[partially supported][awaiting moderator]in the timeline
    “https://www.sec.gov/Archives/edgar/data/0001901799/000119312526219660/btm-20260512.htm”
    reviewerNasdaq suspended trading on May 26, 2026 (timeline entry cites a May 12, 2026 8-K)The suspension date is right, but the cited filing cannot support it. Search found no primary Nasdaq/SEC URL I fetched, so no replacement is proposed.

confirmed

3 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in section: Chapter 11 Bankruptcy and Kiosk Shutdown
    “Bitcoin Depot and sixteen affiliates filed voluntary Chapter 11 petitions in the U.S. Bankruptcy Court for the Southern District of Texas”
    reviewerBitcoin Depot and sixteen affiliates filed Chapter 11 petitions in S.D. Texas on May 17, 20268-K confirms date, court and affiliate count. Press dating of May 18 is correctly flagged on the page.
  2. #4[confirmed][no action needed]in section: Chapter 11 Bankruptcy and Kiosk Shutdown
    “CEO Alex Holmes attributed the filing to an "unsustainable" state regulatory environment”
    reviewerCEO Holmes attributed the filing to an 'unsustainable' state regulatory environmentSupported by Decrypt (not the 8-K, which lacks the quote). Vinson & Elkins and Portage Point were not found in Decrypt; not checked elsewhere.
  3. #6[confirmed][no action needed]in the timeline
    “Tennessee's statewide ban on crypto ATMs takes effect, following a similar ban in Indiana.”
    reviewerTimeline lists Tennessee ban and Chapter 11 out of chronological orderNot independently fetched; page's own section text gives July 1, 2026. Noted only: the July 2026 entry sits before May and June 2026 entries, an ordering issue, not a factual error.
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.