liquid

🚨BREAKING🚨

White-hat hackers have returned 3,400 BTC to Liquid Network after draining 4,000 BTC worth around $320 million in Sunday's exploit.

💰 Around 598 BTC, worth approximately $47 million, remains outstanding as Blockstream continues talks with the hackers.

⚠️ Liquid Network remains paused while operators implement security fixes, resolve a chain split, and ensure L-BTC is fully backed before restarting.

🔒 Exchanges were asked to freeze L-BTC deposits and withdrawals, while other Liquid assets, including USDT, were not affected.

$BTC

#BTC☀ #liquid

The Liquid sidechain has just gone through a significant trust test — a massive withdrawal of 4,000 BTC led to the emergency suspension of bridge functionality.

Many people's first reaction was, "Is the bridge broken? Will the assets be lost?" But the core of this event is actually more subtle: when the liquidity channel between a sidechain and the main chain is cut off, everything tied to the chain — whether settlement confirmations, exchange channels, or cross-chain liquidity — enters a kind of "trust freeze" state.

This is not a problem with $BTC the main chain, but a risk characteristic of the Layer 2 architecture itself: verifiability must rely on the availability of the bridging mechanism. Once the bridge becomes unavailable, the verification chain is broken.

For ecosystem participants, this serves as a reminder of a basic fact: in a layered architecture, the security of each layer cannot be assessed in isolation, and the availability of the bridge itself is part of security.

#Bitcoin #Liquid

Liquid suspension: For those holding LBTC, don’t look only at the BTC price

LBTC holders should first confirm the availability of transfers and BTC redemptions; do not treat the “white hat” claim as a signal that the alert can be lifted. What has been verified is an event involving the Liquid sidechain and its federated wallet, not evidence that the Bitcoin mainnet was compromised.

On September 6, Liquid announced that about 4,000 BTC had been withdrawn from the federated wallet, and the team is contacting the relevant parties; bridge nodes have been temporarily shut down, and exchanges have suspended or are preparing to suspend LBTC deposits and withdrawals. As of this verification, no confirmation of returned funds has been obtained.

LBTC represents BTC locked on the Bitcoin network, but it also adds a layer of federated custody and redemption mechanisms. Therefore, even if the BTC price is stable, that does not prove LBTC can be redeemed at any time. The official statement says that other assets on Liquid, such as USDT and DePix, were not affected by this security incident, but it also clearly states that wallet functions will be affected by the suspension: “assets not affected” does not mean “transfers are normal.”

Affected users should temporarily refrain from making new deposits to the Liquid chain, check the announcements of each platform they use one by one, and keep records of balances and transactions; do not enter seed phrases into any so-called “recovery/compensation” page.

Yesterday’s view still has not been confirmed by new trading-day data: “ETF inflows do not equal a breakout confirmation” remains unchanged. The U.S. stock market will be closed on September 7 for Labor Day, and the next trading day is September 8; holiday price fluctuations cannot be described as a new round of ETF buying.

Over the next 24 hours, watch for evidence of returned funds, official remediation updates, and announcements from platforms resuming deposits and withdrawals. Only when reserves are restored, the fix is verified, and redemptions actually resume should the risk assessment be lowered; if additional assets are affected, the warning scope should be expanded.

#比特币 #Liquid #asset security

White hat returns 270 million USD worth of Bitcoin to Liquid before the network restarts

- The actors have returned 85% of the Bitcoin withdrawn from Liquid’s linked wallet following the security incident.
- The returned amount is equivalent to approximately 270 million USD.
- The Liquid network is preparing to restart after the incident.
- The RSS source has not yet provided further details on the specific timing or restart plan.

#BinanceSquare #CryptoNews #Bitcoin #Liquid #BTC

$btc

vlikevn Titanbot

Source: CoinTelegraph

Liquid Network restores block production after $320 million exploit

- Liquid Network has restarted block production after deploying an emergency software update.
- However, transactions and peg-related activity remain temporarily suspended while recovery efforts continue.
- Damage from the exploit is estimated at $320 million.
#BinanceSquare #CryptoNews #Liquid #BTC

$btc

#vlikevn Titanbot

Source: CoinTelegraph

Liquid 被抽走近 4000 枚 BTC——但链上的"不对劲"，比新闻早

On September 6, the Bitcoin sidechain Liquid had nearly 4,000 BTC (about $320 million) withdrawn; at one point, its reserves dropped to just 5%. Many people’s first reaction was, "Hackers are dumping the market." In fact, the chain had already been flashing red long before the news.

What you really should watch isn’t "how much was stolen," but on-chain indicators such as the reserve balance, abnormal minting, and large withdrawals. The root cause this time was a verification vulnerability in Elements (range proof caching reuse), which allowed L-BTC without real BTC backing to be minted out of thin air, then transferred through the normal withdrawal flow to be exchanged for real coins. The money followed a "compliant" path, but the on-chain data—reserve plummeting, abnormal mints, and large-scale movements—was already visible at the front end.

I built this kind of monitoring into a system before (balance/abnormal transactions/threshold-based automatic alerts), aiming to surface "anomalies" to people before they hit the trending headlines.

My assessment: this has no material impact on the BTC mainnet. The risk is concentrated in the redemption of L-BTC and the trust assumptions for the sidechain. So in the short term it’s just an emotional disturbance—don’t panic. The real focus is these three signals: "reserves recovering + patch deployment + where the remaining 598 BTC goes." Until things are clear, I won’t touch L-BTC.

Do you normally watch for on-chain anomalies? Let’s discuss in the comments.
#Liquid #链上监控 #数据 #量化 #数据控

🔷 Bounty for hacking: how hackers legalized $47 million

A week ago I was looking into the Liquid hack—today, the details.

Facts:
• The attack cost 21 cents in fees—the largest breach of 2026
• “White-hats” returned 3,400 $BTC , but kept 598 (~$47 million) as a “bounty”
• Background: 207 hacks in the first half of 2026 totaling $1.3 billion; the weak link is people

🧠 My take: a shadow market for “bug bounties” is taking shape before our eyes—attackers extract $320 million, return 85%, and keep 15% as a “fee”—more than a legal program would have paid.

⚠️ The “white-hat” label doesn’t erase the theft: check the insurer coverage and the custodian’s reserves.

❓ Is a 15% bounty the norm, or an invitation to new attacks?👇

#BTC #liquid

Liquid hackers paid back 3,400 BTC—returned to the original address 😳
On Sunday, nearly 4,000 BTC were siphoned from Liquid’s sidechain. Now they’ve recovered 85%.
Based on current prices, this repayment is worth about $270 million.

Let’s recap: on Sunday, the hacker pulled roughly 4,000 BTC from the Liquid Federation wallet.
Liquid had only about 4,200 BTC in reserve—almost completely drained, and the network effectively shut down on the spot.
At the time, the other party claimed to be a white-hat, saying that once the vulnerability was fixed, they would return the funds.

Turns out it wasn’t just talk.
Blockstream first patched the vulnerability on the affected nodes, then used a Bitcoin on-chain signed message to reach out and address the attacker.
On-chain records show the full 3,400 BTC were transferred back to the Federation wallet without a single coin missing.
There are still 598 BTC left to be repaid—about $47 million—so both sides are still at odds.

Here’s the interesting part: Ledger’s CTO, the head of the hardware wallet giant, directly fired back.
He said they kept nearly 600 BTC as a “compensation for the trouble.” That move doesn’t really look like a white-hat—more like coercive extortion.
White-hat or gray-hat—on-chain, it’s just one thin sheet of paper.

As for Liquid: the network remains paused. The official advisory says not to send funds to the deposit addresses yet.
Wait until the restart is confirmed before doing anything—don’t be the one who ends up holding the bag.

This incident is a pretty solid reminder for us.
Sidechains and cross-chain bridges—these “high-end” channels. When something goes wrong, it can become a massive hole.
Big players’ assets can be siphoned—what about ordinary users’ wallets?
Don’t put all your eggs in one basket. That old saying still applies on-chain.

Every day I bring you the latest BTC headlines—not just what happened, but also the logic and opportunities behind it 👀🚀
Click the link below to follow me 👇🏻
👉 加入小恐龙粉丝群
#比特币 #Liquid #安全 #Hacker

What is restaking? Liquid restaking, EigenLayer, and the new yield stack explained

Restaking lets you take the ether you have already staked and put it to work a second time, securing other protocols for extra yield. It is one of the largest ideas in crypto today, and one of the most misunderstood.…

#Learn #Liquid Staking #Staking

Something strange happened with Bitcoin’s Liquid sidechain.

The network stopped its operations after a massive withdrawal.

A group identifying itself as white hats took out 4,000 $BTC .

We’re talking about around $320 million in total.

Those responsible notified Blockstream that they will return almost everything.

The condition is that first they must fix a vulnerability in Elements.

It’s interesting how these security events are handled these days.

What do you think about this kind of intervention?

#Bitcoin #Liquid

nobody stole a key

Liquid lost 4,019.4 BTC on september 6. about $320 million, out in one peg-out. the federation signed it with keys that were never compromised, and SideSwap says its peg-out key wasn't either.

the hole sat upstream. an inflation bug in Elements. someone minted over 4,000 L-BTC that didn't exist. the software checked those coins, called them valid, and the signers released real $BTC against them.

reserve page before: over 4,200 BTC. after: about 207😄

then the drainer signed a message on chain. we are whitehats. contact us on chain. Ledger's CTO said the obvious back: white hats don't drain a bridge first and ask for contact after.

i've been repeating "not your keys, not your coins" like it's a whole security model. it's half of one. a bridge coin is backed by the code that counts coins. that code can be wrong. every key stays safe the whole time.

lessons:
- the wrapper is a claim, the coin is sitting somewhere else
- ask who signs the release and what convinces them a claim is real
- do this while the bridge is still open

which wrapped or bridged thing are you still holding? name it in the comments and i'll go read what actually backs each one, then post whatever i find in one go.

like it if that saved you an afternoon, follow if you want that post, from a guy who checks nothing until it's already on fire)

#bitcoin #Liquid #exploit

Trading resumes, but that doesn’t mean risk has been fully cleared.

After Liquid reopens trading, what matters more are the reserve data: currently the L-BTC reserve coverage is about 85%, meaning there’s still a gap of roughly 15%. While reopening trading may improve short-term liquidity and market sentiment, it won’t automatically replenish reserves, nor does it imply that redemption pressure has disappeared.

Next, focus on three things: whether the official side provides a clear plan to make up the shortfall, whether the reserve address continues to see net inflows, and whether payouts after trading resumes are smooth. If these indicators don’t improve, a price rebound is more likely to be sentiment recovery rather than a fundamental recovery.

Before participating in the rebound, be sure to control your position size and wait for verifiable reserve or audit data—don’t let your risk awareness down just because “trading has resumed.”$BTC

#Liquid #LBTC #加密市场

Liquid was torn open with a huge hole—almost 4,000 BTC are gone

Over the weekend, the Liquid network was breached; 4,000 BTC—about $320 million—were basically wiped out. This is roughly 95% of their household savings. They claim it was a white-hat hacker, specifically naming Blockstream and demanding they patch the issue. After the patch was applied, they did manage to return 85%, with 3,400 BTC taken into safekeeping. The remaining 598 BTC is still being held by the other party, and the bridge has been frozen.

Now the most panicked thing is L-BTC. It relies on a 1:1 peg to Bitcoin to make a living. If the hole can’t be patched, it will have to break the peg. This is another domino effect of Bitcoin L2s: just as Bitcoin L2s keep exploding, Coldcard has barely finished blowing up, Liquid exploded too—security is really paper-thin.

#比特币 #Liquid #安全漏洞

Liquid resumes transfers; LBTC cross-chain redemption still not open

LBTC’s in-chain transfers have resumed, but you still can’t treat it as restored BTC redemption. For anyone who needs to move funds back to the Bitcoin mainnet, the most important question now isn’t the four words “network restart,” but when the cross-chain redemption channel will truly be opened.

On September 10, Liquid first announced a resumption of block production without “trading.” Then the latest announcement clarified that in-chain trading has been restored, but cross-chain outbound BTC is still closed. Today, when you read a block explorer, you can also see that transactions are already included in new blocks. If you only look at the previous announcement, you would carry forward the old status that “trading is still paused” into today.

The difference is this: moving LBTC from one Liquid address to another transfers in-chain assets. Redeeming BTC back to the Bitcoin mainnet through the federation channel requires a separate set of actions to release reserves. The former being restored does not automatically open the latter, and it doesn’t guarantee that exchanges synchronize their deposits/withdrawals at the same time.

On September 8, what we followed up on was partial BTC return. Now we should update the progress to “in-chain trading restored,” and stop broadly saying “preparing to restart.” But the judgment about whether redemption is available must remain unchanged for now. Repairing and restoring operations is real progress—shouldn’t be ignored—yet it also shouldn’t be expanded into a claim that funds can already move in and out freely.

According to the latest official announcement, ordinary users currently do not need to take any action; only those running a Liquid node need to update to Elements v23.3.4. Don’t use so-called “unlock” websites to transfer assets or submit seed phrases because of an “urgent recovery” email.

Over the next 24–48 hours, I will verify the cross-chain outbound resumption announcements, the reserve restoration notes, and actual redemption records. If these pieces of evidence mutually confirm, I will further lower redemption risk. If redemption still can’t be completed after opening is announced, or if a new abnormal outflow appears, I will raise the alert level. If you need mainnet BTC funds in the short term, you should avoid adding new deposits into Liquid until the channel’s usability is confirmed.

#Liquid #LBTC #资产安全

Liquid resumes trading, but what’s more worth watching is this: the L-BTC reserve coverage ratio is only 85%.

This means that, based on current data estimates, for every 100 L-BTC there are roughly only 85 BTC reserves backing it—there is an approximately 15% coverage gap. Trading resumption only indicates that the market has started repricing again; it does not mean the pegged-risk has been fully eliminated. $BTC

Going forward, focus on three things: whether the reserves can be replenished back to 100% as quickly as possible, whether the team discloses verifiable reserve addresses, and whether the L-BTC price and redemption depth continue to deviate. Until coverage is fully repaired, it’s not advisable to simply treat it as risk-free equivalent Bitcoin—be sure to manage position sizing and slippage.

#Liquid #比特币 #加密安全

#SideSwapSuspendsLiquidServices
⚠️ SideSwap Pauses Liquid Services
SideSwap just suspended its Liquid Network services — another reminder that even "decentralized" tools carry operational risk. Always DYOR before trusting a platform with your funds.
🔔 Follow for real-time platform alerts
#SideSwap #Liquid #CryptoNews

“Liquid Incident Reversal: 3,400 BTC Returned”
September 8, 2026 — Previously, about 4,000 BTC that had been withdrawn from the Liquid Network have now been returned, with 3,400 BTC returned so far, recouping roughly 85% of the funds.

This batch of funds was returned after Blockstream stated that the vulnerability in the relevant bridging node had been fixed.
However, the matter is not completely over.
The attacker still holds around 598.5 BTC, worth about $47 million. And as of now, there is no publicly available information confirming that this portion of the funds belongs to the “white-hat bounty” formally agreed upon by both sides.

So the biggest controversy now comes down to this:
Returning 85% and keeping 15%—does that count as a white-hat bounty, or is it essentially the attacker awarding themselves a bounty?
#BTC #Bitcoin #Liquid #Crypto $BTC

🎯 Bitcoin sidechain emptied of 4,000 coins

📰 Liquid suffered an anomalous minting attack, with about $320 million worth of BTC being withdrawn; the chain was briefly halted, then 3,400 coins were recovered from a white-hat team, with the remainder still under negotiation and disposition

💬 When it’s your own bridge that gets hit, it’s even more eye-catching than an exchange getting hacked. BTC sits safely in a cold wallet, stable as ever—until it’s connected to a cross-chain bridge, adding another “door.” Who ultimately pays for that bill is the key issue

🏷️ #Liquid #比特币侧链 #安全事件 #cross-chain bridge