Check the Liquid Reserve Yourself

Every L-BTC in circulation is currently backed by roughly 0.047 Bitcoin held in the Liquid Federation’s reserve. Measured directly on September 7, 2026 at 12:39 UTC against the network’s two public endpoints: 197.47190204 BTC in reserve stand against 4,205.01883617 L-BTC issued. That works out to 4.70 percent backing and a shortfall of 4,007.55 Bitcoin, or roughly $319 million (274 million euros) at the CoinGecko price recorded in the same minute.

You do not have to take anyone’s word for this figure. The Liquid Network publishes its reserve and its circulating supply through an open interface, each request takes seconds, and the division is simple arithmetic. How that works, what the number says about your holdings and what it explicitly does not say is set out below. We wrote up the incident itself separately on September 7: Liquid Network hack: $320 million in Bitcoin walked out. What follows is the check you can run yourself.

How Much Bitcoin Backs L-BTC Right Now? The Reserve in a Single Number

The Liquid Federation holds the Bitcoin that back the issued L-BTC in a jointly managed multisignature address. Before September 6, that balance stood above 4,200 BTC roughly level with the circulating supply. After the peg-out on the afternoon of September 6, the endpoint still reports 197.47190204 BTC, last updated at Bitcoin block 965,928

The circulating supply, by contrast, is unchanged. The peg endpoint reports 4,205.01883617 L-BTC as of Liquid block 4,050,335. Together the two figures give the backing ratio, and it is the one metric that counts immediately for a holder:

• Reserve: 197.47190204 BTC
• Circulating supply: 4,205.01883617 L-BTC
• Backing: 4.70 percent
• Shortfall: 4,007.55 BTC

A backing ratio is the share of posted collateral against the amount issued. For a redeemable Bitcoin token the target reading is 100 percent, because every unit issued is meant to be covered by exactly one Bitcoin in custody. On that logic, a reading of 4.70 percent means this: if every holder wanted to redeem today, the balance would stretch to just under five in a hundred.

What Is the Liquid Network, and What Do You Hold When You Hold L-BTC?

The Liquid Network is a sidechain of Bitcoin. A sidechain is a blockchain of its own, connected to a main chain by a bridge, with the main chain’s units represented on it. Liquid was built for fast settlement between exchanges and trading houses: block time is one minute, amounts and asset types are confidential by default, and further issued assets run there alongside L-BTC.

The network is operated by the Liquid Federation, a group of member companies that signs the blocks and jointly controls the Bitcoin in custody. According to several trade publications, a payout requires eleven of fifteen signatures. Blockstream developed the software and provides part of the infrastructure.

Anyone holding L-BTC is not holding Bitcoin on the Bitcoin blockchain. They hold a claim on Bitcoin that a federation redeems. Before September 6 that distinction was a footnote in explainers. Since September 6 it has been the heart of the matter.

Peg-In and Peg-Out: How Bitcoin Reaches the Sidechain and Comes Back

A peg-in is the way in: you send Bitcoin to an address controlled by the federation, and the same amount of L-BTC is created on Liquid. A peg-out is the way out: your L-BTC are destroyed on the sidechain, and the federation pays you the corresponding amount in Bitcoin out of the reserve.

The whole procedure rests on one assumption: that only as many L-BTC exist on Liquid as there were Bitcoin paid in beforehand. That is exactly the point at which it failed on September 6. On Blockstream’s account, reproduced by several trade publications, the L-BTC in the order concerned came into being through a flaw in the Elements software that Liquid is built on. As far as the network was concerned they were valid, without any Bitcoin ever having been paid in for them.

Checking L-BTC Backing: Two Endpoints, One Division

The check needs no tooling and no access rights. Both endpoints are public and answer with a single-line figure in satoshi, the smallest Bitcoin unit. One hundred million satoshi make one Bitcoin.

1. Fetch the reserve. Open liquid.network/api/v1/liquid/reserves. The amount field gives the amount in custody in satoshi, and lastBlockUpdate gives the Bitcoin block the reading refers to.
2. Fetch the circulating supply. The second path is /api/v1/liquid/pegs and returns the amount of L-BTC issued in the same format, together with the Liquid block as a time reference.
3. Divide. Reserve divided by circulating supply, times one hundred. On September 7, 2026 at 12:39 UTC that came to 4.70 percent.

The request has one advantage over any reporting, this piece included: it is current to the minute. When the announced return arrives, you will see it at this endpoint before any outlet writes about it. A proof of reserves you can recalculate yourself is what separates a promise from evidence. We set the principle out at length in how to check proof of reserves yourself, and the current case is the textbook illustration.

How Do I Verify a Bitcoin Transaction? The Peg-Out in Block 965,783

The payout in question sits in plain view on the Bitcoin blockchain. The identifier is 8db751a6…b140, confirmed in block 965,783, block time September 6, 2026, 14:28:56 UTC. The transaction pulls together 83 inputs and pays out a combined 4,019.44391988 BTC across thirteen outputs. These values come from our own request to the public Blockstream interface on September 7, not from a media report.

You verify a transaction in three steps: enter the identifier in a block explorer, read the confirmation status and the block height, then compare the sum of the outputs with what was reported. If the sum differs, you have a finding. If it matches, you have checked the report at its

How Do I Verify Wallet Addresses? Where the Bitcoin Sit Today

Several reports circulate the address that received the first payout. That first address is empty by now. Within the same block 965,783, 3,996.01834922 BTC moved on to bc1ql4mfu6aundtkksxklfajs2h3t9nzcd6gyqjlte. At the time of my measurement on September 7 at 12:39 UTC it held 3,998.49939856 BTC across one hundred counted transactions, with one open entry in the mempool, the queue of unconfirmed transactions.

You check an address the same way: address into the explorer, read off the balance, then place the transaction count and the mempool status beside it. What matters is the difference between an unchanged balance and an unchanged address. The balance can stay level while small amounts move in and out in the background. Anyone writing that the funds are sitting untouched should say which of the two addresses they mean.

Hold your Bitcoin yourself instead of leaving it on a bridge

What Blockstream, the Federation and SideSwap Have Officially Said

Attribution matters more here than sharpening the point, so what follows is only what the parties themselves have said, and in whose name.

The Liquid Federation said that alleged white-hat hackers had withdrawn around 4,000 Bitcoin, that the bridge nodes had been shut down and the sidechain halted, and that other issued assets were not affected. In the operator’s wording, the sidechain is paused until the matter is cleared up

SideSwap, whose peg-out service processed the order, stated publicly that a customer had sent 4,000 L-BTC to the service at 14:05 UTC; that the service had handled the order like any other; that the L-BTC had been destroyed on Liquid with valid peg-out authorization; and that at 14:28 UTC the federation had paid out 3,996 Bitcoin. On Liquid’s account, SideSwap’s authorization key was not compromised, and neither were any other keys. The cause lies in the Elements software.

Some restraint is called for on the “white hat” label. The term comes from a message left on-chain by the other side itself, which several trade publications reproduce. According to consistent reports, Blockstream answered by the same route, with PGP signatures attached to Bitcoin transactions. Whether the intention really was a return will be settled at the reserve and nowhere else.

Why the Promised Return Has Not Restored the Backing Yet

On September 7 Blockstream reported that the bridge nodes had been patched and secured, leaving nothing in the way of returning the roughly 4,000 Bitcoin. That is a solid piece of news, and a welcome one. It does not establish backing yet.

My measurement at 12:39 UTC on September 7 shows the reserve unchanged at 197.47190204 BTC, while the receiving address still holds around 3,998 Bitcoin. Exactly one transaction separates an announced return from a completed one, and at the time of writing it was still outstanding. Anyone who wants to see it happen calls the reserve endpoint: if the figure there climbs toward 4,200, it has happened. If it stays at 197, it has not.

What the Incident Means for Your L-BTC Balance on a Crypto Exchange

L-BTC holders currently fall into two groups, and their options differ considerably.

Anyone holding L-BTC in a Liquid wallet of their own keeps control of the key but cannot move the balance back across the bridge at the moment: peg-outs are suspended. The sidechain itself keeps producing blocks, so transfers within Liquid are running. Anyone holding L-BTC on an exchange is blocked from deposits and withdrawals of that asset, because the venues halted transfers after the federation’s appeal. For the choice of trading venue and its custody practice we keep a separate hardware wallet comparison, because in weeks like this one the question of who holds the key is the only one that counts.

Three things make sense in both cases at present: call the reserve endpoint once a day, follow the official channels of the federation and of your own exchange, and start no new peg-ins while the bridge is paused. SideSwap has explicitly asked users to send neither peg-in nor peg-out deposits until the services return.

Which Assets on Liquid the Peg-Out Incident Did Not Touch

Further issued assets run on Liquid alongside L-BTC, among them Tether’s USDT stablecoin, the Brazilian DePix and tokenized real-world assets. According to the federation, as reproduced consistently by Bitcoin Magazine and Cryptobriefing, these assets are unaffected by the incident: the vulnerability concerned the peg-out mechanism for L-BTC.

That is more than a footnote. A USDT holder on Liquid reads headlines these days about a halted sidechain and may draw the wrong conclusion from them. The chain produces blocks, transfers within the network work, and a stablecoin issued on Liquid hangs on the backing of its own issuer rather than on the federation’s Bitcoin reserve.

Peg Discount: What Can Happen When Payouts Reopen

As long as peg-outs are suspended, there is no free price for the way back. If the bridge reopens while the missing Bitcoin are still absent from the reserve, a race begins: the claim to a payout would then be redeemable for some holders and beyond reach for the rest. In such a situation a backed token typically trades below the value of the underlying asset, because the market prices in the probability of redemption. Cryptobriefing has explicitly flagged this risk of a peg discount.

That is a possibility and no forecast. If the promised Bitcoin come back before payouts reopen, the question never arises. Which is exactly why the order in which the two things happen is more interesting for holders than any price analysis: reserve first, bridge afterwards.

What This Case Teaches You About Every Bridge and Every Sidechain

The case is specific; the pattern is not. Every bridge between two networks creates a claim on the destination chain that hangs on the security of a custodian. A flaw in the destination chain’s software can conjure that claim out of nothing, and the custodian notices only when a payout falls due. The shutdown of the Silicon Network was the orderly version of the same problem: balances on a bridge stay reachable only as long as somebody operates the bridge.

In practice that means three questions before any bridged balance. Who holds the collateral, and is the amount publicly retrievable? How many signatures does a payout take, and who holds them? And how do I get back out if the operator halts the bridge? For most bridges there is no good answer to the third question, which is an argument for keeping bridged balances small and time-limited.

Which crypto exchanges publish a proof of reserves

What the 4.70 Percent Figure Does Not Tell You

A backing ratio measures a balance. It says nothing about intent and nothing about the future. The 4.70 percent tell you nothing about whether the Bitcoin will come back, when the federation will reopen the bridge, or at what rate holders are paid out in the end. They say nothing about the cause either: whether the Elements flaw persists cannot be read off the reserve endpoint, and the operator’s statements are what count there.

What the figure does deliver is still a good deal. The request gives you a reading that nobody interprets on your behalf, it is current to the minute, and it is verifiable without your having to trust a report, this one included. Anyone wondering over the coming days whether something has moved has a better answer from this single request than from any headline.

Frequently Asked Questions About L-BTC Backing

Is my L-BTC worthless now?

No, that cannot be concluded from the backing ratio. L-BTC remains a claim against the federation, and the operators have held out the prospect of returning the funds. What can be said is this: the reserve currently covers a small part of the circulating supply, and how a claim gets served in the end is open.

Can I withdraw my L-BTC now?

Peg-outs are suspended, as are L-BTC deposits and withdrawals at the exchanges that followed the appeal. Transfers within the Liquid network continue, because the chain produces blocks.

Are my Bitcoin in my own wallet affected?

Bitcoin on the Bitcoin blockchain are untouched by the event. What is affected is the reserve that stands against the L-BTC issued on the sidechain. Anyone who never made a peg-in holds no L-BTC.

How will I know the Bitcoin are back?

From the figure at the reserve endpoint. If it rises clearly above the current 197 BTC, a repayment has arrived. A second indication is the balance of the receiving address, which would have to fall accordingly.

Checking L-BTC Backing: What to Take Away

1. Recalculate the backing yourself before you adopt anyone’s assessment. Two requests, one division, thirty seconds. If you hold balances spread across trading venues, the same critical look at their proof of reserves pays off; which houses publish one at all is set out in our crypto exchange comparison.
2. Separate claim from ownership. A bridged token is a claim against an operator; a Bitcoin under your own key is ownership. Anyone wanting to reflect that difference in their portfolio will find the tools for it in the software wallet comparison.
3. Keep bridged balances small and the rest in your own custody. The incident hit nobody who held their Bitcoin on the main chain and under their own key. Which device is up to the job is covered in the hardware wallet comparison.

(As of September 7, 2026. This article is not investment advice. Prices and fee structures change; check the terms with the provider before you buy.)

Transparency note: This article was produced with the assistance of artificial intelligence and reviewed by our editorial team before publication. All figures and claims were checked against the primaryI

More from CryptoTicker

Source: cryptoticker.io