The Liquid Network, a Bitcoin sidechain designed for fast trading between exchanges, saw its L-BTC token backing collapse to just 4.7% on September 6, 2026, after roughly 4,000 Bitcoin were withdrawn due to a flaw in the underlying Elements software. Only 197.47 Bitcoin now back 4,205 L-BTC in circulation, leaving a shortfall of approximately 4,007.55 Bitcoin, or roughly $319 million at the time of measurement.

Unlike traditional finance, where you might trust a bank's published reserve figures, the Liquid Network publishes its reserve data and circulating supply through public application programming interfaces (APIs), meaning anyone can verify the backing ratio themselves in seconds. This transparency, while revealing the problem, also allows holders and observers to confirm the situation without relying on media reports or official statements alone.

What Is L-BTC and Why Does the Backing Ratio Matter?

L-BTC is a representation of Bitcoin on the Liquid Network, a sidechain, which is a separate blockchain connected to Bitcoin through a bridge. When you send Bitcoin to the Liquid Federation, a group of member companies that jointly controls the Bitcoin reserves, you receive an equivalent amount of L-BTC on the sidechain. The network was built to enable fast settlement and confidential transactions between trading houses and exchanges, with block times of just one minute compared to Bitcoin's ten-minute average.

The backing ratio is the percentage of Bitcoin held in reserve relative to the total L-BTC issued. For a redeemable Bitcoin token, the target is 100%, meaning every L-BTC should be covered by exactly one Bitcoin in custody. At 4.7%, if every L-BTC holder tried to redeem their tokens for Bitcoin today, the federation's reserve would cover only about five out of every hundred redemption requests.

How Did the Backing Ratio Collapse So Dramatically?

According to Blockstream, the company that developed Liquid's software, the L-BTC involved in the withdrawal came into being through a flaw in the Elements software that Liquid is built on. The network treated the tokens as valid without any Bitcoin ever having been paid in to back them. On September 6 at 14:05 UTC, a customer sent 4,000 L-BTC to SideSwap, a peg-out service that converts L-BTC back into Bitcoin. SideSwap processed the order like any other, destroying the L-BTC on Liquid and triggering the federation to pay out 3,996 Bitcoin at 14:28 UTC.

The Liquid Federation stated that alleged white-hat hackers had withdrawn around 4,000 Bitcoin and that the bridge nodes had been shut down, pausing the sidechain until the matter could be cleared up. SideSwap confirmed that the customer's peg-out authorization was valid and that neither its authorization key nor any other federation keys were compromised. The root cause, according to the federation's account, lies in the Elements software itself.

How to Verify L-BTC Backing: Steps to Check the Reserves Yourself

• Fetch the Reserve: Open the public endpoint at liquid.network/api/v1/liquid/reserves in your browser. The "amount" field shows the Bitcoin held in custody measured in satoshi, the smallest Bitcoin unit, with 100 million satoshi equaling one Bitcoin. The "lastBlockUpdate" field indicates which Bitcoin block the reading refers to.
• Fetch the Circulating Supply: Use the second endpoint at /api/v1/liquid/pegs to retrieve the total L-BTC issued in satoshi, along with the Liquid block as a time reference for when the data was recorded.
• Calculate the Backing Ratio: Divide the reserve amount by the circulating supply, then multiply by 100 to get the percentage. On September 7, 2026 at 12:39 UTC, this calculation yielded 4.70%, a figure anyone can recalculate in seconds using the live endpoints.

The advantage of checking these endpoints yourself is that the data updates to the minute, faster than any news outlet can report. When the announced return of funds arrives, you will see it reflected in the reserve endpoint before any article is published about it. This represents a proof of reserves you can verify independently, separating a promise from evidence.

Can You Verify the Bitcoin Transaction on the Blockchain?

The payout itself is visible on the Bitcoin blockchain for anyone to inspect. The transaction identifier is 8db751a6...b140, confirmed in block 965,783 on September 6, 2026 at 14:28:56 UTC. The transaction combined 83 inputs and paid out 4,019.44 Bitcoin across thirteen outputs. You can verify this transaction in three steps: enter the identifier into a block explorer, check the confirmation status and block height, then compare the sum of the outputs with what has been reported. If the sum matches, you have confirmed the report at its source rather than at second hand.

The first address that received the payout is now empty. Within the same block, 3,996.02 Bitcoin moved to address bc1ql4mfu6aundtkksxklfajs2h3t9nzcd6gyqjlte, which held 3,998.50 Bitcoin across one hundred transactions as of September 7 at 12:39 UTC, with one open entry in the mempool, the queue of unconfirmed transactions waiting to be included in the next block.

What Does This Mean for L-BTC Holders?

The collapse in backing ratio creates immediate risk for anyone holding L-BTC. Before September 6, the backing ratio stood above 100%, roughly level with the circulating supply. Now, with only 4.7% backing, the token is severely undercollateralized. The Liquid Federation has paused the sidechain, meaning new peg-ins and peg-outs are not currently possible, effectively freezing L-BTC holders' ability to convert their tokens back into Bitcoin until the situation is resolved.

The incident underscores a critical distinction: holding L-BTC is not the same as holding Bitcoin on the Bitcoin blockchain. L-BTC holders hold a claim on Bitcoin that the Liquid Federation redeems. Before September 6, this distinction was largely a technical footnote in explainers. Since the software flaw and withdrawal, it has become the central issue for anyone evaluating the risks of using sidechains or federated bridges.

The transparency of Liquid's public endpoints means the problem is not hidden; it is measurable and verifiable by anyone with internet access. This openness contrasts sharply with traditional finance, where reserve verification often requires trust in auditors and regulatory oversight. However, it also means that the shortfall is immediately visible to the market, creating pressure on the federation to restore the backing ratio and rebuild confidence in the L-BTC token.