Skip to main content
AVOID.NET
← Blockstream Liquid Networkreviewed 2026-10-30 · 9 claims checked

Fact-check findings

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

partially supported 3confirmed 60 corrections pending · 0 applied

partially supported

3 claims

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

  1. #4[partially supported][awaiting moderator]in section: The September 6, 2026 exploit: scope and mechanism
    “At 14:06 UTC, SideSwap requested a peg-out of roughly 3,996 BTC, and at 14:28 UTC the federation's multisignature wallet — reportedly requiring 11-of-15 valid functionary signatures — paid out a transaction of about 4,019 BTC, the bulk of which was forwarded to the attacker's address.”
    reviewerMint at 13:53 UTC block 4,050,336; peg-out request 14:06; payout 14:28; 11-of-15Times and mechanism match; the 4,019 BTC figure and 'bulk forwarded' phrasing differ from Bitquery, where nearly the whole 3,996 BTC was forwarded. Not verified against Protos.
  2. #7[partially supported][awaiting moderator]in section: Role of SideSwap and the federation's response
    “According to The Block and TRM Labs, Liquid block production resumed around September 10, 2026, but peg-outs remained disabled as a precaution pending further security review and resolution of the reserve shortfall.”
    reviewerBlock production resumed around Sept 10 with peg-outs disabled; attributed to The Block and TRM LabsFact is supported by other outlets, but TRM (published Sept 8) cannot be the source for a Sept 10 resumption. The Block article not fetched.
  3. #9[partially supported][awaiting moderator]in section: Blockstream's refusal to pay a ransom
    “As of the most recent reporting identified in this research (mid-to-late September 2026), no arrests, seizures, or recovery of the remaining funds had been publicly reported.”
    reviewerAs of the most recent reporting (mid-to-late September), no arrests or recovery reportedConsistent with what I found, but the page's cutoff is earlier than available Oct 11 reporting that peg-outs remain frozen at ~86% backing; the page's later claim that October searches found no change is consistent.

confirmed

6 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in the timeline
    “2018-09-27”
    reviewerLiquid blockchain went live September 27, 2018Matches the press release.
  2. #2[confirmed][no action needed]in section: Background: Liquid Network and the Liquid Federation
    “The network launched with 23 member exchanges and firms including Bitfinex, BitMEX, Bitso, Korbit, OKCoin, Xapo and others.”
    reviewerLaunched with 23 member exchanges and firms including Bitfinex, BitMEX, Bitso, Korbit, OKCoin, XapoConfirmed.
  3. #3[confirmed][no action needed]in section: The September 6, 2026 exploit: scope and mechanism
    “Multiple outlets, including TRM Labs and The Block, reported the stolen value at approximately $319-320 million, which several described as the largest crypto hack to that point in 2026.”
    reviewerExploit on Sept 6, 2026 of about $319 million (~4,000 BTC), largest 2026 hack to that pointTRM confirms amount, date and ranking.
  4. #5[confirmed][no action needed]in section: Partial return of funds and disputed "white hat" claim
    “the attacker returned approximately 3,400 BTC to the federation's peg wallet on September 7, 2026, while retaining roughly 598.5 BTC (reported at approximately $47 million)”
    reviewerAttacker returned ~3,400 BTC on Sept 7 and kept ~598.5 BTC (~$47M)Confirmed by two sources.
  5. #6[confirmed][no action needed]in section: Disputed technical root cause: range-proof caching vs. dynafed validation
    “Bitquery identified a partial fix merged on September 2, 2026 and backported September 3, with a further hardening fix on September 8 and the release of Elements 23.3.4 on September 9.”
    reviewerElements fixes dates and 23.3.4 release Sept 9Matches Bitquery.
  6. #8[confirmed][no action needed]in section: Ongoing reserve shortfall and network status
    “TRM Labs estimated the federation's identified reserve address held about 3,597 BTC against roughly 4,200 L-BTC in circulation, implying approximately 86% backing”
    reviewerTRM estimated ~3,597 BTC reserve vs ~4,200 L-BTC, ~86% backingConfirmed including the estimate caveat.
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.