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

#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

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

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

SideSwap suspends Liquid services! 4,000 BTC moved out, did $320 million funds go bad?
Today, a major bombshell suddenly appeared in the crypto market.

SideSwap announced:
All swap, peg-in, and peg-out services related to Liquid have been suspended.
The reason is a security incident on the Liquid network.
Around 4,000 BTC was transferred out from the Liquid Federation wallet, worth about $320 million, accounting for 95% of the roughly 4,200 BTC reserves previously held.

What’s even more strange is:
This withdrawal was completed via SideSwap’s Peg-out Authorization Key (PAK).
However, Liquid states:
❌ The PAK itself was not compromised
❌ No other Federation key leaks were found
❌ SideSwap also said its own systems were not breached

Current disclosed information points to:
An Elements software vulnerability → resulting in L-BTC without real BTC backing → exchanged into real BTC through the normal peg-out process.
That means the most concerning possibility isn’t necessarily “private keys were stolen.”

Instead, it’s this:
The system treated fake L-BTC as if it were real L-BTC.
That’s also why Liquid chose to pause the network directly.
The entity claiming to be “white hat” has already contacted Blockstream via on-chain messages, and says that after the vulnerability is fixed and all nodes complete the upgrade, they are willing to return most of the BTC.

So now there are three key questions:
1️⃣ Can the 4,000 BTC ultimately be recovered?
2️⃣ How exactly was the Elements vulnerability exploited?
3️⃣ When will Liquid resume normal operation?

The good news is:
The Bitcoin mainnet itself has not been affected.

But this incident once again reminds the market:
BTC itself is safe ≠ BTC’s Layer 2, cross-chain bridges, custody, and anchoring mechanisms are equally safe.
Especially assets like L-BTC that rely on federation mechanisms—once a problem occurs with the underlying peg, the risk can quickly amplify.

This time, what truly needs attention isn’t whether BTC will drop because of the news, but whether the $320 million worth of BTC can be returned safely in the end.

#BTC #liquid #sideswap暂停liquid服务

【Breaking! About 4,000 BTC Transferred, Worth About US$320 Million】
On September 7, 2026, a major security incident occurred on Bitcoin sidechain Liquid Network. About 4,000 BTC were transferred out from related wallets, worth approximately US$320 million.
Even more outrageous, the person who transferred the funds also claimed to be a "white-hat hacker." After the incident, Liquid Network has suspended new transactions, and some platforms have also suspended LBTC deposits and withdrawals.
It should be noted: this was not a hack of the Bitcoin mainnet, but a security issue on the Liquid sidechain.
The biggest question now is:
Will these 4,000 BTC be returned?
#BTC #Bitcoin #Liquid #Crypto $BTC

🎯 A bombshell worth $320 million in chain exploits—institutions moved in and stepped on another landmine

📰 Liquid network shocks with a staggering new vulnerability report. Even though it’s supposedly tied to Bitcoin, it still got hacked—$320 million is simply gone. Just when institutions were about to nod in approval, they were hit with a bucket of cold water

💬 In the end, the heavier the on-chain footprint, the more it tests security. What we fear most is a “looks reliable” custodial loophole. Don’t overthink short-term market jitters into a systemic collapse; in the long run, stay clear-headed and watch risk controls

🏷️ #比特币安全 #Liquid #黑客 #托管风险 #institutional entry

4000 BTC withdrawn, 3400 returned

The incident occurred on Liquid’s sidechain. After about 4000 BTC was withdrawn, the “white hat” returned roughly 3400 BTC (news reports put it at about $270 million), but is still owed about 598 BTC; the network is preparing to restart.

Cointelegraph 9/8: Samson Mow’s retelling is that it was returned only after a patch was applied. Ledger CTO and others have questioned the white-hat narrative, suggesting it sounds more like a bounty discussion.

My stance: treat sidechain/federated custody risk as its own matter—don’t mix it up with the Bitcoin main chain. Until the outstanding balance is settled and the patch can be verified, don’t let this story become the “closing statement”; if the debt remains outstanding, consider it under unresolved/unfinished conditions and the associated risks. Sidechain risk is sidechain risk; main-chain risk is separate.

Which do you believe more: “white hat returns after the patch,” or “talking about a bounty and only then returning coins”?

Personal observation only; not investment advice.

$BTC #安全 #Liquid

Draft reviewed: passed

A key turning point has emerged in the Bitcoin sidechain Liquid Network fund incident. After about 4,000 units of $BTC reportedly flowed abnormally out of a federation wallet earlier, the self-claimed white-hat party has returned 3,400 $BTC to the Liquid Federation—about 85% of the amount involved. The main funds have already been returned to the federation address.

Only after Blockstream confirmed via an on-chain signed message that the bridge node had completed repairs did the other party complete this repayment. There are still about 598.5 units of $BTC left at the relevant address. Many external interpretations view this as a self-assigned “bounty,” but there is no publicly visible agreement between the two parties, and no official final position has been issued yet regarding how the remaining gap will be handled.

At present, Liquid bridge connectivity and L-BTC deposits/withdrawals remain paused, and the timeline for a full resumption has not been announced. Whether the sidechain reserves will be realigned, how the remaining funds will be handled, and when exchanges will reopen the relevant channels are the key points to watch over the coming days.

#比特币 #Liquid #区块链安全
This does not constitute investment advice

Liquid drained of 95% reserves; the hacker only agreed to return 85%

On September 6, the Liquid network disclosed an Elements consensus and asset verification vulnerability. The attacker minted about 4,000 L-BTC tokens with no real underlying assets, then went through SideSwap’s normal redemption process to swap these “air L-BTC” into 3,996.01834922 genuine BTC, taking them directly from the Liquid Federation. At the time, the value was about $320 million; the reserve balance dropped from roughly 4,207 BTC to around 197 BTC—draining 95%.

The Bitcoin mainnet itself was not compromised. Of the Federation’s 11/15 signing members, those who were supposed to sign did sign—so the signature mechanism was functioning normally. The issue was entirely in Liquid’s sidechain Elements validation logic. SideSwap also stated that its PAK system was not breached; it was only used as a normal redemption channel. Other assets such as USDT were unaffected because they are never backed by that peg wallet. However, the network’s pause mechanism still froze the entire transfer and liquidity.

As for what happened next: the attacker used an on-chain OP_RETURN message to claim they were a white-hat, demanding that the vulnerability be fixed before returning the funds. The two sides negotiated across the blockchain for several rounds. On September 7, the attacker returned 3,400 BTC, keeping 598.5 BTC—worth about $47 million at the time—as an effective “finder’s fee.” That ratio was no longer up for discussion; in the end, the attacker only returned a sad emoji.

This kind of “hack you, then voluntarily negotiate part of the return” is no longer new in DeFi and cross-chain over the past couple of years. But the larger the amounts involved each time, the weaker the deterrent effect of this “post-hack protection fee” approach on the whole industry becomes—if the cost of a vulnerability is always “return the bulk, keep a substantial split,” does that count as effectively encouraging more people to go looking for bugs?

#Liquid #Blockstream #BTC #侧链安全 #白帽黑客

The operator who claimed to be a “white hat” has reportedly sent back about 3,400 BTC to the Liquid Federation wallet, worth approximately $268 million at the time based on the market view. In addition, about 598.5 BTC (about $47 million, about 15% of the amount previously transferred out) remains in the other party’s address.

Cross-verification by Bitcoin.com, The Defiant, and Lookonchain / Odaily indicates that the rollback occurred after Blockstream announced via an on-chain PGP-signed message that “the bridging node has been patched and funds can be safely returned.” Previously, about 3,998.5 BTC had been abnormally minted due to a vulnerability in the Elements software, and were proposed through SideSwap’s legitimate peg-out pathway. The official says that the leak of any keys has not been confirmed. On the Liquid sidechain, operations are still paused; exchange access for LBTC is still suspended; and other assets such as USDT were previously said not to be affected. The Bitcoin mainnet itself has not been implicated.

Set the boundaries clearly: the rollback does not mean the network is fully restored, nor does it mean that 1:1 reserves have been completely replenished—about 600 BTC are still in the other party’s hands, and the official has not publicly characterized this portion as an agreed bounty. First confirm the on-chain numbers, the balance in the federation wallet, and the restart notices; then assess whether the L-BTC peg has returned to normal. Don’t translate “most has been returned” directly into “the event is concluded” or a trading signal.

Market reference (CoinGecko): $BTC about $79,000, and $BNB about $739. Re-check on-chain data and the official position before discussing sentiment.

$BTC $BNB
#Liquid #比特币 #white hat
Not investment advice

Liquid was attacked for $320 million—but on-chain anomalies often show early warning

In crypto, monitoring on-chain data exposes risk earlier than intuition—abnormal transactions and large on-chain movements often show signs before things go wrong.
I personally built monitoring and alerting into a system (automatic alerts/thresholds pushed to WeChat) so I don’t only find out after an incident.

(Featured image: data chart)

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

“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

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

3,400 BTC have been returned—can Liquid safely resume deposits?

The return of funds is a real step forward, but it isn’t enough to justify restoring deposit functionality. LBTC holders need to independently verify that the funds have been returned, the vulnerability has been fixed, and withdrawal services have been restored—not treat the first item as proof that all three have been completed.

On September 6, Liquid announced that around 4,000 BTC had been taken and that the network would be paused. On September 7, The Block updated its report: Blockstream indicated via on-chain messages that the bridge node had been patched, after which 3,400 BTC were returned. This verification cross-checked mempool and the Blockstream browser against the same transaction in block 965950, confirming that 3,400 BTC were transferred out and about 598.5 BTC in change was sent back to the original address. The federal identity of the return recipient is based on media reports.

This provides real transfer evidence beyond a mere “promise to return,” but it still isn’t a complete reserve audit. About 598.5 BTC is change from the transaction; it doesn’t equal the final, confirmed loss. Moreover, these amounts don’t represent the full network reserves or the proportion of user compensation.

SideSwap previously clarified: during the network pause, exchange services are suspended—please do not add new deposits. As of this verification, there has been no announcement of a full service restoration. Funds returning to the receiving address does not automatically mean exchanges, deposits/withdrawals, and cross-chain swaps are restored at the same time.

Yesterday’s view was adjusted accordingly: “no return confirmation” was updated to “partial return confirmed,” but the judgment that “withdrawal usability should be confirmed first” remains. Affected users should check the restored status through the official entry points of the platforms they used. For orders not yet completed, keep the transaction ID, and do not provide a seed phrase to unfamiliar “recovery pages.”

Over the next 24 hours, key points to watch include the handling of remaining funds, explanations of reserve coverage, the post-incident fix review, and platform restoration announcements. Only after the fix and reserve coverage are verified, and actual withdrawals are restored, should risk be reduced. If there are any further abnormal outflows, or if withdrawals still can’t be completed after restoration, the alert level should be raised.

#比特币 #Liquid #资产安全

Good news! Liquid Network successfully recovered 3,400 BTC through on-chain negotiations. The white-hat hacker retained nearly 600 BTC (about $47 million). The bridge nodes have already been patched, and this security incident is now over. In the short term, the BTC market may rise as the resolution of the security issue provides a boost to market sentiment. However, those 600 BTC could be sold off at any time, so investors should watch for short-term volatility. Safety first—there’s still a long way to go for the blockchain industry. #Bitcoin #Liquid #Security

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

Don’t rush to shout “returned = over”: the Liquid white-hat storyline has moved one step further, but the network is not yet back online.

According to on-chain monitoring by Galaxy Research head Alex Thorn, the self-proclaimed white-hat side is communicating with Blockstream via OP_RETURN and PGP-encrypted channels, and has made it clear that they will return “most” of the roughly 4,000 $BTC previously transferred only after the vulnerability is patched and all network nodes complete the upgrade. At the time of the incident, those funds were valued at about $320 million. Liquid’s official statement previously said the Federation wallet had been drained of about 4,000 BTC, with reserves falling from around 4,200 to about 207 BTC; sidechain bridging has been suspended, exchanges have paused LBTC deposits and withdrawals, and other assets such as USDT are said to be unaffected for now.

Keep the wording tight: the other party said “most,” not “all”; the return still depends on the patch being deployed and confirmed. Market reference (CoinGecko): $BTC about $79,300, $BNB about $743. First watch official progress and node upgrade updates, and don’t treat the white-hat statement as if the funds have already been recovered.


#Liquid #比特币 #whitehat
Not investment advice