Liquid May Have Released About 3,996 BTC After Node Dispute

Liquid may have released approximately 3,996 BTC after federation nodes reportedly disagreed on transactions, a claim tied to a security incident the network acknowledged on September 6, 2026. The exact figure, sequence, and cause remain unverified pending on-chain and technical confirmation.

Liquid may have released approximately 3,996 BTC

The core claim is narrow: Liquid may have released approximately 3,996 BTC, a figure reported by SideSwap and relayed through CryptoSlate, which said a customer submitted 4,000 L-BTC on September 6 and the federation paid out that amount. No transaction hash, inputs, outputs, or fee reconciliation has been independently read. For related coverage, see Liquid Network Releases 3,996 BTC After L-BTC Burn.

Liquid Network itself has not confirmed the exact 3,996 figure. In its public statement, the project described a broader, rounded number: purported white-hat hackers withdrew about 4,000 BTC, valued near $320 million, from the Liquid Federation wallet. That figure is the withdrawal others have reported in similar terms. For related coverage, see AINext Awards & Conference Dubai 2026: Where AI Leaders, Innovators and Decision-Makers Shape the Future of Artificial Intelligence.

Federation-wallet withdrawal reported by Liquid

~4,000 BTC

What the headline claims about the BTC release

The available context does not establish what “released” means here or who received any bitcoin. It could describe a valid peg-out, an unauthorized drain, or a disputed edge case. The framing that nearly 4,000 BTC left through a peg-out and the framing of a hack are both circulating, and neither is settled by the evidence in hand.

The reported disagreement among federation nodes

The headline places a disagreement among federation nodes over transactions before the possible release. That sequence comes from secondary technical reporting, not from node logs or operator statements that have been independently verified.

According to unconfirmed reports attributed to the researcher Mononaut and relayed by CryptoSlate, federation functionaries ran Elements code absent from tagged releases, accepted invalid transactions, and kept producing blocks while other nodes rejected them. CryptoSlate expressly states Blockstream has not confirmed this deployment account.

What remains unknown about the transaction disagreement

The affected transactions, the specific participating nodes, and the timing all remain unverified. A separate unconfirmed account attributed to Stu points to an invalid transaction at Liquid block 4,050,336 creating roughly 3,996 L-BTC, but no block or transaction record has been independently fetched.

Why the sequence does not establish the cause

“After” in the headline is chronology, not causation. A node disagreement preceding a release does not prove the disagreement produced it. A range-proof validation-cache key collision has been floated as the mechanism in unconfirmed accounts attributed to Calle and Charles Guillemet, but no official postmortem or reproducer exists. Federation signing rules and any mechanism linking disagreement to a release require sourced technical evidence before they can be described as fact.

What needs verification about the possible BTC release

The embedded evidence contains no corroborating record of a specific release, a named recipient, user impact, or a resolution. The headline alone does not establish unauthorized movement or a financial loss.

Liquid’s own statement said the Blockstream team was working to contact the holders on-chain with a signed message, the status at the time of that post only. Blockstream has separately been reported to have patched the affected bridge nodes, though current operational status is not established by the fetched evidence.

The project stated the position directly in its September 6 post, which serves as the primary source for the incident’s existence.

We are aware of a security incident on @Liquid_BTC. Purported white-hat hackers have withdrawn ~4,000 BTC (~$320 million) from the Liquid Federation wallet. The @Blockstream team is working on contacting them on-chain with a signed message.

What we know so far is that the funds…

— Liquid Network 🌊 (@Liquid_BTC) September 6, 2026

Source: @Liquid_BTC on X

Evidence needed to confirm the amount and impact

Confirmation requires transaction records, relevant federation logs, and an attributable operator explanation, ideally traced to a Bitcoin block explorer showing the hash, addresses, and timestamp. The amount, timing, destination, authorization, and current status each need verification before being presented as fact. Reporting that self-described whitehats are holding the funds pending patches is secondary and unverified; no OP_RETURN message was read.

Market context does not resolve any of this. Bitcoin traded at $79,561 at the time of the research snapshot, down 0.4% on the day, while the broader Fear & Greed Index read 71, or Greed. Neither figure is incident-specific, and user losses, service disruption, and recovery remain open questions.

Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risk. Always do your own research before making decisions.