Liquid Network Stories Do Not Share a Loss Figure

Two accounts published on 1 October 2026 say the Liquid Network was exploited in September and that a large share of the bitcoin was later returned. They do not agree on a single loss figure, so this article does not pick one. Liquid Network L-BTC is the asset at the center of that disagreement. The incident is not the NEAR Intents case and not the Bitget case. It is a September event on this network, with a return that both write-ups acknowledge and a number they do not share.

What happened

The Liquid Network is a separate transaction network associated with bitcoin. L-BTC is the asset that moves on it. In ordinary operation, L-BTC is meant to stand in for bitcoin, so that a holder can move value on Liquid and later convert back. That conversion is the peg. The peg is the claim that L-BTC and bitcoin can be exchanged because bitcoin is there to meet the L-BTC. An exploit is a break in that machinery, not a move in the bitcoin price and not a routine redemption.

Both stories agree on three points and stop. The exploit was in September. A large share of the bitcoin was later returned. The write-ups do not settle on one loss figure. Because they do not settle, repeating any candidate number would choose a side the sources have not reconciled. This article will not state a dollar loss, a coin count, or a percentage beyond "a large share." Those candidates exist in the coverage. They are not a shared fact.

One account says unbacked L-BTC was created and pegged out to bitcoin. Unbacked, in that telling, means L-BTC was issued without the bitcoin that is supposed to sit behind it. Pegged out means that unbacked asset was converted into bitcoin, so the hole showed up as bitcoin leaving rather than only as a token misprinted on Liquid. This article attributes that sequence to one account. It does not treat the sequence as confirmed by both, and it does not describe a technical mechanism, such as a proof inside the software, that only one outlet discussed. A mechanism one newsroom alone explains is not a finding here.

The return is the other shared fact, and it is easy to misread. "A large share" of the bitcoin came back. A large share is not all of it, and it is not a named fraction. Returned does not, in these pages, identify who sent it, whether the return was voluntary, or whether anyone was charged. It means the bitcoin that left was not all still gone when the 1 October stories were written. Readers who need a recovered percentage will not find one both outlets will stand behind.

Why it matters

A pegged asset is a promise that the stand-in can be turned back into the original. L-BTC is that stand-in for bitcoin on the Liquid Network. If unbacked units can be created and then pegged out, on even one credible account, the promise failed in a specific way: new claims were minted, and bitcoin left to meet them. Holders who did nothing but hold a pegged asset can find that the bitcoin side of the peg is thinner. That is why the form of the loss matters more than a single dramatic total. The form is disputed in its details and plain in its outline.

Disagreement on the figure is itself the news, once the outline is shared. Two serious write-ups of the same September exploit, both willing to say a large share came back, still cannot be cited for one loss number. Publishing a number anyway would look more precise than the record. The record supports "the accounts differ," not a midpoint invented for neatness.

The return changes the loss without closing it. A large share coming back means the net harm is smaller than the gross amount that moved in September. How much smaller is the argument. It also means "exploited" and "made whole" are different sentences. Both outlets support the first plus a large return. Neither, in the shared record, supports a sentence that everyone was repaid in full.

This is not a roundup item to be blended with other named failures. The NEAR Intents incident is a different event. The Bitget incident is a different event. Mentioning them is only a guard against mixing files. Nothing in this article describes how those other events worked, what they cost, or who was responsible. Liquid Network L-BTC is the subject because both 1 October stories discuss it, and because their disagreement is concentrated there.

What's next

What both stories already support will not be improved by waiting for a third number to split the difference. September, an exploit, a large share of bitcoin later returned, and no agreed loss figure: that is the record as of the 1 October write-ups. A later notice from the network, a court filing, or a figure both outlets adopt would replace the gap. It is not in these pages.

The one-account sequence, unbacked L-BTC created and pegged out to bitcoin, stands as that account until the other write-up or the network confirms the path in terms this article can use. Confirmation would be new. So would a contradiction. Until either arrives, the sequence is attributed, not adopted as the only mechanics.

Anyone citing a dollar total or a coin count for this incident is choosing among the figures this piece declined. Those choices should be labeled as one outlet's figure, not as a reconciled loss. The same caution applies to market-wide hack totals in the two roundups. They are not a Liquid figure. Cointelegraph's account is here. The FinanceFeeds account is here.