Fact-check findings
What an automated fact-checker found when it re-read Liquid Network / Elements Cache-Bug Exploit (September 2026) 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.
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.
- #9[disputed][awaiting moderator]in section: Scale of Loss and Reserve Depletion
“After roughly 3,400 BTC was returned on September 7, CryptoTimes and other outlets reported the network paused operations, and TRM Labs noted that, based on an identified reserve address holding about 3,597 BTC against an estimated 4,200 L-BTC outstanding, the implied backing ratio stood at roughly 86% — a figure TRM cautioned was not a full reserve reconciliation, since Blockstream had not at that time announced how any shortfall would be addressed.”
reviewerAfter roughly 3,400 BTC was returned on September 7, CryptoTimes and other outlets reported the network paused operations.The page implies the network paused as a consequence of the Sept 7 return of funds. Multiple contemporaneous reports (including The Block's own Sept 6 article) show Liquid halted transactions and disabled bridge nodes immediately upon detecting the Sept 6 theft -- before any funds were returned. The backing-ratio figure (86%) itself is independently confirmed.Proposed correction (not yet applied)The network paused operations immediately after the September 6 theft, as reported by CryptoTimes and other outlets, and TRM Labs noted that, based on an identified reserve address holding about 3,597 BTC against an estimated 4,200 L-BTC outstanding, the implied backing ratio stood at roughly 86% — a figure TRM cautioned was not a full reserve reconciliation, since Blockstream had not at that time announced how any shortfall would be addressed.
partially supported
1 claimThe cited evidence supports part of the claim but not all of it.
- #20[partially supported][awaiting moderator]in section: Network Response, Patch, and Resumption
“Later reporting referenced in secondary sources indicated the network entered what was described as the 'final stages of recovery' more than a month after the incident, though independent confirmation of full peg-out resumption was not found in the sources reviewed for this page.”
reviewerLater reporting referenced in secondary sources indicated the network entered what was described as the 'final stages of recovery' more than a month after the incident.The phrase is a real quote from Liquid, so it is not fabricated, but the page's hedge does not convey that, as of the most recent reporting found (Oct 11, 2026), peg-outs had not partially resumed in any way -- they remained fully frozen with no announced date. This is marked partially_supported rather than confirmed because the framing risks understating how incomplete recovery still was.
confirmed
28 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in the summary
“On September 6, 2026, an attacker exploited a caching flaw in Elements, the open-source software underlying Blockstream's Liquid Network Bitcoin sidechain, to mint roughly 4,000 unbacked L-BTC and peg it out to native bitcoin worth approximately $319 million, draining about 95% of the federation's reserve wallet.”
reviewerOn September 6, 2026, an attacker exploited a caching flaw in Elements to mint roughly 4,000 unbacked L-BTC and peg it out to native bitcoin worth approximately $319 million, draining about 95% of the federation's reserve wallet.Figures and date independently confirmed by both TRM Labs and CoinTelegraph. - #2[confirmed][no action needed]in the summary
“The attacker, claiming to be a "white hat," returned about 3,400 BTC after Blockstream patched the bug but kept roughly 598.5 BTC (about $47 million) as a self-declared bounty; Blockstream publicly refused to pay a ransom for the remainder.”
reviewerThe attacker, claiming to be a 'white hat,' returned about 3,400 BTC after Blockstream patched the bug but kept roughly 598.5 BTC (about $47 million) as a self-declared bounty.Matches The Block's reporting precisely. - #3[confirmed][no action needed]in the summary
“The incident, the largest crypto theft reported in 2026 to that point, renewed scrutiny of Liquid's federated trust model, cost, and adoption levels.”
reviewerThe incident was the largest crypto theft reported in 2026 to that point.Properly hedged with 'to that point'; confirmed by TRM Labs. - #4[confirmed][no action needed]in section: The Exploit: Technical Root Cause
“An earlier fix (referenced as commit c26d719 in third-party analysis) attempted to bind the cache key to the full validation context — the rangeproof, value commitment, asset generator, and script — but did so by hashing the raw, variable-length fields together into a single SHA-256 stream without encoding field lengths or boundaries.”
reviewerThe vulnerability was a cache-key collision in Elements' rangeproof verification cache, caused by a prior fix (commit c26d719) that hashed variable-length fields together without encoding lengths/boundaries, allowing field-tuple rearrangement to produce an identical cache key.Technical description matches CertiK's analysis closely. - #5[confirmed][no action needed]in section: The Exploit: Technical Root Cause
“CertiK's analysis notes that the exact binaries running on individual federation functionary nodes were not published, so attribution of the specific flawed commit is an inference rather than a confirmed fact.”
reviewerCertiK's analysis notes that the exact binaries running on individual federation functionary nodes were not published, so attribution of the specific flawed commit is an inference rather than a confirmed fact.Page correctly preserves CertiK's own epistemic hedge rather than overstating certainty. - #6[confirmed][no action needed]in section: The Exploit: Technical Root Cause
“The attacker then pegged this out to native bitcoin via SideSwap, a Liquid Federation member that holds a peg-out authorization key.”
reviewerThe attacker pegged the unbacked L-BTC out to native bitcoin via SideSwap, a Liquid Federation member that holds a peg-out authorization key.Confirmed by two of the three sources cited in this section (TRM, The Block); the third (CertiK) is silent on SideSwap but does not contradict it. - #7[confirmed][no action needed]in section: The Exploit: Technical Root Cause
“Liquid's own September 8 incident update similarly described the issue as a caching flaw in rangeproof verification and said no federation signing keys were compromised.”
reviewerLiquid's own September 8 incident update described the issue as a caching flaw in rangeproof verification and said no federation signing keys were compromised.Confirmed. - #8[confirmed][no action needed]in section: Scale of Loss and Reserve Depletion
“TRM Labs characterized this as the largest crypto theft recorded in 2026 up to that point, ahead of incidents at KelpDAO (~$292 million) and Drift (~$285 million) earlier in the year, and noted total 2026 crypto theft losses of approximately $1.73 billion across 333 incidents.”
reviewerOn September 6, 2026, approximately 4,000 BTC (~$319 million) was withdrawn from Liquid's federation reserve wallet, about 95% of its ~4,200 BTC balance; ahead of KelpDAO (~$292 million) and Drift (~$285 million), with total 2026 crypto theft losses of approximately $1.73 billion across 333 incidents.Confirmed verbatim against TRM's post. - #10[confirmed][no action needed]in section: Scale of Loss and Reserve Depletion
“the implied backing ratio stood at roughly 86% — a figure TRM cautioned was not a full reserve reconciliation, since Blockstream had not at that time announced how any shortfall would be addressed”
reviewerThe implied backing ratio stood at roughly 86%, based on an identified reserve address holding about 3,597 BTC against an estimated 4,200 L-BTC outstanding.Independently corroborated by a second outlet. - #11[confirmed][no action needed]in section: Attackers' Self-Declared 'White Hat' Claim and Ransom Demand
“The attacker embedded the message "we are whitehats. contact us on chain" in an OP_RETURN field and subsequently communicated with Blockstream via encrypted on-chain messaging, according to CertiK's analysis and reporting from The Block.”
reviewerThe attacker embedded the message 'we are whitehats. contact us on chain' in an OP_RETURN field.Confirmed via independent on-chain analysis (Bitquery), consistent with the page's cited sources. - #12[confirmed][no action needed]in section: Attackers' Self-Declared 'White Hat' Claim and Ransom Demand
“However, in a message dated Wednesday, September 9, 2026 and sent via OP_RETURN, the attacker demanded a 10% 'bug bounty' for the remaining funds, arguing that Blockstream had spent comparatively little — characterized as '$1.5 million, maybe even 0' — to secure roughly $5 billion in assets.”
reviewerIn a message dated Wednesday, September 9, 2026, the attacker demanded a 10% 'bug bounty,' characterizing Blockstream's security spend as '$1.5 million, maybe even 0' to secure roughly $5 billion in assets.Confirmed, including the weekday/date cross-check. - #13[confirmed][no action needed]in section: Attackers' Self-Declared 'White Hat' Claim and Ransom Demand
“The legitimacy of the 'white hat' framing has been publicly disputed; Ledger CTO Charles Guillemet was quoted stating that if the arrangement amounted to a negotiated reward under an encrypted on-chain contract, it looked 'more like extortion than white-hat hacking.'”
reviewerLedger CTO Charles Guillemet was quoted stating that the arrangement looked 'more like extortion than white-hat hacking.'Confirmed; attribution and quote verified at the cited source. - #14[confirmed][no action needed]in section: Attackers' Self-Declared 'White Hat' Claim and Ransom Demand
“TRM Labs noted it had labeled the attacker's wallet addresses within a day of the incident and continued tracking the roughly 598.5 BTC retained by the attacker.”
reviewerTRM Labs labeled the attacker's wallet addresses within a day of the incident and continued tracking the roughly 598.5 BTC retained by the attacker.Confirmed. - #15[confirmed][no action needed]in section: Blockstream's Refusal to Pay and Ongoing Recovery Efforts
“On Friday, September 11, 2026, Blockstream publicly told the exploiter to 'return the bitcoin' and stated it would not pay a bounty for the remaining approximately 598.5 BTC, according to The Block. Blockstream characterized the taking and withholding of the assets as theft rather than responsible disclosure, and said it would not set a precedent of open-source developers paying ransoms disproportionate to their economic participation.”
reviewerOn Friday, September 11, 2026, Blockstream publicly told the exploiter to 'return the bitcoin' and stated it would not pay a bounty for the remaining ~598.5 BTC, characterizing the withholding as theft rather than responsible disclosure.Confirmed; Sept 11, 2026 independently verified as a Friday. - #16[confirmed][no action needed]in section: Blockstream's Refusal to Pay and Ongoing Recovery Efforts
“The company stated that if the funds were not returned, it would work with law enforcement, exchanges, and forensic specialists to trace the assets and identify those responsible.”
reviewerBlockstream said that if the funds were not returned, it would work with law enforcement, exchanges, and forensic specialists to trace the assets and identify those responsible.Confirmed. - #17[confirmed][no action needed]in section: Blockstream's Refusal to Pay and Ongoing Recovery Efforts
“As of the most recent reporting reviewed, the roughly $47 million in retained funds had not been recovered, and TRM Labs continued tracking the associated wallet addresses.”
reviewerAs of the most recent reporting reviewed, the roughly $47 million in retained funds had not been recovered, and TRM Labs continued tracking the associated wallet addresses.Still true as of the most recent reporting this reviewer could find (Oct 11, 2026); appropriately hedged by the page. - #18[confirmed][no action needed]in section: Network Response, Patch, and Resumption
“Elements version 23.3.4, an emergency release hardening the cache-key scheme used for range proofs, was deployed on September 9, 2026.”
reviewerElements version 23.3.4, an emergency release hardening the cache-key scheme used for range proofs, was deployed on September 9, 2026.Confirmed. - #19[confirmed][no action needed]in section: Network Response, Patch, and Resumption
“Liquid resumed block production on September 10, 2026, initially 'without transactions' as a precaution while monitoring for full network stabilization; functionary and bridge nodes had been updated, and functionary nodes resumed signing and validating blocks.”
reviewerLiquid resumed block production on September 10, 2026, initially 'without transactions' as a precaution; peg operations including PAK-authorized peg-outs remained suspended.Confirmed; weekday (Thursday) independently cross-checked. - #21[confirmed][no action needed]in section: Structural and Governance Criticism
“Protos reported that Liquid is governed by a federation of roughly 15 functionaries who must jointly authorize movement of pegged bitcoin via an 11-of-15 multisig, meaning L-BTC's value and redeemability depend on continued trust in those functionaries rather than on cryptographic guarantees alone”
reviewerLiquid is governed by a federation of roughly 15 functionaries who must jointly authorize movement of pegged bitcoin via an 11-of-15 multisig.Confirmed by two separate sources. - #22[confirmed][no action needed]in section: Structural and Governance Criticism
“critics quoted in the piece, including developer BenTheCarman, described Liquid as 'a fork of bitcoin with a few fancy things added' bundled with federated custody and Blockstream branding”
reviewerCritics quoted in the Protos piece, including developer BenTheCarman, described Liquid as 'a fork of bitcoin with a few fancy things added.'Confirmed. - #23[confirmed][no action needed]in section: Structural and Governance Criticism
“The same article reported low network usage — commentator Udi Wertheimer was quoted saying 'no one's using it,' with the piece noting that on a typical day there were more tweets about Liquid than transactions on its network — and noted Blockstream had raised approximately $210 million at a $4 billion valuation in 2021, partly to develop and monetize Liquid, spending the Protos piece characterized as likely wasted given low adoption and centralization concerns.”
reviewerUdi Wertheimer was quoted saying 'no one's using it,' with the piece noting that on a typical day there were more tweets about Liquid than transactions on its network, and noted Blockstream had raised approximately $210 million at a $4 billion valuation in 2021.All components of this compound claim confirmed. - #24[confirmed][no action needed]in section: Structural and Governance Criticism
“Separately, research comparing Liquid to competing Bitcoin layer-2 designs (published by Spark, a corporate competitor, and therefore a self-interested source) similarly described the 11-of-15 multisig federation structure and noted that users moving funds back to the Bitcoin mainchain require cooperation from at least 11 federation members, with no unilateral exit path for an individual user.”
reviewerResearch published by Spark, a corporate competitor, described the 11-of-15 multisig federation and noted that moving funds back to the mainchain requires cooperation from at least 11 federation members, with no unilateral exit path for an individual user.Confirmed, and the page appropriately flags the source's conflict of interest. - #25[confirmed][no action needed]in the timeline
“Attacker exploits a rangeproof verification caching flaw in Elements to mint roughly 4,000 unbacked L-BTC and peg it out to native bitcoin via SideSwap, draining about 95% of Liquid's federation reserve wallet (~$319 million).”
reviewerTimeline: Attacker exploits the caching flaw on 2026-09-06 to mint ~4,000 unbacked L-BTC and peg it out via SideSwap, draining ~95% of the reserve wallet (~$319 million).Confirmed. - #26[confirmed][no action needed]in the timeline
“Attacker returns approximately 3,400 BTC (about $270 million) to the federation wallet after Blockstream confirms affected bridge nodes have been patched; roughly 598.5 BTC remains unreturned.”
reviewerTimeline: Attacker returns ~3,400 BTC (~$270 million) on September 7, 2026 after Blockstream confirms patched bridge nodes; ~598.5 BTC remains unreturned.date_original (2026-09-07) and month-precision date (2026-09) both correctly derived. - #27[confirmed][no action needed]in the timeline
“Liquid publishes an incident update describing the rangeproof caching flaw in Elements and states no federation operator keys were compromised.”
reviewerTimeline: Liquid publishes an incident update on September 8, 2026 describing the rangeproof caching flaw and stating no federation operator keys were compromised.Confirmed. - #28[confirmed][no action needed]in the timeline
“Emergency patch Elements v23.3.4 is deployed, hardening the cache-key scheme used in rangeproof verification. Separately, the attacker demands a 10% 'bug bounty' for the remaining funds via an on-chain message.”
reviewerTimeline: Emergency patch Elements v23.3.4 is deployed on September 9, 2026, and the attacker demands a 10% 'bug bounty' via an on-chain message the same day.Confirmed. - #29[confirmed][no action needed]in the timeline
“Liquid Network resumes block production, initially without processing transactions, as functionary and bridge nodes complete required updates; peg-outs remain suspended.”
reviewerTimeline: Liquid Network resumes block production on September 10, 2026, initially without processing transactions; peg-outs remain suspended.Confirmed; note the entry's own date_evidence field ('Sept. 10: Liquid resumed block production and transactions') is internally inconsistent with this correct event text and with the cited article, but date_evidence is a provenance field outside this review's correction scope. - #30[confirmed][no action needed]in the timeline
“Blockstream publicly refuses to pay the attacker's ransom demand for the remaining approximately 598.5 BTC, calling it theft and stating it will pursue law enforcement and forensic tracing if funds are not returned.”
reviewerTimeline: On September 11, 2026 (a Friday), Blockstream publicly refuses to pay the attacker's ransom demand for the remaining ~598.5 BTC.Confirmed.